How to get the Windows 10 May 2020 Update version 2004

bru said:

For machine B I figured I would try the MCT since it has been reported that it installs the upgrade faster. Well that was not my experience. After roughly 6 hours and still being at only 53% I cancelled it.

.... I am wondering why could I not install with the MCT?

There are two ways to use the MCT to update a machine, the first is to use its 'Update this PC now' option. That works in a similar way to letting Windows Update do the work and is generally no faster. It was this method that I suspect you tried.

The second way is to take the MCT's option to 'create media for another PC' and make an ISO file. Then mount the ISO and run the Setup.exe you'll find there to begin the upgrade. That is the fastest way to perform a feature update, but you should only use it if the machine has been offered the 2004 update in Windows Update. Doing so before you see it offered bypasses any checks for known blocking issues.

Bree said:

There are two ways to use the MCT to update a machine, the first is to use its 'Update this PC now' option. That works in a similar way to letting Windows Update do the work and is generally no faster.
The second way is to take the MCT's option to 'create media for another PC' and make an ISO file. Then mount the ISO and run the Setup.exe you'll find there to begin the upgrade. That is the fastest way to perform a feature update, but you should only use it if the machine has been offered the 2004 update in Windows Update. Doing so before you see it offered bypasses any checks for known blocking issues.

Machine B (and all of my others) was offered 2004 via WU. Since machine A took a while via WU I created the MCT on a USB stick and tried to upgrade machine B that way. I've done it in the past via MCT/USB so not sure why I had trouble. Right now it is updating through WU, hoping it works (I know it will take a while).

Ztruker said:

You cancelled it. It may very well have finished if left alone. Some have taken 9 hours or more.

Well I was going by the post about MCT being faster. So far the two machines that went through WU have taken about six hours. I was at 7 hours at 53% complete so decided to stop it. Probably should have let it continue but it was at 53% for about 3 hours.

It is currently updating through WU and it is going pretty slow.

Well its been at 73% for a few hours. Approaching 11 hours. I don't have a good feeling about this.

Steve C said:

I had previously set up to enable PUA Protection using a reg file - Enable or Disable Windows Defender PUA Protection in Windows 10 This caused the new Defender setting for PUA to show the setting as Managed by your System Administrator. I did my usual trick of toggling that setting on/off in the Group Policy Editor and rebooted which fixed the issue.

In Home you don't have the Group Policy Editor to be able to do that. If you had previously used a .reg file to turn on PUA detection then Home also shows the ' Managed by your System Administrator' message. To remove it in Home, use the .reg file from Option Four in the tutorial.

Bree said:

If you have previously enabled PUA detection then, as Brink says in Option Four, after upgrading to version 2004 you may find that Option One's 'Potentially unwanted app blocking' switch is ON but greyed out, with a 'This setting is managed by your administrator' message above it.

If so then I can confirm that Option Four's Default_allow_set_Windows_Defender_PUA_in_Windows_Security.reg will remove the message and enable the switch.

Enable or Disable Windows Defender PUA Protection in Windows 10 post #64

Well I finally got the 2004 update come to the Core2 desktop and the i3 laptop. Both went smooth and successful. I didn't time them because I was busy doing other things, so I just checked every few hrs. Happy camper.

Ztruker said:

@bru, let us know the time when it finishes.

"We couldn't install this update but you can try again 0xc1900104"

blech