Windows 10 May 2020 Update 20H1 RP build 19041.207 - April 16 Insider

So is this just the same one that was released into the Slow ring earlier in the week?

Or did they change/fix anything before they dumped it off into the RP ring?

Just wondering if I need to bother installing it again or not. Or if its the same one.

peace
wanna

Wannagofast said:

So is this just the same one that was released into the Slow ring earlier in the week?

Or did they change/fix anything before they dumped it off into the RP ring?

Just wondering if I need to bother installing it again or not. Or if its the same one.

peace
wanna

Hello wanna,

Correct. This is the same build from the Slow ring now released to the Release Preview ring.

Updated to it today on my baremetal machine(as opposed to one of my VM's), the upgrade went very good, just like mentioned above it took quite awhile. One hour, and on my machine, I mean in a VM it goes much faster, but on baremetal upgrade.exe needs to move all my different OEM drivers(files, folders, registry settings, driver settings and so on) back and forth, so of course it takes much longer.

Both the on-line and the off-line portions of the install took it's sweet time at 88%, guess that's why it's called in-stall, because it stalls for a while

But; any how all my settings were taken over to the new version, and I only needed to mess with settings for the new stuff.
Oh wait! My search setting reset from enhanced back to classic(the default) and I needed to click an option to set it back, how horrible, who makes this stuff

Brink said:

Hello wanna,

Correct. This is the same build from the Slow ring now released to the Release Preview ring.

Cool beans. Thank you sir.

peace
wanna

That's why I did a clean install. Well, it can only get better like aged wine. Naw, bad analogy. Wine really does get better.

Kaliaila said:

Just installed this update over night, and I woke up this morning to find that my keyboard and mouse were not powering back on at the end of the start up process.

To be more clear:

1. Turn on computer which opens up to Asus Express Gate for 3 seconds, then continues to POST. (Keyboard and mouse work).
2. Keyboard and mouse turn off for short time but start up again to trigger BIOS entry.
3. POST completes and Windows starts to load. Keyboard and mouse turn off again.
4. Windows finishes loading bringing me to the Log in screen, but keyboard and mouse are still off, eventually monitor goes to sleep and cannot get it to wake up, because the keyboard and mouse are not active.

I think that this has happened in the past, but it has been quite a while, so I don't remember how I fixed it. Has anyone else ran into this?

Can you check to see if "Allow this device to wake the computer" has a tick before in Power Management window.
1. Right-click the Windows button at the far left in Task Bar and click on "Device Manager"
2. In Device Manager, under "keyboard" and "Mice and other pointing devices" right-click each device and open the properties dialog box.
3. Under the "power Management" tab, make sure the "Allow the device to wake the computer" has a tick before it (red arrow in the screenshot below). You will have to go through the same procedure for each device.



------UPDATED------

In case the above instructions didn't fix your issue, you can try the same "Allow the device to wake the computer" in BIOS/UEFI settings under Power Management. Or better yet, you can go for the same steps as above for USB Root Hub, but this time around, you will have to untick "Allow the computer to turn off the device to save power" under Power Management tab as illustrated in the following screenshot:



Really hoping that helps.

Cheers!

By the way after upgrading you get a new Windows RE(Recovery Environment) .wim file and if you use Macrium Reflect you may want to update the Windows Boot Menu recovery and your USB

dany007119966 said:

it is ok it makes mi this iso

19041.207.200409-1713.VB_RELEASE_SVC_PROD1_CLIENTCORE_OEMRET_X64FRE_SK-SK.ISO

but instalator showing license information and up is june 2018 ??

From the name it looks like the correct iso. Don't know about the date on the licence information. Maybe that was the last time the licence terms were updated.