I am on Windows 10 pro and have debloated and stripped as much tracking junk as I could from the OS, so Copilot had been long gone… until two days ago, when it reappeared on my start menu. I assumed it was sneakily reinstalled after an update so I uninstalled it.
Less than 30 minutes later, it was back. I uninstalled it again, and again it reinstalled after about an hour.
I’ve tried registry edits, I’ve tried changing the group policy, but it does nothing - Copilot keeps reinstalling itself in the time span of 20 minutes to an hour.
I know being on Lemmy I’m going to get a bunch of “Replace it with Linux!” replies so I’d like to preempt this by promising you that yes, that will happen eventually - there’s just some compatibility issues with a couple of my daily driver programs that are pending a resolution.
For now I must stay on Windows, but Microslops incredibly aggressive Copilot reinstalls are pissing me off and I was just wondering if there are any other means in which I can get rid of this program, or at least hide the stupid ugly thing from my sight?
Edit: I suppose it’s important to note that I am not nearly as tech-savvy as a lot of people here, but I try to get by. Please keep this in mind if I ask stupid questions.


On maybe a more-helpful note, I have no idea if it might have consequences for your system (spend time every reboot trying to reinstall?) but you might try doing something that’d cause the installer to fail. Whatever update mechanism they have might back off if the installer just can’t succeed. Maybe uninstall Copilot, then replace one of the files that’s associated with Copilot with a directory or something, and if the installer can’t handle replacing that directory with the file it tries to install next time it runs, it bails and backs out?
I’ve occasionally used that trick when some program writes massive log files and doesn’t have an explicit way to disable log file writing — just drop a directory in the way.
It may also help taking ownership of a folder and making everything read only. I slightly doubt there are checks for that scenario in the middle of the process.
Knowing microslop, it’d probably just bsod