Jared ran into a simliar'ish problem recently... There is a thread around here somewhere.

@brandon220 said in HP EliteDesk 800 G5/G6 mini - error on windows update: @Dashrender I had it on a new 800 mini a few weeks ago. I clicked through it and it has been running fine since. Several reboots and it never happened again. I just updated the OP. sadly, after rebooting, the system locked up, requiring another hard reboot, another flashing of this HP screen, hit esc to bypass and the user is back up and running.

@black3dynamite said in Windows Server 2016 RDS - GPO for Disabling Windows Update Notifications for Non-Admins/Users?: @wrx7m said in Windows Server 2016 RDS - GPO for Disabling Windows Update Notifications for Non-Admins/Users?: @black3dynamite said in Windows Server 2016 RDS - GPO for Disabling Windows Update Notifications for Non-Admins/Users?: @wrx7m Is that a computer configuration or user configuration policy? Try applying the rules to only non-admins groups. Yeah, it is at the computer level. I would like to do it via user config but I only want them to apply to users on the RD servers. I need to figure out the proper way to structure AD/GPOs to not screw up everything else. I am guessing creating another OU as a sub container and move the RD servers into. Edit: Since it isn't GPP, there isn't any item level targeting, so I can't do it that way. If you can make those changes directly in the registry, maybe can allow you to use GPP and item level targeting. Hmmm. That makes sense. Let me mull it over.

@wrx7m said in Windows 10 Updates - Trigger "Update and Restart": @IRJ said in Windows 10 Updates - Trigger "Update and Restart": @wrx7m said in Windows 10 Updates - Trigger "Update and Restart": @IRJ said in Windows 10 Updates - Trigger "Update and Restart": @wrx7m said in Windows 10 Updates - Trigger "Update and Restart": A simple restart command doesn't perform the update step, just the restart, so the update doesn't get applied. This has been an issue for a very long time with windows. I am surprised it hasn't been fixed yet. It's really annoying Well, at least with Win 7, a standard reboot applies updates. At least, I think it does. The main difference between Win 7 and 10, is that they have switched to the osoclient.exe to manage the updates. I'm pretty sure server 2008 and onward had the issue. I don't remember dealing with it on workstations I still have a 2008 R2 box and can test it on the next go 'round. I won't have it much longer, as I am dumping it prior to EOS. LOL - Didn't make this cutoff. Next week, hopefully.

@wrx7m said in Server 2016 - Force Default Update Server to WSUS Server Via GPO: @dbeato said in Server 2016 - Force Default Update Server to WSUS Server Via GPO: This would have happened on Server 2012 R2 as well, dual scan has been around and causes a lot of problems as you noted. It is strange that I didn't have these issues in 2012 R2. I essentially copied the same GPO for 2012 R2 and made some minor changes to it to convert it for 2016. My 2012 R2 show the correct default service. Weird, I have various Server 2016and now 2019 with WSUS and while dual scan was an issue for me on Server 2012/ 2012 R2 not anymore.

https://www.bleepingcomputer.com/news/microsoft/microsofts-april-2019-updates-are-causing-windows-to-freeze/ Looks like it isn't just Sophos.

A bit outside your specific question; however on my Exchange servers I just disabled the MSExchange ActiveDirectory Topology Service; doing that prevented the rest of the Exchange services from loading and KB40720650 loaded without issue

@dbeato said in KB4074588 breaks USB mouse and keyboard: Also are your devices with AMD Processors? No, Intel, different gen on both laptops too

Always wait these out. The only time I wouldn’t is if I have a snapshot pre update that failed and just revert to it.

Since today is patch Tuesday, I'll wait and see what comes down.

That assumes you can.

@travisdh1 said in Windows 7 and 8.1 updates switching to cumulative monthly rollups starting in October: @scottalanmiller said in Windows 7 and 8.1 updates switching to cumulative monthly rollups starting in October: I've seen a lot of people complaining that there have so many small patches break things that this will cause support problems for them. I should pull the local repair shop owners in here, you'd never hear the end of it. Ha! Yeah, why do patch updates only seem to affect consumers and SMBs?

Might have something to do with most Samsung computers still being incompatible with Windows 10. Also, beat you to it http://mangolassi.it/topic/5345/samsung-disabling-windows-updates