- Oct 25, 2017
Someone I know had issues upgrading because of some random driver that was not compatible. There was no warning, just a failed to update.
Thanks. I'll have a look.
I know there's a risk by not updating, but I think it's riskier to update Windows until the patches are vetted. I always wait a week or two before patching.Yeah, that's the wrong mindset. The whole point is to prevent it, but sure, listen to the guy with a blog and not to those who actually know how to weaponize this and are warning about it.
People like him is why WannaCry had such a wide reach: people didn't patch.
yesThe updates I have are the following:
- Windows Malicious Software Removal Tool x64 - January 2020 (KB890830)
- 2020-01 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4528760)
- 2020-01 Cumulative Update for .NET Framework 3.5 & 4.8 for Windows 10 Version 1903 for x64 (KB4532938)
Am I good?
I dealt with a machine a few weeks ago that was stuck on 1803, and would bluescreen when going through Windows Update to 1903.
Microsoft: "Sorry folks, we can't get you that super important security update until you download our sweet new web browser."
I'm having the same error. If I do this, do I keep all my files or do I have to start from scratch?I dealt with a machine a few weeks ago that was stuck on 1803, and would bluescreen when going through Windows Update to 1903.
I used Rufus to download and create a 1809 USB, and used it to installed 1809 OK.
Then I did the same with a 1903 USB and a 1909 USB. That was the only way to get that machine updated, but hey it's on 1909 and it seems to be working fine.
More details: https://pureinfotech.com/download-older-iso-windows-10/
Rufus homepage: https://rufus.ie/
edit: oh you already got it to update ok. Nice, good luck with the rest of the updates.
lol... this goddamn computer. Tried to delete those files, nope. Doesn't even give me an error message, just ignores me.
Works for 10
Hey I just wanted to thank you for this. This didn't solve my problem but the entire thread was the prompt I needed to actually do something about my PC being stuck in a boot loop every time it tried to update, so lots of Googling later I found a suggestion of disabling VT-d in BIOS (chipset settings) and it actually worked.