yes he will for sure reup the file for you which does the 0 job in a great way. here my 0 meant ? & ? itself is a question upon question thus story never ends
And not only that, it is blocking another "innocent" domains MISTAKENLY!!! I'm gonna ditch this "solution".
So what happened to your telemetry solution? Why did you block non-MS domains/ips? If it's so difficult to explain, try it to make it easy. At least try.
On one machine I put a server 2011 sp1 update to 05.2016 Ran everything I could on it, including drivers - it's an amd RX570 Disabled unnecessary services Turned on PFsense packet capturing for 24 hours The miracle happened. Requests were only from epicgames and Infix PDF Editor to update. From winds up only pings to other computers (roll call) I haven't seen any crazy leaks to Microsoft servers! I haven't looked into it in more detail, but I like the results. ps: Just a side note Do you know the difference between Windows Server and normal Windows? The only difference is two lines in the registry (or rather two anchors) (not my comment) Mark Russinovich
I don't put any updates on purpose! Do you think security updates come out? After the words of a former Microsoft employee, that patches and patch updates come out, at best 2 or 3 years old, to close holes. The purpose of updates has nothing to do with your security at all! Security of your system files -YES Security of your code - YES Your privacy - NO For a server converted to your needs, for protection, PFsense + VPS + VPN = online This is bum protection
Hey man. Im very new to like this telemetry stuff and im wondering how i run this these type of things
If you're new, better research first what each registry entry does. You might disable or remove a feature you need.
It's a batch script. Put it in the same folder with your install.wim. Run the script as TrustedInstaller. The script mounts the install.wim, loads the Registry hives, applies the registry modifications, unloads the Registry hives then unmounts the install.wim Spoiler begin.cmd (script) Code: @echo off pushd "%~dp0" "%~dp0PowerRun_x64.exe" disable.cmd Edit: I updated the script
It's the package for installing Windows. Might I suggest you find a simpler method of disabling telemetry
rem == disable studying user preferences or device behavior == reg add "HKLM\SOFTHIVE\Policies\Microsoft\Windows\PreviewBuilds" /v "EnableConfigFlighting" /t REG_DWORD /d "0" /f You deleted this script line - is it no longer needed? What is the script better at now? You ran the previous scrypt only as admin - now as a TrustedInstaller?
This entry - HKLM: \ SOFTWARE \ Policies \ Microsoft \ Windows \ DataCollection "" AllowTelemetry "0 - has been reported to work - only - for enterprise and education. On pro and home - automatically sets to 1.