SOLVED

1803 (Targeted)?

Highlighted
New Contributor

1803 build 17134 is now available

 

Did it release as Semi-annual (Targeted) or Semi-annual?

windows-10 release-information

 

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???

32 Replies
Highlighted

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

1709-semi annual

Highlighted

"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

1803-semi-annual.jpg

 

 

 

Highlighted

Take a look at this. Why is 1803 installed on a client with Semi-Annual Channel?

 

image.png

Highlighted

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.  

Highlighted

Great and now? Microsoft please tell us a solution to stop this.... Thanks.

Highlighted

https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-rei...

Use that to block it.  (and come on Microsoft , I've lost count how many times deferrals haven't worked)

Highlighted

Hello,

The machines should not have been upgraded with that policy set, with a couple of exceptions

There are two ways this can happen.

  • The dual scan scenario where the polices settings configuration is not set properly, we took changes to address this last summer, by adding a new policy but it’s possible that people have not figured it properly. The fix was to offer a new option but it’s possible that policy is not set.
  • GP that sets Telemetry to Zero Exhaust

Is there a support case where machines were upgraded with that policy set?

 

Darrell Gorter [MSFT]

Highlighted

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.

 

https://partnersupport.microsoft.com/en-us/par_clientsol/forum/par_win/why-was-windows-10-machine-up...

 

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.

Highlighted

Hello, 

the Case No. is 

 

  • Service Request #: 118052418249642
  • Service Request Title: Unwanted Installation of Windows 1803 - GPO with 365 Day delay is setup

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.

 

 

Highlighted

Hello

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\DataCollection]

 

and we would like to see the logs collected with this tool

https://aka.ms/wucopylogsexternal

 

Please Send the information to me

Darrellg.removethis.@microsoft.com

Thanks

 

Highlighted

Darrell,

 

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:

GPresult.png

 

AllowTelemetry is set to Basic as shown in the group policy above:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection]
"AllowTelemetry"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\DataCollection]

(Key exists but no values)

 

BTW I did see the note in Group Policy that I have to have AllowTelemetry=1 or higher:

 

SelectWhen.png

However the setting of AllowTelemetry shouldn't matter on Pro anyway since 0 is the same as 1:

AllowTelemetry.png

When I tried to run Copylogs.exe, I get this:

CopyLogsMessage.png

Must be 64-bit-only?

 

Mark Berry
MCB Systems

Highlighted

Hello Mark,

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

 

  • Category: Install and Update
  • Sub-Category: Windows update

Promote to a bug, Upload Logs.

Send me the Feedback ID or post to this thread

 

Thanks

Darrell

Highlighted

Darrell,

 

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:

 

C:\Users\<MyUser>\Documents\FeedbackHub\{b1b0d70e-7d3d-49bb-8d1e-af6c040ee2fe}

 

If you have a list of logs that's not too long, I can just zip them up for you.

 

Mark Berry

Highlighted

Please ZIP and share %windir%\Logs 

Highlighted

Navjot,

 

Thank you for the suggestion. I have emailed Darrell the Windows\Logs folder as well as Windows.old\Windows\Logs.

 

Mark Berry

Highlighted

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.

Thomas

Highlighted
We are still looking for more logs if anybody has them.
The one set of logs showed RS4 was available prior to the machine joining WUFB with the deferral policy.
Send me the logs or make them available for download please
Thanks,
Darrell
Highlighted

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.