Please save the image with Ntlite first and then observe. ControlSet001\Control\WMI\AutoLogger\AutoLogger-Diagtrack-Listener will be generated under HKEY_LOCAL_MACHINE\SOFTWARE\I don't see a problem. Confirmed the AutoLogger setting was correctly updated in the image. Look in the registry hive's path.
Just installed the same image. I don't see HKLM\SOFTWARE\ControlSet001.
<Tweaks>
<Settings>
<TweakGroup name="Privacy">
<Tweak name="DataCollection\AllowTelemetry">0</Tweak>
</TweakGroup>
</Settings>
<Services></Services>
<ExtraServices></ExtraServices>
<ScheduledTasks></ScheduledTasks>
</Tweaks>
Don't understand where this is going. Telemetry is data shared with MS. AutoLogger-Diagtrack-Listener is for logging boot events, like device driver loading. Whether it's shared with MS or not, doesn't impact the local system's log profile.
If you change the GPO policy, it's not going to update other ControlSet keys.
Further, why is only ONE KEY listed in your example when AutoLogger-Diagtrack-Listener owns multiple keys?
Why don't you test this by deleting the HKLM\SOFTWARE\Control001 key, and switch the GPO around. If you're right, then this key will be recreated or updated by itself.
<Tweak name="DataCollection\AllowTelemetry">4</Tweak>
Aa yes, thanks! Corrected in the next version.I found it, this will cause the registry to do that.
Code:<Tweaks> <Settings> <TweakGroup name="Privacy"> <Tweak name="DataCollection\AllowTelemetry">0</Tweak> </TweakGroup> </Settings> <Services></Services> <ExtraServices></ExtraServices> <ScheduledTasks></ScheduledTasks> </Tweaks>