Market Share March 2018

So much for the discussion on market share. That's OK, this OT is an interesting discussion. The update in question is an obvious breach of trust, but maybe all those W10 users have Stockholm syndrome by now. I too survived GWX in 2015/16 and as a W7 user, I sure hope nothing like that is being planned for 2020. I am not expecting it, but from what has happened over the last 2 years and especially this week, I am keeping a wary eye on this buzzard in the trees.

Brds7t7 said:

It's been a few months since I've tinkered with a 10 vm, as I've had no real desire to try it out again. So, are Pro users also not able to delay the updates now too?

The issue is somehow related to the Telemetry level that has been set in W10.

The reports indicate that Microsoft ignores user update settings and even installs the update on devices on which Windows Update is turned off.

If Windows Update is turned off, Microsoft uses the Update Assistant to deliver the update.

Woody suggests that the forced upgrades have something to do with the Diagnostic Data level setting of the system. Microsoft collects Telemetry on all consumer versions of Windows 10.

Tip: The next version of Windows 10, version 1803, includes options to view the Telemetry data.

If it is set to 0 (Security), an Enterprise-only value, update policies have no effect. This is confirmed on the Microsoft Docs website for Windows Update for Business clients.

For Windows Update for Business policies to be honored, the Diagnostic Data level of the device must be set to 1 (Basic) or higher. If it is set to 0 (Security), Windows Update for Business policies will have no effect.

Windows 10 users should check the Telemetry level in the Windows Registry if they are unsure what it is set to:

1. Tap on the Windows-key, type regedit.exe, and hit the Enter-key. This opens the Windows Registry Editor.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
3. Check the AllowTelemetry value. If Data is set to 0, the Diagnostic Data level is set to Security.

https://www.ghacks.net/2018/03/08/re...indows-update/

Additional
MS has fixed/released an update which apparently fixes the issue for those who haven't already been affected.

Important
Microsoft is aware that this notification was incorrectly delivered to some Windows 10 Version 1703 devices that had a user-defined feature update deferral period configured. Microsoft mitigated this issue on March 8, 2018.

Users who were affected by this issue and who upgraded to Windows 10 Version 1709 can revert to an earlier version within 10 days of the upgrade. To do this, open Settings > Update & Security > Recovery, and then select Get started under Go back to the previous version of windows 10.

https://support.microsoft.com/en-us/...stall-the-late

Brds7t7 said:

Well this all sounds like... fun!

So people have to rollback to the previous version because of another one of MS update cock-ups? Last time I tried to do a rollback on a 10 VM it turned into a total disaster. In the end I just deleted the VM.

I keep backup copies of my VMs in case of disaster.

I also use the Snapshot feature for my VMs that run in VMware Workstation 9.

Brds7t7 said:

It's been a while though, so maybe they've improved the rollback process?

I'm not sure it has.

Here is a link from a post (made a couple of days ago) in TenForums:
Windows 10 not working properly after rollback - Microsoft Community

Brds7t7 said:

The whole thing is an inconvenience though.

That's stating it politely.

Brds7t7 said:

I usually do take regular Snapshots, but it was one of my daft moments where I'd deleted the snapshots for that particular VM the day before, gone off to do something else, and then forgotten to do one for it before attempting the rollback.

Isn't that always the way.
The one time you forget is the time you actually need to do it.

Brds7t7 said:

Wasn't too bothered about it though, as I didn't use the 10 VM very often and had nothing important in it anyway.

I'm going to have to install Visual Studio 2015 and try to get Hyper-V to run in my W10 VM (for my TAFE course).