If you really want to disable telemetry then your best option is Enterprise or Education or Server because with these editions you can turn "Diagnostic data off" (Allow Telemetry=0) Other editions gather "Required diagnostic data" (Allow Telemetry=1) If you want you can easily upgrade from Pro to Enterprise just by changing the Product key (and Activating)
Aside from disabling Telemetry with my script I also use Firewall to block all outbound traffic https://forums.mydigitallife.net/th...lemetry-repository.63874/page-73#post-1724179
I need to get into the OOBE, what lines do I need to remove to be able to do that ? I searched for "CloudExperienceHost" in theb script but coudn't find anything in the script. Any help will be greatly appreciated.
No need to edit "disable_telemetry.cmd" script (to bypass OOBE phase). Just use your "autounattend.xml" in place of the "unattend.xml" i provided in my post
How does "CloudExperienceHost" affect telemetry? I have never seen it try to make any connections. Is it possible to prevent Certificate Path Validation from contacting ctldl.windowsupdate.com domain via any settings without disabling Certificate Path Validation? Ctldl.windowsupdate.com is one of the hard-coded domains that can only be blocked by 3rd party filters (such as the mentioned YogaDNS and/or Pi-Hole), but blocking ctldl.windowsupdate.com does not prevent non-Windows programs from updating certificate database in Windows Certificate Manager.
When your computer connects to the Cloud (MS account, OneDrive, joining the workplace environment or Azure AD, etc...) Windows collects information about you and your PC. Autologger creates & collects logs and traces your every keystroke and mouse click. During OOBE (when you connect to the Internet/Cloud) Autologger sends this logs to MS.
I know you can skip OOBE with unattended installation, but is it also possible to stop or delete services before they start when installing win 10? Also preconfigure group policy?
That is why Windows must be installed and fully configured/tweaked before it is connected to any network and must not use any MS account. Local account is the only acceptable account. That way CloudExperienceHost doesn't influence telemetry at all.
True... but the Cloud is more than just an MS account. It's any of your online accounts or anything you store in the the Cloud... and Windows tracks all of this.