Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Windows 10 May Update (1903), any known issues?

May 24, 2019 3:50PM PDT

I believe Windows 10 May Update (version 1903) is available to most now. For those who are daring enough and have no fear of being ahead of the crowd and have already updated your system with it; curious minds want to know. Have you run into any issues or snags that we the not-so-daring group should be aware of? Would you overall recommend the update, or would you say to hold off on it? Anything you can share about your experience with it will be helpful to us. Thank you in advance!

-- Submitted by Ben C.

Post was last edited on May 31, 2019 1:12 PM PDT

Discussion is locked

- Collapse -
None Here, But Only Three Comps On Network
May 31, 2019 5:19PM PDT

I also previously had some issues on our home network with the earlier Win10 update/upgrades but this time, I've had no problems. But it's a simple network, with a common workgroup name, (not a "home group", which has been eliminated), with two test Win10 V1903 Pro computers and one Windows 7 Home on it. File sharing, printer sharing with one printer on a Win10 computer, and such have worked fine this time but all sharing is standard stuff with all machines using the same user login with admin rights.

Hope this helps.

Grif

- Collapse -
Worked OK on VR machine
May 31, 2019 5:15PM PDT

I installed it two days ago on the PC I use for VR and was surprisingly/happily not impacted by the update, 1809 to 1903 on Win10 Pro.

This machine runs Steam plus all the Vive and WMR software and has a GTX 1080ti with up-to-date Nvidia drivers, so I was happy there were no problems to interfere with my playtime.

The updates were pretty time consuming IIRC, I had some other stuff to work on while it updated. I believe it took about an hour,on an 8700K using an Intel M.2 drive as boot device.

The only time I got concerned was when the video blacked out for a couple minutes but I was still seeing disk activity and when it came back it said the install would reboot a number of times, which it did. As I said, my video drivers were already current before I started the update.

After the 1903 update it wanted to do Flash and .NET updates and those also completed successfully.

I checked the networking that a previous post asked about and my shares hosted on that machine are still working as well as a number of shares where it is an SMB client to a NAS and those are fine, too.

I also checked the time setting that another poster mentioned and mine worked first try, but I am using Windows time server, not NIST.

My report is thumbs up.

- Collapse -
On Previous Semi-Annual Updates
May 31, 2019 5:58PM PDT

Some users "watched" the update and didn't like seeing a BLACK SCREEN and powered off the computer. Killing these updates in the middle have been traditionally bad news. So, in one discussion on a previous updates, one of the conclusions were that "IMPATIENCE" was a cause of issues. Like you, I checked the disk activity light and just casually monitored the black screen and it was black for an hour or so. It's not really the users' faults here. MS should have done a better job of communication with the user as to how much time has elapsed, how much time to go (progress bar?) and no black or weird screens that casual users will interpret as an error. I usually post about it so some people will remember not to jump to conclusions about the state of the upgrade. As it is, some people think the upgrade should be 10-20 minutes but this is more intensive that a complete reinstall of windows as it tries to keep settings, installed programs, files, etc. Pulling the plug could put these in jeopardy. My timing/experience was from about a year ago. I.m waiting to see what others come up with since my other PCs are down.

- Collapse -
Windows 10 1903?
May 31, 2019 6:32PM PDT

I installed 1809 a couple of weeks ago and almost everything that I have checked seemed to work OK. Occasionally I still have Window 10 losing track of my external hard drives and they don't even give a warning. At times I have been able to remove and reapply the power, but sometimes that doesn't work and I have to do a manual Restart. The drive usually show up then. I have I have a G drive (external) that I do back ups to and am using AOMEI and unfortunately it seems to start up without checking that the drive is present. It fails, and then after I get the computer restarted and the external drives are recognized, I have to rerun the program. I have had missing drives fairly often and usually have to restart the computer to get the drives recognized. I thought that Microsoft had solved this problem, but seems not. Normally I am not using the external drive except for back up, so don't always notice.

- Collapse -
If You Decide To Install V1903, Unplug ALL USB
May 31, 2019 6:53PM PDT

Unplug all USB devices before the installation and things will go better. This has been an known issue since the first Windows 10 update/upgrades and it's why unplugging USB when performing the update is the best method forward..

Hope this helps.

Grif

- Collapse -
By Hforman's article above.
Jun 1, 2019 5:14AM PDT

.
6) DISM and SFC: These check your system as far as your Windows Image and your system files. You may want to run this set a couple of times:
Go to command prompt (Admin) by right-clicking the start button then left-clicking on Command Prompt (Admin). I'm running the pro version so the home version may be different. then --

DISM /Online /Cleanup-Image /RestoreHealth ; correct
SFC /CHECKNOW ; incorrect

Both take a while
..
Correction:
Sfc / scannow (Sfc /checknow is wrong !!!!)

- Collapse -
Thanks
Jun 2, 2019 11:20PM PDT

I can't believe I must have had a brain fart while typing that. You are absolutely correct:

It should be sfc /SCANNOW

No idea where my brain picked up that wrong. I apologize to everyone!

- Collapse -
1809 to 1903 would not update. 1803 to 1903 Settings Errors
May 31, 2019 9:05PM PDT

I had a desktop and laptop fully patched and updated with Win 10 1809. Using windows update, 1903 would download and install, then say that the update failed. It tried 6 times on each computer and gave up. I finally downloaded 1809 using MediaCreationTool1903.exe and was able to update both. My wife's desktop running a fully patched and updated Win 10 1803 updated fine with windows update......however, the Settings "Apps & Features" would load then disappear immediately. Then when the computer was idle, I would get the BSOD with "Critical Process Died" error. I tried updating with MediaCreationTool1903.exe and had the same problems. I tried updating from 1803 to 1809 using the MediaCreationTool1809.exe which fixed the Settings "Apps and Features" issue, but the BSOD Critical Process Died continued. Thank goodness I ran my Acronis Backup prior and just restored my drive. 1803 runs fine so I will continue to use it for the foreseeable future. I WOULD NOT UPDATE TO 1903 RIGHT NOW. Too much of a crap shoot!

- Collapse -
No Idea Why You'd Get Those Errors
Jun 2, 2019 11:25PM PDT

Those type of things are usually caused by KILLING an update before its finished (previous update) or trying to run apps while the update is still going. Do you have any background jobs that run?
Since you reverted back, Go into settings --> Update & Security --> View Update History and check to see if some previous update failed. I had one over a year ago because some of these updates "sneak" in and I power off my machine when not in use. You might want to run a virus check too.

- Collapse -
Takes its time ...
May 31, 2019 11:18PM PDT

Started the update last night at 8.30pm, did the so far final restart this morning at 7am; took about five hours to get everything ready, then largely went its way. i5-2450 w. 8GB ram and 500GB HDD. The 'install overnight' option is the obvious way to go, it seems.

- Collapse -
Yes, It Does!
Jun 2, 2019 11:27PM PDT

I don't remember which semi-annual update it was (probably a year ago) and it took well into the next day. My config is about the same as yours except 12 GB RAM and 1 TB for drive and most of that available.

- Collapse -
Windows 10 Update (1903), any know issues?
Jun 1, 2019 3:44AM PDT

I have updated on 3 desktops and two laptops, and have no issues whatsoever. I made sure that there were no USB storage devices attached. My computers are a mix of Windows 10 Pro and Home. I can happily report not a hitch in sight.

- Collapse -
"Update AND DON'T" Approach
Jun 1, 2019 4:50AM PDT

I haven't tried the update yet, but one thing to always keep in mind ...

Pretty much anyone in this forum has quite a few spare disks lying around that still work. And nowadays drives are pretty inexpensive.

If it won't involve major surgery, clone the disk(s), make sure the clone(s) work, and then upgrade one set. Even if something totally screws up--you can just pull the upgraded set and put back the one you didn't upgrade.

Keep in mind that often some older software might see a different O/S version as a new install--and not reactivate on the upgrade because "number of activations exceeded" or the activation server is no longer online.

I ran into that recently when I upgraded a PC from Win 7 to Win 10. Particularly with lower-price non-major brand software, often the company only supports the current and two previous versions. If you contact them about "activations exceeded" for an older version, their response is "we no longer support that, we suggest you upgrade"--they won't offer to change your account for more activations.

- Collapse -
One nagging issue so far
Jun 1, 2019 2:36PM PDT

I always start with my oldest and most disposable computer, a Lenovo Thinkpad X201 with 8GB and an SSD, when I install the latest and greatest Windows 10. With EVERY version, Windows 10 insists on installing the Synaptics touchpad driver, which is absolutely flaky. I uninstall it and revert back to the standard PS/2 mouse driver and all is well again. This is a minor annoyance in the grand scheme of the world, but why can't Microsoft and Synaptics get it right? This is yet another example of flawed quality assurance in Microsoft land.

- Collapse -
Sorry but you are thinking of Microsoft
Jun 1, 2019 2:46PM PDT

As the company that deals with getting the drivers right. It's been decades and not perfected. Why is this a Microsoft issue since they never claimed to have fixed this and all the hardware makers keep web sites full of drivers?

I see this misconception with newer users. Not so much with those that have been on this ride for decades.

- Collapse -
Automatic Updates?
Jun 1, 2019 8:34PM PDT

Can auto updates be disabled only in Win 10 Pro?

- Collapse -
You Mean PAUSED
Jun 2, 2019 11:40PM PDT

In Win 10 Pro you can PAUSE updates, but eventually it will go back to automatically downloading. There are a few techniques out there aside from this like telling Update not to download over metered connection (no idea if available to the home edition).

- Collapse -
Mostly a smooth installation, but with one catch
Jun 2, 2019 2:44AM PDT

My upgrade from 1809 Pro largely went without hitches - there were no Blue Screens on the restart sequences as I came to anticipate on previous upgrades.

It did take a couple of hours though from start to finish by using the Upgrade Assistant, also a good thing as up to 1803 I typically had to use the Media Creation Tool.

I had no external drives attached and would have removed them anyway, but I did read somewhere that some models of internal drives can also be affected?

Now for the catch and yes, there is always one! For some reason after initiating a Skype call to a blind friend of mine who needed remote assistance on his laptop, my USB microphone/webcam stopped working. After the session I looked more closely to find out what was going on.

Admittedly the webcam/microphone is quite old (Logitech Pro 9000), so figured it down to age/support and that I might just need to get a new one. But then I checked the microphone properties (Settings > System > Sound > Microphone 'Device Properties' > Additional Device Properties) and selected the 'Listen' tab. This allows you to check that your microphone is working by applying the audio output and listen while you speak. It worked for me, so I knew at that point a new microphone was not needed.

I then headed to Settings > Privacy > Microphone. Skype was not listed at all, nor were other applications that I frequently used. There is a message that says that some applications may not be listed, which is fine - but, Skype? That IS odd.

So I reinstalled Skype, even if it was not Skype's fault. It was the Windows installations fault for not copying over the settings correctly. Lo and behold it worked, so I reinstalled my other apps too.

Everything since has run smoothly, touch wood!

- Collapse -
May 29, 2019—KB4497935 (OS Build 18362.145) beware
Jun 4, 2019 7:24AM PDT

I installed version 1903 on two computers without a hitch. But then when I installed the 1903 update May 29, 2019—KB4497935 (OS Build 18362.145) and tried to reboot each computer booted to a blank screen and never completed loading. I had to go thru getting into safe mode on each computer and do a system restore to be able to boot each computer again. Since I had chosen to voluntarily install 1903 since is was not presented to me I then chose to to uninstall version 1903 until it was presented to me as an option. Beware of May 29, 2019—KB4497935 (OS Build 18362.145). You may pay the price.

- Collapse -
Black Screens
Jun 4, 2019 8:39PM PDT

While I have not received 1903 yet, every semi-annual update I installed showed a black screen for 1/2 to one full hour as part of the update. While you and I might not consider this "normal", I have seen it in the past and the correct response was to just leave it.. Shutting down the computer in the middle of these semi-annual updates is not a good idea. A check of the HDD light blinking usually tells you things are still going.
I'm not saying this is true in your case, but I have seen it in past updates.

- Collapse -
Update
Jul 2, 2019 10:17PM PDT

I almost forgot. Yes, I did install 1903. It went FINE. Did my screen go black? Sure it did. I don't like that the Microsoft talent thinks this is OK because others see a black screen, panic, and "pull-the-plug" (or, hold the power button). Making things worse. In this particular case, I moved the mouse around and did a couple of double-clicks and the screen came back on. But I have seen where this doesn't work. Patience solves that, as long as the HDD light is flashing or on.

- Collapse -
I tried 1903
Jun 4, 2019 5:40PM PDT

and went back to 1809.

The problem was Nvidia control panel stopped working. It's mentioned in the Nvidia forums.

After a short time the image on the monitor loses color and turns gray. Trying to adjust desktop colors with the the control panel causes it to crash.

Apparently Nvidia and Microsoft are aware of it and are working on a fix.,

- Collapse -
It has been fixed.
Jun 7, 2019 1:13PM PDT

Nvidia issued a hotfix driver that updated the 430.86 driver to 430.97.

I installed the dch version along with the Nvidia control panel app from the Microsoft store as this is the wave of the future. Windows 10 was upgraded to 1903 and everything is fine.

- Collapse -
Sync account
Jun 7, 2019 1:34AM PDT

not sure if anyone is having this issue but ever since updating to the May 2019 update I cannot sync with my Microsoft account anymore. I'm not sure why or how, and I don't understand why I can't fix it if I am the system administrator on this laptop. It makes no sense.

A Microsoft support agent told me to do an "in-place windows 10 upgrade" which did not fix the issue.

I see that there's also an issue with mounting drives on this version (have not experience but will remember as my brother has a PC with more than one internal drive). There's always some kind of issue with these updates, isn't there? :/

- Collapse -
What about INTERNAL volumes?
Jun 30, 2019 12:07AM PDT

What about internal hard drives, and/or partitions within the same physical boot drive? You can't "just" remove them because Windows Installer is too thick to figure it out, especially when adding an extra "reserved" partition.

What if you have shell folders mapped to other volumes and/or drive letters? You can't "just" remove those, else Windows will get even more screwed up.

This problem is old, and predictable, and lies in the difference between what the installed OS sees (including registry references that override default letter allocations) and what is deduced when booting without access or reference to the installation's registry. As the installation process crosses from installed to new-boot phases, so arises this risk.

I've seen similar behavior when SysPrep runs on a system where the boot partition is not the partition marked Active (as can happen when using non-standard MBR boot managers such as PloP).

Until I know this is properly fixed (and beyond just "oh we check for removable drives now... oh yeah BTW also affects internal drives") I'd hold off 1903 - if that's possible. What worries me is that of the 6% or so Win10 that is 1903 right now, 65% were "upgraded" from 1809 - which suggests that although 1809 should still be supported, those systems are getting "pushed" into 1903 by WU?

- Collapse -
You Don't Need to "Hold Off"
Jun 30, 2019 12:46PM PDT

Assuming it is not already fixed, having the additional drive letters does not cause an issue that will mess up your computer. If it is an issue, you simply get a message about it not being able to do the install. It doesn't "break" anything.

- Collapse -
If You Allow The 1903 Upgrade To Install The New Updates...
Jul 2, 2019 3:35PM PDT

..which happen during the update/upgrade installation, then the latest updates should fix the drive letter problem. When I first did the manual installs of 1903 on some test machines, the latest updates that "fixed" the various known issues were NOT part of the installation. Now they are. On my latest 1903 install last week, I checked the computer's Windows Updates section and it had already detected the availability of the new version but it wasn't "pushed" into the update. But instead of using the online installation from the computer's Windows Updates section, I downloaded the ISO from the Windows 10 Media Creation Tool, mounted the volume, then ran setup.exe from within the ISO. During the install, it asks if you'd like to include any new updates during the install and I allowed it to do that. After the install was finished, which included the newest updates to version 1903, the version number 18362.175 is the same as my first test installs which received the latest updates afterward.

There are no guarantees here, it's Microsoft, but I've now updated 5 or 6 computers and they've all been fine. Still, if you happen to have any USB connected devices, disconnect them before the update. No reason to test fate.

Hope this helps.

Grif

Post was last edited on July 2, 2019 3:43 PM PDT

- Collapse -
Windows 10 1903 update
Jul 8, 2019 6:13AM PDT

caused links in outlook mail to not work!

- Collapse -
Have You Tried These Fixes For That Problem?
Jul 8, 2019 3:48PM PDT

I"ve not see this happen on any of our computers here, which are now using Windows 10 V1903 and Outlook 2010.

But....This usually occurs because Internet Explorer needs to be re-set. So open the Control Panel, then the Internet Options icon, then the "Advanced" tab, then click on the "Reset" button.

If that doesn't work, you can change the default browser to something different, such as Firefox, etc.

Other fixes are in the links below:

https://www.timeatlas.com/outlook-hyperlinks-fail-to-work/

https://support.microsoft.com/en-us/help/310049/hyperlinks-are-not-working-in-outlook

Hope this helps.

Grif

Post was last edited on July 8, 2019 3:49 PM PDT

- Collapse -
Great Points!
Jul 8, 2019 6:13PM PDT

And that brings up the point that most people should NOT be clicking any links in an email in the first place. I had an email "from my bank" and had a click to see your account-type of link, but, I thought about it at the last second and it turned out to be an almost perfect PHISHING email. the first link above carries the point that the email MAY have been a phishing email, along with all of the other suggestions in there.