WinQuickTools: A Set of Quick Maintenance Utilities for Windows

WinQuickTools is a set of quick maintenance scripts for Windows, aimed squarely at the operations that should take one step but which the system turns into several. Take setting “Run as administrator” on an exe: you open Properties, go to Compatibility, tick a checkbox, one layer nested inside another. Doing one is fine; doing a batch is a pain. This toolbox collapses that kind of operation down to a single drag or a double-click.

No installer software here, just scripts. Drag or double-click and it runs directly: no environment setup, no pulling dependencies, no build. Download whichever .bat you need, delete it when you’re done, leave no junk behind. Target platform is Win10/11, every entry point is a batch file, starting with @echo off, CRLF line endings, no BOM. Miss these details and Chinese output and paths start acting up. The dirty work goes to inline PowerShell (powershell -NoProfile -ExecutionPolicy Bypass), and everything else uses built-in commands like reg.exe. Zero external dependencies.

For now the only thing that actually works is SetRunAsAdmin, which batch-sets .exe or .lnk files to always run as administrator: drag a pile of files onto the script icon, or double-click and then drag the paths in and hit Enter. The mechanism splits into two cases. For .exe, it writes the RUNASADMIN flag to HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers, preserving existing compatibility settings without clobbering anything else. For .lnk, it directly modifies the administrator flag bit in the shortcut file header. After that, launching pops the normal UAC prompt.

When it finishes it gives a short summary in Chinese, listing successes, failures, and skips separately:

[成功] 已处理：路径
[失败] 原因：具体原因
[跳过] 不支持：路径

结果：成功 1 个，失败 0 个，跳过 0 个。

To slot it into automation, set RUNASADMIN_BAT_NOPAUSE=1 and it won’t pause at the end.

A few principles it won’t compromise on: support Chinese and paths with spaces, batch-process multiple files dragged in at once, output entirely in Chinese split into success/failure/skip, require confirmation for high-risk operations rather than blindly executing, and preserve whatever user settings can be preserved. Everything planned next is stuff I use every day myself: open a terminal or Explorer in the current directory, batch rename, copy paths, ping/port/DNS checks, and confirmation-gated cleanup of temp directories. It’s still early days. SetRunAsAdmin is the one that runs and sets the template; the rest is on the roadmap.