Windows Super God Mode: A PowerShell Shortcut Factory for Every Hidden Settings Page

What This Script Actually Solves

Windows hides a lot of its own surface area. The classic 'God Mode' folder gives you one view of Control Panel items, but it misses many modern Settings pages, shell folders, and URL protocols. This script addresses that by generating shortcuts to all of them at once. It is for people who know Windows well enough to want a single jump point for tasks like opening the BitLocker management page, the old-style folder options, or a specific CLSID shell folder. The README is explicit that this is not a 'mode' in any functional sense. Running it does not change any system settings. It only creates a folder with shortcuts. That distinction matters: the script is a navigation aid, not a tweaking tool. If you already know the exact ms-settings: URI for every page you use, you may not need it. But if you want a searchable, browsable index of what Windows offers, this script builds one for you.

The Mechanism: Harvesting Windows' Own Metadata

The script pulls shortcut targets from several sources. It reads CLSID shell folders from the registry, named special folders, task links that appear inside shell folders and Control Panel, ms-settings: URIs, and URL protocols. It also scans for 'hidden app links', which are undocumented URL links used by apps. The README says the script saves XML content retrieved from shell32.dll and other sources for reference. That suggests it parses the resource strings in shell32.dll to discover task links. The script then creates .lnk shortcut files in an output folder, grouping task links by application name unless you pass -DontGroupTasks. It also generates CSV files with shortcut details and a statistics folder. This is a read-only operation on Windows' own data, so the risk of breaking something is low. The main output is a folder full of shortcuts, each pointing to a real Windows feature.

Running It: From GUI to Full CLI Control

The easiest path is to download the .ps1 script and the launcher batch file, then run the batch file. That avoids typing anything. For direct execution, you open PowerShell in the script's folder and run: powershell.exe -ExecutionPolicy Bypass -File ".\Super_God_Mode.ps1". With no parameters, a GUI appears for configuration. For scripting or automation, you must use -NoGUI for most arguments to take effect. The README lists many switches. For example, -SkipMSSettings skips ms-settings: links, -AllURLProtocols includes third-party URL protocols from installed software, and -Output lets you specify a custom output folder. A full example is: .\Super_God_Mode.ps1 -Output "C:\SuperGodMode" -AllURLProtocols -Verbose. There is also a -uniqueOutputFolder argument that appends a unique identifier to the output folder name to prevent overwriting existing folders. This is useful if you run the script repeatedly with different settings. The CLI is well thought out for a PowerShell tool, though the requirement to add -NoGUI even for simple switches is a minor friction point.

Limitations: Broken Links and Version Drift

The README warns that some shortcuts may not work on all Windows versions due to differences in available features. That is the core limitation. Windows 10 and Windows 11 have different Settings pages, and even within Windows 11, feature updates move or remove entries. A shortcut that works on your current build may break after a feature update. The script cannot know which shortcuts are valid on your system; it just creates them. So you will likely end up with some dead shortcuts. The script also auto-deletes existing output folders before running unless you pass -KeepPreviousOutputFolders. That means if you point -Output at a folder you care about, it will be wiped. The README does not mention a dry-run mode, so you cannot preview what will be created without actually generating the folder. For a tool that creates hundreds of shortcuts, that is a real usability gap.

The Extra Tools: String Reference Utilities

The repository includes an Extra Tools folder with two additional PowerShell scripts. Get_DLL_String_Reference.ps1 takes a single string reference like @%SystemRoot%\system32\shell32.dll,-9227 and resolves it to the localized string. Windows_XML_String_Resolver.ps1 processes an entire XML file that contains string references, replacing them with the actual string values. The README says this is mostly intended for use with the XML from shell32.dll.mun that contains Windows task links. These tools are for developers or advanced users who want to understand how the main script resolves display names. They are not necessary for using the main script, but they show the project's depth. If you are debugging why a shortcut has a weird name, these utilities can help you trace the string reference back to its source.

Alternatives: Manual URIs and God Mode Folder

The obvious alternative is the built-in 'God Mode' folder. You create a new folder and rename it to GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}. That gives you a flat list of Control Panel applets, but it does not include ms-settings: pages or modern Settings deep links. Another alternative is to manually type ms-settings: URIs in the Run dialog (Win+R). For example, ms-settings:windowsupdate opens the Windows Update page. This works for a handful of pages you use often, but it requires you to remember the exact URI. The Super God Mode script automates the discovery of those URIs and turns them into double-clickable shortcuts. The difference is scale and discoverability. The manual approach is fine for five settings; this script is for when you want all of them in one place. A third option is to use a third-party launcher like PowerToys Run or Everything to search for settings by name, but those do not create persistent shortcuts and may not surface hidden app links.

Maintenance, Licensing, and Practical Concerns

The project is licensed under GPL-3.0. That means if you redistribute modified versions, you must share your source code under the same license. For personal use, this is a non-issue. The repository was last pushed in June 2026, and the latest release is v1.2.3 from that date. The README mentions that release versions are signed with an EV code signing certificate, which is a good sign for verifying integrity. However, the script depends on Windows internals like shell32.dll and SystemSettings.dll. Those change with each Windows release, so the script will need updates to stay accurate. The GitHub repository is the only source for those updates. If the project becomes unmaintained, the script will still work but will produce more broken shortcuts over time. The -CustomDLLPath and -CustomSystemSettingsDLLPath parameters suggest you can point the script at alternate DLLs, but that is for advanced debugging, not regular maintenance. Before adopting this in a managed environment, you should test it on a representative Windows version and check the generated shortcuts for correctness.

Editorial conclusion

Adopt this script if you are a Windows power user or IT professional who frequently navigates to obscure settings pages and wants a single folder with hundreds of shortcuts. Do not use it if you expect it to change system behavior or if you need a tool that works identically across all Windows versions; many shortcuts may not work on older or newer builds. Before running, verify the script's signature (releases are EV-signed) and test with -NoGUI and -Output to a non-default folder to avoid clobbering existing output. The script does not modify settings, so it is low-risk, but you must accept the output folder may contain broken links on your specific Windows version.

Official sources

1. Official README
2. Project repository
3. Release notes