CLI tool
ThioJoe/Windows-Super-God-Mode avatar
ThioJoe/Windows-Super-God-Mode

Windows-Super-God-Mode: it makes a folder of shortcuts, and your arguments need a flag

Project brief: Creates shortcuts to virtually every special location or action built into Windows.

2,078 stars144 forksPowerShellGPL-3.0

At a glance

What is it?
A single PowerShell script that resolves the localized labels out of the Windows shell DLLs and writes a folder of shortcuts pointing at every settings page, task link and URL protocol it can find. It changes no system settings, and every switch you pass is ignored unless you also pass the one that skips the graphical prompt.
Who is it for?
This is worth running on a machine you own if you have ever wanted to find the entry point for a settings page rather than hunt for it, and it is genuinely non-invasive: it writes shortcuts and files and nothing else. Three things to know.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 13 days ago.
What is it written in?
Mainly PowerShell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ThioJoe/Windows-Super-God-Mode2,078 ★ · +11
Star history
Repository2026-07-302026-11-21
ThioJoe/Windows-Super-God-Mode2.1k2.1k

11 Stars in the last 114 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A folder of shortcuts, and nothing else changes

The script's own disclaimer is the most useful paragraph in the file. It is not really a mode, it says; that is just a catchy name. Running it does not change any system settings, it just creates a folder containing a lot of shortcuts. That claim is repeated in the notes section almost word for word, with the addition that every parameter and every graphical setting is optional and the script runs with defaults if you change nothing. The idea came from the folder nicknamed God Mode that circulates online, and the file's claim on it is quantitative rather than rhetorical: it creates many more shortcuts than even that. So the deliverable is a directory of link files plus a few text and CSV artefacts describing them, which is also why the tool is safe to delete and safe to run twice with different switches.

Seven families of shortcut, one of them undocumented

The feature list enumerates what gets linked, and the categories differ in how official they are. Shell folders addressed by their class identifier are the base layer, and named special folders are the friendlier version of the same idea. Task links are the sub-pages inside shell folders and control panel menus. System settings are the ms-settings links Windows uses internally. Deep links are direct routes into settings menus. URL protocols are included, with a switch to add the ones belonging to third-party installed software. The seventh family is the interesting one: hidden app links, described as internal-use and undocumented URL links used by applications. That family is what makes the output larger than the God Mode folder, and it is also the part most likely to differ between Windows builds, since those routes are not a contract.

Arguments are ignored without the no-interface switch

One line decides whether the rest of the parameter documentation works, and it is easy to miss because it sits above the list rather than inside it. Except for the debug and verbose switches, you must pass the no-GUI switch for arguments to take effect. So a command that sets an output folder, adds third-party URL protocols and turns on verbose output needs three flags, not two:

powershell
.\Super_God_Mode.ps1 -Output "C:\SuperGodMode" -AllURLProtocols -Verbose

With no parameters at all, a graphical dialog appears for configuration, which is the friendly path and the reason the rule is not more prominent. The two debugging switches are exempt because they are also useful interactively, and a third one reports how long each section took to run and is turned on by the other two. There are also two switches that narrow the search rather than the output: one skips the packaged-app search and looks only at ordinary programs, and the other takes a comma-separated list of protocols to search for and nothing else.

Where the folder names come from

The labels on the shortcuts are not hard-coded, which is what lets the tool work in a non-English Windows. It retrieves XML content from shell32.dll and other sources and saves it for reference, and it resolves individual string references of the form a DLL path with a comma and a resource identifier. Two helper scripts in the Extra Tools folder exist to make that resolution manual: one prompts for a single reference and prints the localized string, with a worked example pointing at the system directory and a numeric identifier; the other walks whole XML files, substitutes the resolved strings and writes a new file, and is aimed at the task-link tables shipped with Windows. The advanced parameters let you point the script at a different copy of that DLL, a folder of language files, the system settings DLL, or an alternative copy of the all-system-settings XML, so a Windows Preview build or a different language can be targeted without editing the script.

Output folders are cleared before each run

Two parameters decide what happens to previous output. By default the script deletes existing output folders before running, which keeps a rerun from mixing results from two different configurations. Keeping them is a single switch. The other control is a folder name parameter, and it is the one place in the parameter list written without a leading dash, which means it reads as documentation of a switch rather than a switch you can type; if that matters to you, test it before relying on it. Output content is controlled separately: statistics can be suppressed so no statistics folder and files are written, and the tips text file can be suppressed too. The result of a full run is therefore not only shortcuts but a folder of CSV files describing them, which is the part worth keeping if you want to know what the machine actually exposes.

Nine switches turn whole families off

The parameter list has a block dedicated to limiting what gets created, and it covers every family plus the two report files. Shell folders by class identifier, named special folders, task links, system settings links, deep links, URL protocols and hidden app links each have their own skip switch, and the statistics folder and the readme file have theirs. Two of them are not about output at all: one prevents grouping task shortcuts by application name, and the other uses alternative category names for task links, which is the sort of switch that matters when the translated category names are wrong or duplicated on a particular build. A third collects extra information about URL protocols. Another is the switch to keep deep links that are exactly identical to an existing task link, which by default are skipped as duplicates.

Signed releases, and a two-year gap in the tag list

Release versions are signed with an extended validation code signing certificate, which is unusual for a script of this kind and means the execution policy bypass in the run instructions is not asking you to trust an unsigned download. The tag history is thinner than that suggests. Two releases were published on the same day in August 2024, and the next one came in June 2026, so the project went roughly two years between shipping anything. The last commit on the default branch is dated 2026-06-04, two days after that release. The notes section also warns that some shortcuts may not work on every Windows version because of differences in available features, which is the honest framing for a tool whose output depends on undocumented internal routes.

Editorial conclusion

This is worth running on a machine you own if you have ever wanted to find the entry point for a settings page rather than hunt for it, and it is genuinely non-invasive: it writes shortcuts and files and nothing else. Three things to know. The one rule that will waste your time is that arguments do nothing without the no-interface switch, with only the two debugging switches exempted, so read that line before anything else. Second, it scrapes undocumented internals, including the hidden links applications use internally and the string tables inside system DLLs, which means a Windows update can change what you get and some shortcuts will simply stop working on some builds. Third, two output directories in the repository carry spaces and capital letters, which matters if you script anything around them. Release versions are signed with an extended validation certificate.

Frequently asked questions

Does Windows-Super-God-Mode change any Windows settings?

No. The file says plainly that it is not really a mode, only a catchy name, and that running it does not change any system settings: it creates a folder containing a large number of shortcuts. Every parameter and graphical setting is optional, and the script runs with defaults if you change nothing.

How do I run Windows-Super-God-Mode from the command line?

Download the script, then hold Shift and right click the folder background to open a PowerShell window or a terminal there, and run powershell with the execution policy bypassed against the script path. With no parameters a graphical dialog appears; with parameters you must also pass the switch that skips that dialog, or they are ignored.

Why are my Windows-Super-God-Mode parameters being ignored?

Except for the debug and verbose switches, the file states you must pass the no-GUI switch for arguments to take effect. So a command setting an output folder and enabling extra URL protocols needs that switch too, otherwise the graphical dialog appears and the arguments do nothing.

What kinds of shortcuts does Windows-Super-God-Mode create?

Seven families: shell folders addressed by class identifier, named special folders, task links inside shell folders and control panel menus, system settings links, deep links into settings menus, URL protocols including optionally third-party ones from installed software, and hidden app links, which the file describes as internal-use and undocumented links used by applications.

Where do the shortcut names in Windows-Super-God-Mode come from?

From string references resolved out of shell32.dll and related language resources, of the form a DLL path, a dash, a resource identifier. The script saves the XML it retrieves for reference, exposes switches for a custom DLL path, a custom language folder, the system settings DLL and an alternative XML file, and ships two helper scripts that resolve one reference or a whole XML file on demand.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thiojoe-windows-super-god-mode.svg)](https://hysenlabs.com/projects/thiojoe-windows-super-god-mode)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thiojoe-windows-super-god-mode.svg)](https://hysenlabs.com/projects/thiojoe-windows-super-god-mode)

Was this useful?