OP
OP
-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
Windows 10 users: UPDATE NOW! Certificate validation is broken! (NSA: Critical Vulnerability Advisory issued)
- Thread starter neoak
- Start date
OP
OP
Just checked, it's actually KB4534293. It was in the post I quoted.
Very helpful, lol.
I give up. That's supposedly the 1803 update for x64... but it aint playing ball.
The one you have in that pic is for .NET 4.8. Do you even have 4.8?
On KB4534293 I just get "this update is not applicable to your computer". Might that mean it's already installed?
OP
OP
Check the update history. It's there in the Windows Update window
Not that I can see. Just a bunch of failed attempts to install 1903, and some failed attempts on the .net update.
OP
OP
You sure it is 1803? Not 1809?
1803 is only on LTSB status right now, so unless it's Win10 Enterprise, you should have 1809.
Happy to try upgrading to 1809 if I can find a download somewhere, but I don't really want to try 1903 again as it took hours and I'm not convinced it's going to work this time around.
Edit - Or whatever version the Windows 10 November 2019 Update is.
OP
OP
Someone I know had issues upgrading because of some random driver that was not compatible. There was no warning, just a failed to update.
Happy to try upgrading to 1809 if I can find a download somewhere, but I don't really want to try 1903 again as it took hours and I'm not convinced it's going to work this time around.
Edit - Or whatever version the Windows 10 November 2019 Update is.
I'll try to find a 1809 update
OP
OP
You'll have to do a feature update. Earliest supported now is 1803 for Enterprise licenses.
OP
OP
Psychotext Go to https://tb.rg-adguard.net/public.php
Select Redstone 5 March 2019 for version.
Mount the ISO or extract it to a USB drive, and try again.
Select Redstone 5 March 2019 for version.
Mount the ISO or extract it to a USB drive, and try again.
Thanks. I'll have a look.
If this doesn't work I'm just going to build another machine. Crazy how screwed up this one seems to be.
OP
OP
Plus the HTTPS for Windows Core, as well as certificates for Updates and applications.
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.
That build seemed to install, thanks. Just seeing if I can install updates from there onward.
The 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)
OP
OP
Ffs, my update is stuck on "Getting things ready" for some stupid Microsoft Edge update. Is there any way to skip it?
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.
Thanks... and the stupid thing is currently sat trying to update Edge with status "getting things ready - 0%" for the last two hours. lol
Microsoft: "Sorry folks, we can't get you that super important security update until you download our sweet new web browser."
Good job, Microsoft.
OP
OP
I'm having the same error. If I do this, do I keep all my files or do I have to start from scratch?
This method keep all your files. Use Rufus to make the USB, launch the setup in Windows, and it (surprisingly) just works.
OP
OP
lol... this goddamn computer. Tried to delete those files, nope. Doesn't even give me an error message, just ignores me.
Going to try it via command line now. Thanks again for all the help btw. Would have probably thrown the computer out of the window by now otherwise.
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.
I'm now running version 1909 with all he latest updates, including the one in the OP. Really, thank you very much.