Updated all scripts disable_telemetry_05.09.2026 Elevate_as_TI v1.3 https://forums.mydigitallife.net/th...lemetry-repository.63874/page-66#post-1686849 disabled more TPM telemetry: DeviceHealthAttestationService and TPM scheduled task
From what I saw for Elevate_as_TI v1.3.ps1 to work - the folder must exist: C:\Window\Logs. And inside it a file is created in which data is constantly recorded about what is being executed. That is, this information is accumulated in one file. The folder C:\Window\Logs was deleted by me, I delete it every day and then I created it to test Elevate_as_TI v1.3.ps1. But why is this folder necessarily needed?! In terms of privacy it is worrying that a file is created in which everything is recorded about what is opened when using Elevate_as_TI v1.3.ps1. If it were possible to use Elevate_as_TI v1.3.ps1 without creating such a file...
Why the script needs a log? When a script does something powerful — like running programs with the highest possible Windows privileges — If something goes wrong (a program crashes, something behaves unexpectedly, or you just want to know what happened), the log file tells you exactly what the script did and when. Without it, troubleshooting would be guesswork. Why it logs to C:\Windows\Logs specifically? C:\Windows\Logs is safe — only Administrators and Windows itself can write there. If the log were kept somewhere more open (like your regular Temp folder), a sneaky program running in the background could interfere with it or even trick the script into overwriting important system files. Using C:\Windows\Logs prevents that. What it records? When the script ran (timestamp) What file you asked it to launch Whether it succeeded or failed Update: Elevate_as_TI V1.4 — Privacy fix — Added a -NoLog switch. If you run the script with -NoLog, it writes nothing to disk at all — no file is created, no folder is needed. You still see what's happening in the terminal window, but nothing is saved anywhere. So users who are concerned about privacy can simply use this option. Usage: Code: .\Elevate_as_TI.ps1 -NoLog powershell -ExecutionPolicy Bypass -File "%~dp0Elevate_as_TI.ps1" -FilePath "%~f0" -WorkingDirectory "%~dp0." -NoLog
Hi, i have the telemetry script for Win 10. I installed the new driver from Nvidia and new control panel dont start anymore? Is anyone else having these problems!? I can't make any more settings! Does anyone know how to fix this problem with the script?
Updated disable_telemetry package (disable_telemetry_08.03.2026) Added StartMenuExperienceHost.exe to Image File Execution Options (IFEO) in Windows 10 Added StartMenuExperienceHost.exe and MpDefenderCoreService.exe to Image File Execution Options (IFEO) in Windows 11 Deleted MDCoreSvc (Microsoft Defender Antivirus Core Service) in Windows 11 Added updated (Added -NoLog switch) Elevate_as_TI v1.4 script https://forums.mydigitallife.net/th...lemetry-repository.63874/page-66#post-1686849
Sorry guys Somehow adding StartMenuExperienceHost.exe to Image File Execution Options (IFEO) in Windows 10 breaks the Start menu - it won't launch But Start menu in Windows 11 works I'll be correcting the scripts and re-uploading the disable_telemetry package
Uploaded the corrected script package disable_telemetry_08.04.2026.zip Removed StartMenuExperienceHost.exe in Image File Execution Options (IFEO) in Windows 10 and 11 scripts -- Adding StartMenuExperienceHost.exe to Image File Execution Options (IFEO) in Windows 10 prevented Start menu from launching altogether -- For safe measure it was removed from Windows 11 scripts too https://forums.mydigitallife.net/th...lemetry-repository.63874/page-66#post-1686849
When FAM 2.80 detects "FOUND" issues that need fixing, you should ask AI; that is exactly how I fix them.
I have Windows Server 2022. After using the freddie-o script, I had 97.8. Later, after modifying the ISO image (1.71 GB), I got this result. Sorry, the image didn't paste.