Registry and PowerShell files affecting Windows policy, gaming, input, power, UI, permissions and system behavior.
Adds the same elevated PowerShell action through SystemFileAssociations\.ps1, covering systems where the primary PowerShell file-class registration differs.
Functionally overlaps the other admin PowerShell context-menu file. It launches arbitrary selected scripts elevated.
Usage: Import only if the other PowerShell context-menu registration does not appear on the target system.
Adds “Run with PowerShell (Admin)” under the PowerShell script file class and launches the selected .ps1 in an elevated PowerShell process.
This is a convenience launcher, not a safety boundary. Any selected script receives administrator rights. Review the script before launching it.
Usage: Import the .reg file, then right-click a PowerShell script associated with Microsoft.PowerShellScript.1.
Adds an Explorer “Take Ownership” command for files and folders. It runs takeown and then grants the local Administrators group Full Control; folder changes recurse through descendants.
Useful when recovering access to files you legitimately administer. It changes ownership and ACLs, so applying it to Windows, Program Files, component-store, or application folders can break inherited permissions and servicing. The file itself credits Walter Glenn / How-To Geek and is treated as third-party material rather than MIT-licensed project code.
Usage: Import the .reg file as an administrator, then use the new Explorer context-menu entry only on paths whose permissions you intentionally want to replace.
Creates an Image File Execution Options PerfOptions entry for bf6.exe and sets CpuPriorityClass to 3 (High).
Every matching bf6.exe launch is affected. High priority can reduce scheduling headroom for background, audio, capture, networking or system work under load. It does not guarantee lower latency or higher FPS.
Usage: Import only if bf6.exe is the intended executable and benchmark before/after behavior.
Disables Game Bar presence writing and Game DVR/capture through machine and per-user values while leaving AutoGameModeEnabled set to 1. It also writes fullscreen-optimization related GameConfigStore values.
Can affect Win+G, background capture and Xbox gaming overlays. The “fixed” variant differs from Disable Gamebar.reg by keeping Game Mode enabled and adding more GameDVR/FSE policy values.
Usage: Import for the intended user and system. Sign out or reboot before judging the result.
Disables Game Bar presence writing, Game DVR/capture and Auto Game Mode through machine and current-user registry values.
Can disable Win+G and capture features. It also disables Game Mode for the current user, so it should not be described as a pure Game Bar toggle.
Usage: Import for the intended user and reboot or sign out.
Removes two explicit timer/power-throttling overrides, sets core-parking ValueMax to 100, disables multimedia network throttling, sets SystemResponsiveness=10, raises Games task priorities and writes Win32PrioritySeparation=0x26.
Also restores DisablePagingExecutive and LargeSystemCache to 0. These are machine-wide scheduler and multimedia settings; claimed gaming benefits depend on workload and are not guaranteed.
Usage: Record the original values first and test with repeatable frametime/latency measurements.
Writes MouseSensitivity=10 and custom SmoothMouseXCurve/SmoothMouseYCurve values, plus disables default-user mouse acceleration thresholds.
The filename indicates a 100% display-scale 1:1 mouse-fix profile. Games using Raw Input bypass the classic Windows pointer acceleration path, so this may not affect them. Applying a curve designed for another scaling/input configuration can change desktop pointer behavior.
Usage: Use only for the matching Windows scaling/pointer setup and keep the previous mouse registry values for rollback.
Sets kbdclass\Parameters\KeyboardDataQueueSize to 0x64 (100 decimal).
Changes the keyboard class driver's input queue capacity. A larger or smaller queue is not a direct input-latency control, and 100 is already a common/default value on many systems.
Usage: Benchmark only if you know the current value and have a concrete reason to override it.
Sets mouclass\Parameters\MouseDataQueueSize to 0x64 (100 decimal).
Changes mouse class-driver queue capacity. Queue size is not equivalent to USB polling rate or render/input latency and may be a no-op relative to the existing default.
Usage: Benchmark before and after instead of assuming a latency improvement.
Modifies the current power plan: CPU EPP/boost/core parking and thresholds, USB selective suspend/LPM, PCIe ASPM, disk idle, sleep, display timeout, multimedia playback bias and detected SATA HIPM/DIPM settings.
It writes both AC and DC values, including EPP=0, core parking minimum/maximum=100, USB and PCIe power saving off, sleep off and disk idle off. This can materially increase idle power, heat and battery drain. Several CPU aliases are hardware/Windows-build dependent.
Usage: Run as administrator only after exporting the current power plan or otherwise recording its values. Avoid as a generic laptop preset.
Attempts to set MSPower_DeviceEnable.Enable to False through WMI/CIM for USB-root related devices.
The implementation enumerates MSPower_DeviceEnable repeatedly and then filters using PNPDeviceID even though the WMI class commonly identifies devices through InstanceName. It may behave differently from the apparent intent or fail to target the expected devices. Do not treat it as a verified universal replacement for Device Manager power-management checkboxes.
Usage: Review and test on a non-critical machine before use. A maintained device-specific implementation should identify exact instances first.
Sets HiberbootEnabled to 0 under Session Manager\Power, disabling Windows Fast Startup.
This does not necessarily remove hiberfil.sys or disable full hibernation. Boot behavior may become more predictable at the cost of slower cold startup on some systems.
Usage: Import as administrator and reboot.
Sets instant menu/hover timings, disables hibernation/Fast Startup, blocks automatic driver delivery, writes NVIDIA/graphics-related registry values, sets DWM OverlayTestMode=5 and disables Notification Center.
This is a mixed preset rather than one tweak. The RMHdcpKeyglobZero and OverlayTestMode values are hardware/driver-sensitive and may affect DRM, overlays, MPO behavior or display compatibility. The display-adapter path ending in 0000 is not guaranteed to identify the intended GPU on every system.
Usage: Prefer applying narrowly scoped components individually. Create a restore point and export affected keys first.
Writes DisableNotificationCenter=1 in current-user and machine policy locations.
Suppresses the Notification Center/Action Center interface. The HKCU value applies only to the user importing it; the HKLM policy provides machine scope where honored.
Usage: Import as administrator if machine-wide policy is intended.
Excludes drivers from Windows quality updates, blocks device metadata retrieval from Microsoft and sets driver-search order to avoid Windows Update.
Useful when maintaining vendor drivers manually, but it can also prevent security, compatibility or hardware fixes from arriving automatically.
Usage: Import as administrator. Revert the policy values before relying on Windows Update for drivers again.
Sets TargetReleaseVersion=1 and TargetReleaseVersionInfo to the currently installed DisplayVersion, then restarts Windows Update.
Despite its filename, this targets the Windows feature release, not Home/Pro/Enterprise edition licensing. It also omits ProductVersion, which newer Windows policy guidance commonly pairs with these values. The maintained Set-WindowsFeatureTarget.ps1 is preferred.
Usage: Prefer scripts/Set-WindowsFeatureTarget.ps1. Use this preserved variant only when you understand the policy behavior.