Has your copy of Win10 version 1803 been updated?

I’m seeing reports – notably from Bogdan Popa – that there’s a Day 1 cumulative update rolling out to those of you who downloaded and installed 1803 from the Windows download site, or from Windows Update.

The original release is build 17134.1. If you got the Day 1 update, you’ll be on build 17134.5. (Type About in the Cortana search box.) Those of us who stuck through the Windows Insider updates are on 17134.5. Many people are on 17134.1. I updated a VM, but it’s still on 17134.1, and I don’t really trust VMs to tell the whole truth.

If you just got version 1803 — by hook or by crook, but not through the Insider program — could you check your version number for me?

Thanks.

April: Windows 10 share down, Windows 7 up

At a time when Windows 7’s user share should be falling, and Windows 10 on the rise, Net Applications’ data for April shows the opposite.

Gregg Keizer at Computerworld.

Patch Lady – early trending issues with 1803

I’ll be updating this post with trending 1803 install issues I see and potential resolutions:

I will note when an issue is expected and when (to the best of my knowledge) it’s not expected.

1. Home group removed:  Known and expected:   Microsoft has removed this from 1803 and recommends alternatives:  https://support.microsoft.com/en-us/help/4091368/windows-10-homegroup-removed  You will need to also enable a specific service  (Function Discovery Resource Publication service) to get peer sharing working after the feature release.
2. After 1803 seeing several reports of recovery drive being assigned a drive letter.  Not expected.  Workaround:  Use Diskpart to remove drive letter.  Acknowledged by Microsoft.
3. Alienware laptops and desktop users are reporting issues with the upgrade.  Expected this is actually a block with a not well thought out error message  Not expected.  Workaround:  Per page 3 on this forum.  Remove Alienware update and digital delivery utility and just leave Alienware command centre and Alienware onscreen display.  Alternatively you can download from the media creation page,  when it proceeds to “creating media” disconnect from the Internet and it will prevent it from downloading drivers and will get past the 49% mark where the install gets stuck.   UPDATE see https://www.askwoody.com/2018/patch-lady-dont-go-around-the-block/
4. Chrome is freezing after the update as noted here:  Known issue.  Fix now released install the May 1803 update.
5. For those running Essentials 2012 R2 or Essentials 2016 (Microsoft’s SMB server) the connector software that needs to be installed on Windows 10 to get it to communicate fully with the server is having issues with 1803.  I’m also getting reports from folks using that platform that it’s health routine is causing the clients to update to 1803.  Any routine that will cause workstations to check for updates will trigger the “seeker” behavior and cause 1803 to install.  Fix now released install the May 1803 update.See https://blogs.msmvps.com/bradley/2018/05/02/1803-and-issues-with-essentials/
6. Issues with SSDs on Surface Pro devices. Specially Intel SSD 600p Series or Intel SSD Pro 6000p Series.  Fixed.  Known.  Microsoft has blocked the update from systems.  Now fixed in May 23rd updates for 1803.
7. Issues with Toshiba XG4 Series, Toshiba XG5 Series or Toshiba BG3 Series SSD drives. Fixed.  Known.  Noted here and here.   Now fixed in May 23rd updates for 1803.
8. Possible issues with Avast antivirus.  Still being investigated.

Microsoft releases major Windows or Office patches on 11 different days in April

It took a while to find them all.

If you know someone who follows patches for a job, have pity on them.

Computerworld Woody on Windows.

Patch Lady – don’t go around the block

For those with certain models of Alienware machines read on for issues with 1803:

Do not go around the block:

https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/hybrid-laptops-with-discrete-gpu-connected-to/3518f6b4-c267-4d38-b5b9-d5ea0c16e975?tm=1525314302049&auth=1

Side effects include not being able to wake from sleep. Go Back to 1709 under Settings > Update & security > Recovery

Alienware 13 R3
Alienware 15 R3
Alienware 15 R4
Alienware 17 R4
Alienware 17 R5

Microsoft is currently blocking these models from installing the update due to a known incompatibility that may cause these devices to display a black screen after resuming from battery saver mode. For this reason, we do not recommend attempting to work around the current block to install the April 2018 Update. Microsoft is currently working on a solution that will be provided in a future Windows Update, after which these devices will be able to install the April 2018 Update.

If you are receiving this message, you do not need to take any action at this time. There are no apps that need to be uninstalled. Windows Update will notify you when the April 2018 Update is ready for your device.

There’s a seeker born every minute

We know a little bit more about how and why Win10 1709 users are being pushed onto Win10 1803.

Computerworld Woody on Windows.

Patch Lady – Simplification in the GUI

In the 1803 release Microsoft made some changes in the Windows update section to make it more streamlined and simple.  Bottom line that entire section in the Pro sku where inside the GUI you could push off the Feature update up to 365 days isn’t there anymore.  Kinda.  Well at least in the GUI it’s gone.  But the good news is under the hood it’s still there.

The streamlining means you only have pause for 7 days as a GUI option.  You can see the changes here:

https://www.windowscentral.com/whats-new-settings-app-windows-10-april-2018-update#update_settings_windows10_1893

It is thankfully still fully available to be adjusted by using local group policy or registry keys.

However it obviously isn’t quite as standalone user friendly as it used to be.  To adjust this using the local group policy editor, IF YOU HAVE THE PRO SKU and 1803 (which if you want to control updates you must have) in the search box type in gpedit.  Click to launch the local group policy editor that is offered up.  Find the Local Computer policy, then computer configuration and open up the administrative templates tab.  Find the windows components section and scroll all the way down to Windows updates.  Now find the Windows update for business folder in the right hand side of the pane and click to expand.  You’ll see the select when preview builds and feature updates are received.  Open it up.  Enable the setting and choose semi-annual channel and then you can choose to push off feature updates for up to 365 days.

So the same deferral is still there in 1803, but not quite as easy to find the settings as 1709 if you are using a standalone Windows 10 pro sku.

Heads up: If you’re a Windows Insider and you want to stay with Win10 1803, you need to get out of the program

Dona Sarkar advises:

#WindowsInsiders: if you don't want to start receiving RS5 builds, you should switch to Release Preview TODAY. Both WIP Fast and Slow will see RS5 builds….why, yes, SOON ™ pic.twitter.com/I9oHGDNIyq

— Dona Sarkar (@donasarkar) May 2, 2018

To stick with 1803 and stay out of the beta testing process (for a while anyway), click Start > Settings > Update & Security. On the left choose Windows Insider Program. Click the button to Stop Insider Preview builds. When asked, confirm that you want to stop the beta builds. Then you’ll have to reboot.

You can move to the Release Preview if you really, really want to. Microsoft has a detailed description of the Ring and how to get into it on the Windows Insider blog.