Known and Resolved issues for Windows 10 May 2020 Update version 2004

This update typifies Microsoft's management ethos - If it ain't broke then break it!

Bree said:

Yes, it did.

Still here.

UPDATE 6/9:

Current status and known issues have been updated for Windows 10 version 2004. See first post for more details.

Tweet

— Twitter API (@user) View on Twitter

Brink said:

UPDATE 6/9:

Current status and known issues have been updated for Windows 10 version 2004. See first post for more details.

Thanks Shawn
And I see they have been busy beavers. There is another networking issue that I hadn't seen before that was also mitigated.
Progress! Glacial - but progress!

*** UPDATE **** see below.

First off, sorry for the long read, but history is important.

For the very first time since the first release of Window 10 (in 2015), I had to use Macrium to restore to the prevous release (1909) due to several major in my mind issus.

On the 28th of May I downloaded 2004 and installed/updated it into my Hyper-V test system 2004. When 1903 came out I started with a clean copy of 1903 and have since installed a few apps that I need on a daily basis and it has been upgraded to 1909 18383.836. For about 4 days I tested 2004 and found little to no problems.

On 06/04/2020 I decided to apply 2004 to my backup test laptop which was at 1909 18383.836. I did try something new to me, was to apply 2004 via "Windows Upgrade Asst". Worked great (but it does take a bit longer since it has to actually download the code again). The install took right around 30 minutes (You can see the devices specs in my system 2 configuration). I really only found 2 issues. 1- It must of turned OFF in Windows Defender "Virus protection for Browsers" since it was on before the update ? and 2- That Old, old problem from several feature update ago where if switch to another desktop and return, I scrambles the location of many desktop Icons ? I found it happens with DOSBOX (Since I run it in Fullscreen not in a window). Running DOSBOX in a window seems to not bother it.

Nothing really serious jumped at me and it is right now stll at 2004 19041.264.

Early Sunday morning 06/07/2020, I decided to upgrade my Desktop which is normally used Daily. Totally different hardware, but has been a reliable workhorse since it was built and first installed with I believe 1603. The install was performed via Mounted ISO, took just under 30min. No errors were reported and I figured I would be to go. Since I was using the Laptop for the last 3 days, I copied the data files to the Desktop needed for my daily work. I tested it for "ICON scramble", of which it did none (need to still address that issue on the laptop). On Monday morning, I did what I normally (Issue a couple of Stock trades, Checked all of the markets that are open, but ours our still closed (one can gleam future activity based what is happening elsewhere during their day).

There were a couple of things that were really good. 1- Since an early CU in 1909, SFC /scannow began to fail every time it was run. That CU did something bad. I never was able to fix it and since the system accepted daily Win Updates, I stopped trying to fix it. Well the upgrade to 2004 fix all of the problems that I had there. 2- early on 1909, there was a CU that busted Event Viewer. Mine was busted. MS had a fix that I appled (register zaps), and it worked. Shortly there after another CU came along and Event viewer was again broken. At that point I threw my arms up and if I needed to view Even Viewer, I went there indirectly via "Computer Management". I grew tired of messing with it. Well 2004 fixed Event viewer". Also I noticed that both the Laptop & the desktop nolonger shows in "Disk Management", the portable base layer. Horray !

Now for the real problem and the reason I reverted back to 1909. Early Monday I had an appointment and I place the system in "Sleep" mode (As I have always done). Upon returning I pressed the pwr button and nothing happened ? No matter what I did, System Rest Button no workie, It was LOCKED SOLID. Basically had to unplug it from the wall, so I could power it back up. I searched could not find any reason for what happened. There are no dumps, no nothing. I ended up chalking it up to a freak issue. Later on Monday, I went to the kitchen to have some lunch. Upon return (20min later), the screen was blank (as it should be), I rattled the mouse and nothing happened, pressed the power button and nothing happened. It acted just like the earlier episode when I placed the the system in sleep mode. Again required a unplug from the wall. Note that this system never sleeps unless I request it. All of the power mgmt setting have "NEVER SLEEP" set. I verified that the settings were still in place and they are.

I decided that this problem could be worked around (Set it to never enter screen save mode and never put in Sleep mode). However, I felt it was to much of a problem for me and 1909 went back this morning. Also I don't believe that this same issue exists in the laptop, but I will test it soon.

****** UPDATE *******

I ran the laptop which has had 2004 installed for 7 full days. The purpose was to test the SLEEP functionality that had failed on my Desktop. It past all test. No hangs, did exactly what it should do. The laptop obvious has battery, so it has different settings battery management when running on battery. I also tested all functionality under shore power, and NO problems.

I guess the problem maybe due to the hardware on the desktop.

No winners or losers.