[REPO] Windows 10 TELEMETRY REPOSITORY

Discussion in 'Windows 10' started by Yen, Aug 4, 2015.

  1. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,740
    3,068
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. czsss

    czsss MDL Novice

    Aug 14, 2015
    9
    0
    0

    How to uefi boot iso folder?
     
  3. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,740
    3,068
    60
    I don't understand what you mean by "uefi boot iso folder"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. KMPLAYER

    KMPLAYER MDL Member

    Jan 12, 2014
    100
    77
    10
    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... :cool:
     
  5. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,740
    3,068
    60
    #2805 freddie-o, May 11, 2026
    Last edited: May 28, 2026
    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

    Privacy fix
    Elevate_as_TI V1.4 (updated script) adds 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 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


    Elevate_as_TI V1.4
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...