this post was submitted on 06 Jul 2026
350 points (92.7% liked)
Technology
86131 readers
3257 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nah, Windows is getting terrible. I had to delete AI.exe and aimgr.DLL to get performance back in the office suite. Updates try to out it back, and I know as soon as its deployed because everything runs like crap. And there's Onedrive that locks up the system while it syncs a newly written local PC file to the cloud. Like it should immediately write local, and sync in the background but it waits for the commit back from one drive
My armchair diag is that you're causing your own issues by doing things the wrong way. Disable it via policy not by deleting random files. How could onedrive lock a computer up syncing a file that doesnt even make any sense since it does write it local and sync in the background. It sounds like you were trying to save to a network folder or sharepoint maybe.
I couldn't find a policy for the ai. Exe, but when it's deleted the PC runs fine.
No on the network, we don't have typical network shares.
It's my C drive, and file explorer locks up until sync has happened. Because I see the spinning sync icons, as soon as sync has happened to one drive the file is accessible and apo saving it gets a commit back that it happened and is functional again. These are some of the problems, but there are tons more.