Cumulative update KB5001391 fails to Install
Hello Guys ! A expected ONCE AGAIN Microsoft Cumulative update KB5001391 fails to install on #Windows 20H2 , as this has been the 3rd failed update like previously two KB5000842 and KB5001330. Am I the alone on this planet ? The error message I have received is 0x800f0922. I got a new Laptop HP 8th generation. What is happening inside Microsoft these days ? Shout out loud If you're having the pain like I have these days ? Please Please Please
Problem installing Cumulative Update Windows Server 2016
Hi! We have a Citrix VDA running on Windows Server 2016, and trying to install Cumulative Update 2018-10 but after the restart the process stops at 99% and then the installation reverts. Same thing happens when I try Cumulative Update 2018-11. But all the other Updates works, for example: 2018-11, update for Windows Server 2016 We have tried the following things: Renamed the softwaredistribution folder Tried manually install Run DISM-commands with no errors Run SFC /Scannow no errors The error I see in the log is: Event 20, WindowsUpdateClient Installation error: It was not possible to install the Update, cause error 0x800F0922: 2018-10, Cumulative Update for Windows Server 2016 Do anyone here have a suggestion what I could try more? Best regards Gustav
did the Jun 9 Security Update remove trusted (amazon) certs?
We have a product that runs on Windows and uses AWS IoT to connect and transmit info. We noticed yesterday that many - roughly 2/3 of our fleet went silent - no connections. We have some of our own PCs that experienced this as well. Investigation yielded issues with TLS. The client (which is just using the default windows cert checking) actively terminated the connected. It didn't like the cert from the AWS IoT endpoint. All of these PCs were happily connected on Jun 8. Investigation seemed to indicate that some combination of Amazon Root CA (1-4) and some Starfield certs were not in the device cert mgr. Also - when we manually added AmazonRootCA1.pem to the cert mgr, our service connected again. So the evidence seems to strongly support that the security update removed trusted amazon root certs from the cert store. I'm guessing some/many won't notice since they are making regular TCP connections and maybe the certs get auto-added if they are not there? But we are doing MQTT over the AWS port 8883. So perhaps Windows did not detect this and seek to refresh its cert store? Can anyone confirm if they have seen the same?
