Forum Discussion
Windows 2022 Server may Updates have failed
https://catalog.update.microsoft.com/Search.aspx?q=5038282
Hello, I Thank you for the reply and suggestion.
I have tried several times, and I am currently trying it again to see what will happen.
If it fails again tonight, sometime this weekend I will disable all of the anti-malware and bypass the security protections to see if that matters.
THIS time I see that the 5038282 apparently installed correctly, but when I look at windows update it shows that it still needs the patch. I ran the Windows Update troubleshooter again and it says it had issues.
The only hint that the troubleshooter gives is:
WaaSMedicService
Issue found by : DynamicProtectionPlugin
The patch KB5037930 has applied successfully, via the Update History.
With the Cumulative Update failing and three patches needed, it will uninstall all three patch attempts if there is a problem as it has done several times. I will wait to see if windows update will reflect the success of KB5038282 (aka KB5037930). Then I will be down to MS Defender Update and the May CU.
If it does not register as installed, I will run the WU again and see if it reports it as already installed.
- I am down to just the May CU. I worked in network security for 25 years with over 50% of those years dealing with patches of all sorts, majority being MS. All I want to say is, if some patches work and apply successfully, then the process works, but this patch does not.
In the past I have found that several IP's which MS uses for storing patches also has some rather questionable domains which are separate from the MS, but reside close to them. That results in a bad reputation score for that IP or IP range and anti-malware and IPS style security vendor will add them to the block list.
In the next few days, I am going to go through the entire Windows Update History area and see if there are any other currently valid patches that may have failed and attempt to apply them as well.- To my side, from time to time we get some kb who doesn't want to install, so when that happen we try to manually install, if it work, we use SCCM to deploy the kb.
To respond to your question about the DeviceSetupManager, i have the exact some error but this is not about windows update but about an update drivers.
You can find some tips to below, but there are no really answer to this error except to contact microsoft.
https://answers.microsoft.com/en-us/windows/forum/all/why-am-i-seeing-lots-of-event-id-131/48e86fda-03c6-4292-9dbb-88bd9218ae87
And below to see how thing progressing
https://www.bleepingcomputer.com/news/microsoft/microsoft-says-it-fixed-a-windows-metadata-server-issue-thats-still-broken/
For the kb who doesn't want to install you have to check with the powershell "Get-WindowsUpdateLog" and see what happen.
