Heh... it certainly will. I'd recommend doing that last in the integration process, tho. it might break a future update.
Windows Component Store, "tells" windows update what Component are currently on OS it will not give updates for defender anymore
I ran the disable telemetry batch script. So after reboot and running it again, it should say that telemetry is disabled. Would you want to re-enable it? But instead, it still says that the Telemetry is enabled and offers to disable it again and again. So your script I am afraid is not working or needs some modifications. Thank you for the effort.
sorry for reasking, but really want to make sure does that reg key truly disable telemetry on home and pro? have you tested it to make sure no telemetry traffic is going on? again i don't mean to bug. and yeah, when i ran the script, it told me it was already disabled and would i like to reenable it, but i never added the key. so i ended up adding it manually.
Okay try this for the disable telemetry script. I had some errors that were causing it to only work to disable, but not to re-enable: Disable-Telemetry.cmd: Code: @echo off title Disable/Enable Windows Telemetry color 1f :Begin UAC check and Auto-Elevate Permissions :------------------------------------- REM --> Check for permissions >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system" REM --> If error flag set, we do not have admin. if '%errorlevel%' NEQ '0' ( echo: echo Requesting Administrative Privileges... echo Press YES in UAC Prompt to Continue echo: goto UACPrompt ) else ( goto gotAdmin ) :UACPrompt echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs" echo UAC.ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs" "%temp%\getadmin.vbs" exit /B :gotAdmin if exist "%temp%\getadmin.vbs" ( del "%temp%\getadmin.vbs" ) pushd "%CD%" CD /D "%~dp0" :-------------------------------------- :Check the key: (reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry"|find /i "0x0")>NUL 2>NUL if %errorlevel% NEQ 0 GOTO :KEYOFF :KEYON echo ============================================================ echo Windows Telemetry currently disabled. echo Would you like to re-enable it? (Y/N) echo ============================================================ echo. choice /c yn /n If %ERRORLEVEL% NEQ 1 GOTO :QUIT Echo Deleting Telemetry Registry key REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry" /F>NUL 2>NUL IF %ERRORLEVEL% NEQ 0 GOTO :ERROR Echo. Echo Windows Telemetry enabled Echo. goto :QUIT :KEYOFF echo ============================================================ echo Windows Telemetry is currently enabled. echo Would you like to disable it? (Y/N) echo ============================================================ echo. choice /c yn /n If %ERRORLEVEL% NEQ 1 GOTO :QUIT Echo Changing Registry key reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry">NUL 2>NUL if %errorlevel% equ 1 REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry" /F>NUL 2>NUL REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry" /D 0 /T REG_DWORD /F>NUL 2>NUL IF %ERRORLEVEL% NEQ 0 GOTO :ERROR Echo. Echo Windows Telemetry disabled Echo. goto :QUIT :QUIT echo ============================================================ echo Press any key to exit... echo ============================================================ pause>NUL goto :EOF :ERROR echo ============================================================ echo The script ran into an unexpected error setting reg key. echo Press any key to exit... echo ============================================================ pause>NUL goto :EOF
Well, it's hard to prove. You can get wireshark out and find if any of the vortex addresses are being accessed. If they are, is any data being sent? or is it a timed thing that just checks in? All of this stuff needs further testing.
Would be good to gather reg-keys/info and put all together, the Tweaks Thread is a formidable Mess . Then one could try to merge into a script.
A lot of times ppl post a tweak without any sort of explanation. I don't know about you, but I tend to avoid adding registry info if I don't know what it's supposed to do Yes, needs cataloging and sorting.
Reminds me, there's always a nice hybrid code(abbodi: Powershell/s1ave: CMD) to change a reg-key with TI level and set back to TI afterwards .
May i ask if this keylogger is present in the RTM build (10240.16384.150709-1700) or was it found in the beta/testing builds only ?
hello master Murphy78, i have installed Windows 10 Professional X64. There is option Speech, inkink, & typing at Settings->PrivacyIn the right side there is a button Stop getting to know me Have to press it ? On the other hand, at option General have to switch off all the privacy options? I don't understand exactlly your text: It's an option during setup, yes This option appears during the OS installing?Thank you in advance
Did some catch up reading on the 60+ pages of this thread and I've concluded MS and their data logging in W10 is ridiculous. Seems like they've made it FAR more tedious to get rid of their snooping behavior than in previous versions of Windows. Is it possible that someone is working on an all-in-one patcher to remove all datalogging/keylogging/telemetry/bulls**t in one click (similar to Microsoft Toolkit or KMSpico)? As a consumer, I can only dream.
This is what i am waiting for something we can integrate into the iso and straight after setup it can run automatically and disable all the telemetry sh*t!
So... this means all of this keylogger thing is just paranoia and it just collects data to make this services run better? Well... that sounds better... but what is all this telemetry all about then? Sorry, I'm just confused about this... Thanks in advance for the answer