I woke up again
to my machine being restarted. To make it worse
, I had a VM open as I was going to have an early meeting and wanted to make sure I didn't have to start the VM before the meeting. To make it even worse
, the VM showed aborted as the status. I started the VM, and it was thankfully fine, but I just knew I had to do something at this point.
Apparently, Microsoft introduced a Windows Update Medic Service
in 1803- I'm guessing this is what broke my workaround. This service is apparently meant to repair Windows Update
happens to it. The service itself has the description, "Enables remediation and protection of Windows Update components."
part means that this re-enables the Windows Update Service if you disable it- I found that out the hard way. To make it even worse, you can't disable this service. You get access is denied if you attempt to do so. I suppose you could attempt to take ownership, but I found a tool that does it for you before I even tried, and figured I'd mention it here, as I don't see any mentions on a search.
Windows Update Blocker (https://www.sordum.o...update-blocker-v1-1/
) is a portable tool that allows you to disable both. It does require a bit to get it to disable the medic service that you have to do manually, though it does have a protect service settings that would seem to handle that also.
The struggle is real- how long can this continue before they learn that their customers don't want this?