3 ms·
Microsoft totally lets them. If you use any Enterprise version of Windows, the company can disable updates, but not the user.
by philistine 2y ago
Microsoft totally lets them. If you use any Enterprise version of Windows, the company can disable updates, but not the user.
- __MatrixMan__ 2y agoNo, after the fact. Where's the prompt at boot-time which asks you if you want to load yesterday's known-good state, or today's recently-updated state? It's missing because users are not to be trusted with such things, and that's a philosophy with harmful consequences.
- bentcorner 2y agoIsn't this in the boot options? https://support.microsoft.com/en-us/windows/advanced-startup-options-including-safe-mode-b90e7808-80b5-a291-d4b8-1a1af602b617 https://support.microsoft.com/en-us/windows/advanced-startup... > Last Known Good Configuration (advanced). Starts Windows with the last registry and driver configuration that worked successfully.
- __MatrixMan__ 2y agoI don't have any affected systems to test with, but I'd be pretty surprised if that were an effective mechanism for un-breaking the crowdstruck machines. Registry and driver configuration is a rather small part of the picture. And I don't think that's an accident either. Microsoft is not interested in providing end users with the kind of rollback functionality that you see in Linux (you can just pick which kernel to boot to) because you can get less money by empowering your users and more money by cooperating with people who want to spy on them.
- vetinari 2y ago1) It is not enterprise version of Windows; it is any version capable of GPO (so Pro applies too, Home doesn't). 2) it is not disabling them; it is approving or rejecting them (or even holding up the decision indefinitely). You can do that too, via WSUS. It is not reserved to large enterprises, as I've seen claimed several times in this thread. It is available to anyone, who has Windows Server in their network and is willing to install the WSUS role here.