90
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Apr 2026
90 points (100.0% liked)
techsupport
3102 readers
3 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 2 years ago
MODERATORS
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