How to get the Windows 10 May 2020 Update version 2004

Scottyboy99 · 28 May 2020

cameos said:

Only 2 of my 5 Win10 systems see the updates from Windows Update.

I have to go to https://www.microsoft.com/en-us/soft...load/windows10 and use the Update Assistant to update the other 3.

Seems that the amount of PCs getting it through windows updates is in the minority. Given that some much older machines are getting it ahead of many modern machines seems like it’s hard to find rhyme or reason as to why.

sygnus21 · 28 May 2020

DJG said:

Maybe it could change what the BIOS can see in the Windows partition ...

No. Remember, the BIOS doesn't need an OS, the OS needs the BIOS. And the BIOS deals with "hardware", not software. So unless the hardware was damaged or moved, the OS shouldn't say what the BIOS can and can't see. That even if a drive can no longer be booted by the BIOS because the OS hosed the boot files, as long as the drive isn't damaged the BIOS will still see the drive.

larc919 · 28 May 2020

Had to revert to 1909 on an older laptop since 2004 complained about not being unable to find some mysterious device driver every time it started. The update isn't being offered to it on WU anyway, so maybe it's something that will get fixed somewhere down the road.

Ex_Brit · 28 May 2020

That was exactly what I got too. But the ISO installed OK on my spare HDD, so I suspect it doesn't like some software I use in my main OS.

DJG · 28 May 2020

But why then does my BIOS over the years has changed its BIOS boot options based on different Windows releases on the same drive? Sometimes it only showed the SSD as a boot option, other times it showed the SSD and a Windows Manager boot option? There's got to be some sort of interaction somewhere ...

There's a firmware Boot setting called Secure Boot which allows you to set UEFI or Other OS as a boot option. When this morning the Windows Manager boot drive option disappeared I had to boot the SSD as Other OS to get Windows up. Only after I used Paragon HD Manager's feature to clear the UEFI cache was I able to boot using the UEFI firmware option.

OldGuyFromCdn · 28 May 2020

Wasn't offered via WU so I dl'd it via MCT and installed this morning. It messed up some of my settings but once I redo those and clean up I might regain some space. Got a 1909 image from 2 days ago in case things go south. All in all not too shabby.

Brink · 28 May 2020

Updating to Windows 10, version 2004 on devices with Hypervisor-protected code integrity (HVCI) enabled

CountMike · 28 May 2020

DJG said:

But why then does my BIOS over the years has changed its BIOS boot options based on different Windows releases on the same drive? Sometimes it only showed the SSD as a boot option, other times it showed the SSD and a Windows Manager boot option? There's got to be some sort of interaction somewhere ...

There's a firmware Boot setting called Secure Boot which allows you to set UEFI or Other OS as a boot option. When this morning the Windows Manager boot drive option disappeared I had to boot the SSD as Other OS to get Windows up. Only after I used Paragon HD Manager's feature to clear the UEFI cache was I able to boot using the UEFI firmware option.

Possible explanation, UEFI usually shows "UEFI boot on disk... such as such " in BIOS boot order list and ignores other non-bootable disks.

Emer · 28 May 2020

Is it possible BIOS can't see the drive because the version is not compatible with pc/laptop?
I mean we need to upgrade (or maybe downgrade) the version of the BIOS?

Sometimes it happened when we get bios upgrade from windows update.

DJG · 28 May 2020

CountMike said:

Possible explanation, UEFI usually shows "UEFI boot on disk... such as such " in BIOS boot order list and ignores other non-bootable disks.

That was the definite behavior until now. Now I show no boot options, but it handles boot properly.

- - - Updated - - -

Emer said:

Is it possible BIOS can't see the drive because the version is not compatible with pc/laptop?
I mean we need to upgrade (or maybe downgrade) the version of the BIOS?
Sometimes it happened when we get bios upgrade from windows update.

It does boot, so it must see something :)