Windows 10 version 1903 'May 2019 Update' now released

[Breelander]

The next version of Windows 10, version 1903, build 18362, has just been released.

https://www.microsoft.com/en-gb/softwar ... /windows10

To accompany this release, new cumulative updates have been released for 1803 and 1809. These add new control over Features Updates making them optional for both Home and Pro users. Windows update will still notify you when your machine is ready for the 1903 Features Update, but you now can decide if/when you want it. This is the 1809 cumulative update.

Starting with update KB4497934, we are introducing functionality that allows you to decide when to install a feature update. You control when you get a feature update while simultaneously keeping your devices up to date. Feature updates that are available for eligible devices will appear in a separate module on the Windows Update page (Settings > Update & Security > Windows Update). If you would like to get an available update right away, select Download and install now. To find out more about this feature, please go to this blog.

https://support.microsoft.com/en-gb/help/4497934

The one for 1803 is KB4499183. If you decide you don't want to 'Download and install now' you can continue to check for updates and keep your 1809 or 1803 fully up to date with all the latest cumulative updates for your version.

Only when your version is near the end of support will the Features Update be installed automatically. For 1803 end of service is November 12, 2019.

https://support.microsoft.com/en-us/hel ... fact-sheet

[Breelander]

There is a known issue in build 18362.116 that will not allow you to do an in-place upgrade while a usb drive is attached. The Catch 22 is that if you used the Media Creation Tool to make an install USB then your setup files are on a USB that must be connected! There is no such problem if you use the MCT to make an ISO, then mount then ISO to perform the upgrade (removing any other usb drives while you upgrade, of course).

If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating "This PC can't be upgraded to Windows 10." This is caused by inappropriate drive reassignment during installation.

Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H).

https://docs.microsoft.com/en-gb/window ... 442msgdesc

If you chose to make the install USB then a workaround, if you have enough space, is to create a temporary folder (anywhere on your HDD will do) then copy the contents of the install usb to this folder. Remove the usb then run Setup from the temp folder and it should allow you to upgrade. You can delete the temp folder when done.

This issue is expected to be fixed in the next cumulative update for 1903. After that, if you let Setup check for updates as part of the upgrade (this is the default) then it should complete successfully, even if using a USB to do the upgrade.

[supremetwo]

Install error three times:-

Installation Failure: Windows failed to install the following update with error 0x80071A30: 2019-05 Cumulative Update for Windows 10 Version 1809 for x86-based Systems (KB4497934).

Current version is:- 1809 17763.504

[Redmires]

I had the same install problem twice. It installed ok on the 3rd attempt. I can't understand why it has to download it from scratch every time as a 4Gb download on a 2.5Mg broadband connection isn't ideal.

[Breelander]

Install error three times:-Windows failed to install the following update with error 0x80071A30...

...I can't understand why it has to download it from scratch every time as a 4Gb download on a 2.5Mg broadband connection isn't ideal.

It's not entirely clear what the error code 0x80071A30 means, but it has been around for a LONG time....

Windows Server 2008 R2 updates fail - error code 80071A30

https://social.technet.microsoft.com/Fo ... serverwsus

Windows Update is not the most reliable way to upgrade Windows. A more reliable method (and one that only needs the one download which can be kept for re-use on this or other PCs) is to use the Media Creation Tool to download the ISO. In Windows 10 you can mount the ISO by double-clicking on it then run Setup from it to start the upgrade.

Get the MCT from Microsoft here (the 'Download tool now' button) then run it, select 'Create media for another PC' and select 'make an ISO'.

[Infrasonic]

I'd second the MCT route for feature updates.
I've done online via Windows Update, MCT in place upgrades ( and clean installs) over the years on a few machines and the MCT route is far quicker.

On a decent specced machine with SSD and fast USB ports (3.1 and up) and branded higher spec USB flash drives, the difference is quite marked.

I suppose if you have a really good FTTP ISP connection *(1Gb/s symmetrical say) then it starts becoming more moot (although the server load/contention ratios at the Microsoft end will be relevant there especially during peak USA hours. I generally do large online upgrades around 6am GMT as I also get more Three ISP 4G bandwidth allocation then).


*A friend has the Hyperoptic 1Gb package and despite my initial skepticism he does consistently get very close to 1Gb each way.

[production100]

Installed today. Same problem with every feature update - it removed the Intel Raid programme and also removed the windows 7 games. Both reinstalled ok.

It seems to have re-introduced the problem where it creates a second ethernet network which has no internet access and randomly chooses which network setting to select when starting from a shutdown. Sometimes it chooses 'Network' which works perfectly, and sometimes it chooses 'Network1' which does not.

Have gone into the registry and deleted Network1, however when it feels like a change it suddenly decides to re-create Network1 with the same problem of no internet access.

I have seen this same problem on a clean install of windows 10 with nothing else installed, where you install it and it sets up 'Network', but when you then change it to be a private network it sets up 'Network' as a private network, but also sets up and additional 'Network1' with no internet access.

Apart from that it seems to work as before. Still has network problems where networked pc's do not show up in File Explorer. Even though you can connect to them...

Chris

[Breelander]

According to this Tweet by Mike Ybarra, Microsoft's Corporate Vice President of Xbox Program Management...

https://twitter.com/XboxQwik/status/1136790864586366976

..as of today 7th June, a manual check for updates in Windows Update will find and show the 1903 Feature Update as available (provided there are no known blocking issues for your particular PC model).

If your 1809 already has the 21st May update KB4497934 to build 17762.529 the feature update will be optional, nothing will happen unless/until you click 'Download and install now'.

[Julian]

Windows Update is not the most reliable way to upgrade Windows. A more reliable method (and one that only needs the one download which can be kept for re-use on this or other PCs) is to use the Media Creation Tool to download the ISO. In Windows 10 you can mount the ISO by double-clicking on it then run Setup from it to start the upgrade.

And from your subsequent post (with my bolding)...

According to this Tweet by Mike Ybarra, Microsoft's Corporate Vice President of Xbox Program Management...

https://twitter.com/XboxQwik/status/1136790864586366976

..as of today 7th June, a manual check for updates in Windows Update will find and show the 1903 Feature Update as available (provided there are no known blocking issues for your particular PC model).

Does the MCT route still check for blocking issues at installation time or is that implemented somewhere in the interaction between the Windows Update client and the update servers where the servers decide whether to even make an update visible to the client hence downloading the update using MCT might bypass that check?

I'm quite surprised, given that I have an about 8 month old system from what I assume is a reputable supplier (Intel) which is still (I just checked) the most recent high-end i7 NUC that one can buy, and yet my manual check-for-updates just now still tells me that since I am running 1803 I already have the latest version installed and there are no updates available to me. I'm not even seeing 1809 let alone 1903. If there are still blocking issues on my system it's rather disappointing that a company of the size and stature of Intel hasn't been able to work more closely and determinedly with Microsoft to keep its most recent platforms up to date with the latest Windows releases.

- Julian

P.S. As an irrelevant aside, when I went to the intel NUC page just now (https://www.intel.co.uk/content/www/uk/ ... /kits.html) to check that my system was still the latest model I got a bit of a shock when looking at the first couple of systems Intel lists on that page, i.e. the first on the page, the "Intel NUC Kit NUC5i3RYHSN". I had a brief moment of extreme confusion - could Intel really be selling Ryzen-based systems now? What is going on in the universe? Obviously the spelling is quite different and there is "i3" clearly in that NUC's model number but I confess that it did catch me out for just a couple of seconds .

[Breelander]

Does the MCT route still check for blocking issues at installation time or is that implemented somewhere in the interaction between the Windows Update client and the update servers where the servers decide whether to even make an update visible to the client hence downloading the update using MCT might bypass that check?

The MCT bypasses those checks, it does check for hardware/software compatibility but not known blocking issues. Windows update, either the automatic or manual check, will take into account known blocking issues. A manual check will declare you as a 'seeker' and can find the features update sooner than the automatic check. It will also find any optional cumulative updates (these have no new security fixes and may be issued in the 3rd/4th week of the month), while the automatic check will only find the mandatory updates (those issued on Patch Tuesday, the 2nd Tuesday of the month).

[chas49]

Does the MCT route still check for blocking issues at installation time or is that implemented somewhere in the interaction between the Windows Update client and the update servers where the servers decide whether to even make an update visible to the client hence downloading the update using MCT might bypass that check?

The MCT bypasses those checks. Windows update, either the automatic or manual check, will take into account known blocking issues.

So, if a manual update check does not present 1903 as available, that means (presumably) that there's a blocking issue on your machine and it would be unwise to use the MCT route?

[Julian]

Does the MCT route still check for blocking issues at installation time or is that implemented somewhere in the interaction between the Windows Update client and the update servers where the servers decide whether to even make an update visible to the client hence downloading the update using MCT might bypass that check?

The MCT bypasses those checks. Windows update, either the automatic or manual check, will take into account known blocking issues. A manual check will declare you as a 'seeker' and can find the features update sooner than the automatic check. It will also find any optional cumulative updates (these have no new security fixes and may be issued in the 3rd/4th week of the month), while the automatic check will only find the mandatory updates (those issued on Patch Tuesday, the 2nd Tuesday of the month).

Thanks. There must be some blocking issue/issues on my pretty new Intel NUC then because even a manual check-for-update still shows 1803 as the latest build supported by my system. Disappointing.

Edit - just saw your reply chas. I had come to the same conclusion. Thanks.

- Julian

[jackdaww]

re blocking issues .

is there a way of finding out if they are present on ones PC.?

thanks.

[Breelander]

So, if a manual update check does not present 1903 as available, that means (presumably) that there's a blocking issue on your machine and it would be unwise to use the MCT route?

Not necessarily, the rollout is phased, so it may just be that the MS update servers have not decided its your 'turn' yet. Only one out of my four machines I have upgraded with an MCT ISO had shown the feature update as available in windows update. All upgraded to 1903 without a problem.

If using the MCT it is always a sensible precaution to make a system image first with something like Macrium Reflect Free, but I've not needed to go back to the old system on any machine I've upgraded.

[Breelander]

re blocking issues.
is there a way of finding out if they are present on ones PC.?

Not by directly testing the PC, but known issues for 1903 are listed here:

https://docs.microsoft.com/en-us/window ... ws-10-1903

If the issue is significant enough to warrant a block the 'Issues details' section for that issue will say...

...To safeguard your update experience, we have applied a compatibility hold ... from being offered Windows 10, version 1903, until this issue is resolved.

...and/or

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

[supremetwo]

New issue - latest update causes event viewer errors.

https://borncity.com/win/2019/06/12/win ... nt-viewer/

Don't use it much so I'll wait and see if MS fixes it.

[supremetwo]

https://borncity.com/win/2019/06/12/win ... nt-viewer/

Could only close down event viewer via task manager (CTRL-ALT-DEL) mmc - end task.

So I copied the contents of ‘C:\ProgramData\Microsoft\Event Viewer\Views\ as per the link above before deleting the View_.xml files and errors gone.

[Itsallaguess]

There's a pretty good howtogeek article here discussing the new Windows 1903 features -

Everything New in Windows 10’s May 2019 Update -

https://www.howtogeek.com/402569/everything-new-in-windows-10s-april-2019-update/

I like the sound of the built-in Sandbox feature for some versions of Windows, and the speed-improvements concerning the earlier Spectre issues are very welcome indeed.

Cheers,

Itsallaguess

[jackdaww]

1903 downloaded and installed today - no problems as yet .

[JonE]

1903 downloaded and installed today - no problems as yet .

That's very probably the usual case. I had some time available a while ago so finally let WU do 1903 on 'Win10-64 Home' and noted without surprise that my dual-boot menu had disappeared as a result so would need to be reinstated. I needed to spend quite a bit more time than I'd hoped researching and fixing other effects.

Slightly peeved that I had to browse into my network printer and disable SNMP to get it recognised as being on-line - not an elegant or obvious fix but it swiftly overcame something I hadn't experienced before which is seemingly due to Win10.1903 changing detection method. As anticipated, I needed to use regedit again to get rid of Quick Access and other annoyances in File Manager.

It's now the case that merely creating and asserting DisableAntiSpyware no longer gets rid of Windows Defender AV Service so I had to disable Tamper Protection to permit that change! Windows seems increasingly keen to get in my way so dual-booting with Win10 may not remain on that machine for very much longer. Very heavy reliance on Quicken 2k has kept me with a foot in the Windows camp but since it doesn't work 100% in Win10 (so I currently still run it on a Win7 box) that tie seems no longer strong enough for me to tolerate Win10 and the time-cost of its future updates.

Cheers!