I need to disable Update Orchestrator Service aka. When I noticed this pattern, I thought that setting "Do not allow update deferral policies to cause scans against Windows Update" to Disabled might finally have put the issue to bed last month, as the laptops are all joined to our completely isolated, internet-only wifi, but here we are again with the same issue.I'm on build 1803 of Windows 10 Home. The only clue really is that most of the affected machines are laptops - our desktop PCs (which are a minority apart from one department) don't seem to have this issue.
Initiating the restart are completely absent. Usual signs that the computer is about to shut down due to explorer.exe Update from the list above requiring or initiating a reboot – in fact, the Nothing in the event logs shows a particular Log that it has processed this update prior to rebooting. Successfully installed the following update: 2018-02 Cumulative Update for Service terminated with the following error: It then rebooted without any obviously relevant These updates should require a restart as far as I can tell. I went through the event logs and found the following information:ĩWZDNCRFJ10M-2FE3CB00.PicsArt-PhotoStudio The WSUS Automatic Approvals rule applied to these clients is:Īgain, this has been ignored, with a few clients rebooting within 24-48 hours of the updates being released.Īn example client machine is one from this morning - it's a laptop (HP ZBook, if that makes any difference) which rebooted shortly after logging in at 9AM. In particular, it seems to ignore the the 'No auto restart with logged in users' and 'Active Hours' settings. We recently applied a set of policy template updates which added a set of Windows 10-specific controls we thought were the culprit. All clients have the following GPO applied:Īs far as I can tell, these are all set correctly to prevent the behaviour we're seeing. All PCs are on an Active Directory domain managed via group policy. Updates are managed by our on-premise WSUS server. It's not always the same machines, it happens in the 48 hours following updates being released and goes against our group policy settings. We have a problem with Windows 10 client machines rebooting to apply Windows updates following patch Tuesday.
This is a well-worn topic, I know, but no amount of research and GPO adjustment has helped on this one so I'm hoping someone can highlight where we've gone wrong.
0 kommentar(er)
