Known and Resolved issues for Windows 10 May 2019 Update version 1903

It is because the right hand does not know or does not care what the left hand is doing.

When I purchased my machine it was on 1709 and it upgraded from 1709 to 1803 without any problems, then we all know how 1809 acted but my machine would not upgrade to 1809 and with the spectre of 1903 approaching I used the UA (upgrade assistant) on the advice of a few learned members last month.

All has gone well with 1809 since then, except; For the past two weeks when the display will flicker when resuming to the desktop from sleep (no hibernation) and a refresh cycling of the desktop icons where all icons will blink.
My feelings are the former is related to the intel graphics and the latter is the desktop window manager process (dwm.exe) trying to keep up with what little demands I place on the system, the desktop will refresh even while sitting at idle and no programs open.

From the first page of this thread, my apologies to Kado for bringing this back up:

kado897 said:

Hmm. That's a worryingly long list of issues.

Get used to it. For every update or upgrade coming down the pike, because it is the road we have chosen to travel.

So, as far as I'm concerned you'll hear no more "bitchin" from me and I'll get there when I get there...

jimbo45 said:

Hi there.

Another issue -- if you disable Sandbox after enabling it once VMWare still doesn't work so if you use VMWare take a backup image before enabling the Sandbox which you can restore when you don't need the sandbox.

Sandboxing is a great idea -- why on earth does Ms have to make it so complicated and unfriendly to use with other popular applications.

Cheers
jimbo

From my own testing, Hyper-V is hypervisor type 1 and Virtual Box / VMWare is type 2 (check Google to learn more differences between the 2). I use VirtualBox so i will focus on that, i think VirtualBox have to be updated to support running along with Hyper-V enabled - there is an active thread on VB forum you can check, because the latest v6 should support Hyper-V but there are a few issues...
Windows Sandbox runs on Hyper-V, so if you enable any of the virtualization of Windows 10, like the also usefull Windows Defender Application Guard (that runs a sandboxed Edge Browser) other virtualization software might not run the VM's.
You can easily enable / disable the hypervisor but you have to restart Windows - you don't even have to uninstall any of the virtualization from Windows (Hyper-V, Sandbox, Application Guard, etc).
Just open administrator CMD and run:
bcdedit.exe /set hypervisorlaunchtype off
to disable Hypervisor. Restart Windows and VMWare will work.
If you want to enable:
bcdedit.exe /set hypervisorlaunchtype auto
or
bcdedit.exe /set hypervisorlaunchtype on

An advanced user can even add a Boot option when starting Windows and you can choose to have the hypervisor enabled or disabled on boot. Thats it!

Anak said:

It is because the right hand does not know or does not care what the left hand is doing.

When I purchased my machine it was on 1709 and it upgraded from 1709 to 1803 without any problems, then we all know how 1809 acted but my machine would not upgrade to 1809 and with the spectre of 1903 approaching I used the UA (upgrade assistant) on the advice of a few learned members last month.

All has gone well with 1809 since then, except; For the past two weeks when the display will flicker when resuming to the desktop from sleep (no hibernation) and a refresh cycling of the desktop icons where all icons will blink.
My feelings are the former is related to the intel graphics and the latter is the desktop window manager process (dwm.exe) trying to keep up with what little demands I place on the system, the desktop will refresh even while sitting at idle and no programs open.

From the first page of this thread, my apologies to Kado for bringing this back up: Get used to it. For every update or upgrade coming down the pike, because it is the road we have chosen to travel.

So, as far as I'm concerned you'll hear no more "bitchin" from me and I'll get there when I get there...

Hi,
Might check and see what chip set driver you now have ms standard or intel.
When you bought it I'd bet intel or amd don't know what you have

ThrashZone said:

Hi,
Might check and see what chip set driver you now have ms standard or intel.
When you bought it I'd bet intel or amd don't know what you have

Oh, it's intel:

Anak said:

Oh, it's intel:

Hi,
Is device manager showing an intel chip set driver or on IDE is it showing standard ?

Does this help?

apparently the terror of October / 2018 is repeating itself in May / 2019. The ISO MSWindows May / 2019 has been removed from the Microsoft download options.

emailx45 said:

apparently the terror of October / 2018 is repeating itself in May / 2019. The ISO MSWindows May / 2019 has been removed from the Microsoft download options.

Meh, you haven't lost anything. I personally haven't seen much improvement in 1903. Cortana still runs as a background process and this time you have StartMenuExperienceHost.exe that consumes 20+MB RAM.

WindowsInternal.ComposableShell.Experiences.TextInput.InputApp.exe never goes to suspended mode and consumes another 9MB RAM.

Boot times are also slower than 1809. 18-22 seconds vs 12-16 seconds under 1809 using conventional hard drive.

What is there for you to be angry? If this 1903 download option has been removed it means it is full of faults and shouldn't be officially published! You have nothing to regret! Personally I wished I stayed with 1809.

emailx45 said:

apparently the terror of October / 2018 is repeating itself in May / 2019. The ISO MSWindows May / 2019 has been removed from the Microsoft download options.

You appear to be using a phone, for the same 'pt-br' web address as you used, on a PC using Edge I still see the May 2019 and October 2018 updates. Looks like you have a old version of that page, have you tried clearing your browser cache?

Caledon Ken said:

Is one of them the Qualcomm drivers?

I made the error of updating the Qualcomm driver from 3.0.2.201 to 10.0.3.456, and while I could surf there were problems with accessing my Gmail over IMAP