MS in particular has the habit of actually introducing small bugs like this regularly through their usual updates. It's infuriating. One day something works the next it just doesn't. I know people who never update their machine because of this. Can't blame them. Once it works, why take the chance of breaking it with updates? It it is a certainty that at some point MS will break some functionality of your system with an update. It's just a matter of time. So turning off auto update is the most sane thing to do for most people. I recommend it myself, and if you update your Chrome or Firefox automatically it is safe enough to use an unpatched Windows for most people anyway.
Once MS started introducing new bugs rather than actually fixing old ones I knew the last MS machine I will service is a gaming machine for my family. As long as that needs to run, I will make it run. All my other systems are on linux now. Once the gaming craze is over I will ceremoniously burn the Windows license key that I used, and I will never, ever, run any software from Microsoft ever again.
Except at work of course, but I don't mind getting paid to be frustrated.
HA!
I was just testing a VR app that has a Windows component when things started failing in VR. I took off my headset and noticed my test machine going through power-on self test.
"Oh crap!", I thought, "a bug caused the system to reboot".
Nope. Just Microsoft deciding it's time to apply some updates. Doesn't matter that I scheduled for a time that I wouldn't be testing.
I've NEVER been able to successfully gain control of this, despite reading up on it and doing all the recommended things.
%windir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator
rename Reboot files and add them as folders (you'll need to override file permissions).https://www.joe0.com/2019/10/17/how-to-prevent-windows-10-au...
I feel like this used to work properly until a month or so ago.
The worst bug I've seen, and this is also something that only started happening in the last several months, is select messages simply not appearing! So basically I open my computer in the morning and look at Teams and it'll have messages from overnight. EXCEPT some messages did not make it, like, at all. There was a whole thread that had replies that were simply not visible to me. I even replied to that thread and on my screen the reply appeared right after the last visible message whereas for everyone else it appeared after the 40 or so messages that came in overnight.
I haven't been the only one to run into that issue either. Restarting Teams is the only thing that brought the messages back.
Now that's what I call a critical bug! Who knows how many things I've missed.