May 07 2018 08:20 AM
May 07 2018 08:20 AM
1803 build 17134 is now available
Did it release as Semi-annual (Targeted) or Semi-annual?
will it be the approximately 4 months before my rings begin to defer it as semi-annual or are they going to start installing it now if on the semi-annual branch???
May 09 2018 05:08 PM
The documentation is incorrect. 1803 is semi-annual targeted. If you have your deferral set to install feature releases as semi-annual it will be several months.
1803-semi annual targeted
May 10 2018 07:50 AM
"The documentation is incorrect."
that's cant be, Its Microsoft! they wouldn't release a feature update to 10 million devices and mess up the release communication (LOL)
I need MS to either fix their documentation or standby the release
May 24 2018 06:33 AM
You aren't alone. I'm getting reports that 1803 is getting on machines that have semi-annual selected. It shouldn't even be near that machine.
May 24 2018 06:56 AM
Use that to block it. (and come on Microsoft , I've lost count how many times deferrals haven't worked)
May 24 2018 05:52 PM
The machines should not have been upgraded with that policy set, with a couple of exceptions
There are two ways this can happen.
Is there a support case where machines were upgraded with that policy set?
Darrell Gorter [MSFT]
May 24 2018 10:34 PM
Even with the dual scan issue these machines are set for "semi-annual". We are still at semi-annual targeted. There is no reason these machines should be getting 1803.
I have two other MVPs on a private list who are behind Windows update who got 1803 and they had semi-annual chosen as well.
May 25 2018 01:09 AM
the Case No. is
May 25 2018 03:05 PM
Fellow MVP, not behind a domain, therefore no WSUS/dual scan, telemetry on.
This is not the first time that feature releases have come down when they clearly should have respected the block.
May 25 2018 04:04 PM
We would like to see some log files and registry entries from machines that were upgrade to 1803 where you thought the feature update to 1803 was deferred.
Please Collect these registry values
and we would like to see the logs collected with this tool
Please Send the information to me
May 25 2018 05:14 PM - edited May 25 2018 05:15 PM
Susan forwarded this to me as I have an affected machine. (I started the partner thread she cited.) Win10 Pro 32-bit virtual machine, domain environment, no WSUS. 64-bit machines in the same environment have not upgraded yet. Group Policy Result as follows:
AllowTelemetry is set to Basic as shown in the group policy above:
(Key exists but no values)
BTW I did see the note in Group Policy that I have to have AllowTelemetry=1 or higher:
However the setting of AllowTelemetry shouldn't matter on Pro anyway since 0 is the same as 1:
When I tried to run Copylogs.exe, I get this:
Must be 64-bit-only?
May 26 2018 11:51 AM
We don't have a 32-bit version of tool available right now.
Can I get you to file a feedback request using the Feedback Tool
Promote to a bug, Upload Logs.
Send me the Feedback ID or post to this thread
May 26 2018 04:01 PM
I submitted feedback without signing in. (I prefer domain accounts and don't link my Microsoft account to most machines.) I told it to submit logs but I did not see the option to "promote to a bug." I did not get a feedback ID but it did create this empty folder:
If you have a list of logs that's not too long, I can just zip them up for you.
May 26 2018 07:13 PM
Thank you for the suggestion. I have emailed Darrell the Windows\Logs folder as well as Windows.old\Windows\Logs.
May 29 2018 06:26 AM
Is there any News available.
I have set a Policy to my Clients that they dont check the MS Update Websites in order to stop the deployment. But this will lead to a lack of security. I want to use the normal semi annual channel with the acutal Build (1709 and not 1803) and defer the Installation like offered in the Policy. I have also set the telemetry to value 0 which is the same like 1 for Enterprise users.
Many thanks for any Feedback.
May 29 2018 10:44 AM
May 29 2018 11:15 AM
You don't want to set telemetry to 0 as that ignores the Windows update for business settings. If you use the don't use dual scan setting - and are behind WSUS you should be fine.