Forum Discussion
1803 (Targeted)?
Microsoft updated the docs to make it clear, that when Telemetry is set to Zero, the deferral policies do not take affect and you make get the feature updates.
Here are the links to the updated Docs
https://docs.microsoft.com/en-us/windows/deployment/update/waas-overview
Important Devices on the Semi-Annual Channel (formerly called Current Branch for Business) must have their diagnostic data set to 1 (Basic) or higher, in order to ensure that the service is performing at the expected quality. If diagnostic data is set to 0, the device will be treated as if it were in the Semi-Annual Channel (Targeted)(formerly called Current Branch or CB) branch. For instructions to set the diagnostic data level, see Configure the operating system diagnostic data level.
https://docs.microsoft.com/en-us/windows/deployment/update/waas-configure-wufb
Note Users will not be able to change this setting if it was configured by policy. Important Devices on the Semi-Annual Channel (formerly called Current Branch for Business) must have their diagnostic data set to 1 (Basic) or higher, in order to ensure that the service is performing at the expected quality. If diagnostic data is set to 0, the device will be treated as if it were in the Semi-Annual Channel (Targeted)(formerly called Current Branch or CB) branch. For instructions to set the diagnostic data level, see Configure the operating system diagnostic data level.
Thanks
Darrell Gorter
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
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:
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:
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?
Mark Berry
MCB Systems
Navjot,
Thank you for the suggestion. I have emailed Darrell the Windows\Logs folder as well as Windows.old\Windows\Logs.
Mark Berry
Please ZIP and share %windir%\Logs
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
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
