iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To enable the Windows 11 feature commonly called God Mode, create a folder and rename it exactly to GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}. Press Enter, then open the renamed folder. It becomes an Explorer view of Windows’ All Tasks namespace. The word GodMode is only a label; the CLSID after the period is what selects the Shell object.
You can reach the same view without creating a folder by running explorer.exe shell:::{ED7BA470-8E54-465E-825C-99712043E01C}. These methods expose a convenient collection of Shell and Control Panel tasks. They do not make your account an administrator, remove permission checks, or bypass security controls.
What Windows 11 “God Mode” actually is
“God Mode” is an informal name for a Shell namespace view associated with All Tasks. Windows Explorer normally shows folders and files from the disk, but its Shell namespace also contains virtual objects. Control Panel pages and other system locations can appear in that namespace even though they are not ordinary directories with files inside them.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsThe special folder works because Windows recognizes a naming convention documented by Microsoft for namespace junctions. A normal folder name is followed by a period and the string form of a registered class identifier (CLSID). Microsoft describes the mechanism as creating a folder in the appropriate location and appending a period followed by the CLSID of the extension. Explorer interprets the suffix as an instruction to open the corresponding Shell object.
#1 Best Overall
In this recipe, {ED7BA470-8E54-465E-825C-99712043E01C} identifies the All Tasks view. The visible prefix can be changed to another descriptive label, while the identifier must remain exact. A missing brace, an altered character, or a misplaced hyphen prevents the junction from resolving correctly.
Create the God Mode folder in Windows 11
The folder can live on the Desktop, in Documents, or in another location where you want a reusable entry point. The location does not change the namespace object; it only determines where the icon is stored.
-
Open File Explorer and browse to the location you want to use. The Desktop is convenient for a first setup because the result is easy to find.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Right-click an empty area, choose New, and select Folder.
-
Right-click the new folder, choose Rename, and enter this complete name:
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} -
Press Enter. Keep the period between the label and the opening brace. Keep both braces and every hyphen in the CLSID.
-
Open the resulting folder. Explorer should display the All Tasks view instead of an empty, ordinary directory.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Windows may replace the folder’s displayed icon and may hide the suffix after it recognizes the namespace object. That is expected. The object is still selected by the CLSID even when Explorer shows only a friendly label.
Choosing and changing the label
Only the text before the period is a user-facing label. You can use names such as All Windows Tasks, System Tools, or a team-specific description. To rename it later, preserve the period and the full CLSID suffix. For example, System Tools.{ED7BA470-8E54-465E-825C-99712043E01C} targets the same view as the original name.
Do not remove the suffix while renaming. If you want an ordinary folder again, create a separate folder rather than trying to edit the special folder into a normal container.
Rank #2
Open All Tasks without creating a folder
For a one-time visit, or when you prefer not to leave an icon in a folder, use Explorer’s Shell syntax.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
-
Press Windows key + R to open the Run dialog, or open a Command Prompt.
-
Enter:
explorer.exe shell:::{ED7BA470-8E54-465E-825C-99712043E01C} -
Press Enter. Explorer should open the same All Tasks namespace associated with the folder recipe.
The three-colon form is significant: shell::: tells Explorer to resolve the following identifier as a Shell namespace object. Omitting the colons, inserting a space, or changing the CLSID can cause Explorer to treat the input as an ordinary path and fail to open the view.
Turn the command into a reusable shortcut
A shortcut can save the command without requiring a special folder. On the Desktop, right-click an empty area, choose New, then Shortcut. In the location field, enter the complete command explorer.exe shell:::{ED7BA470-8E54-465E-825C-99712043E01C}, choose Next, give the shortcut a clear name, and select Finish. This shortcut and the CLSID-named folder point to the same Shell object; they differ only in how you launch it.
Folder or command: which access route fits?
| Characteristic | CLSID-named folder | Explorer command or shortcut |
|---|---|---|
| Initial setup | Create and rename one folder in File Explorer. | Run one command, or create a shortcut containing it. |
| Where it appears | Any chosen folder location, commonly the Desktop. | Only when you run the command, unless you save a shortcut. |
| What it opens | All Tasks for the specified CLSID. | The same All Tasks object for the specified CLSID. |
| Best use | A visible, reusable icon for frequent access. | A clean Desktop, scripting notes, or occasional access. |
| Privileges | No privilege elevation. | No privilege elevation. |
| Failure point | An inaccurate folder name or damaged suffix. | A mistyped command or CLSID. |
Neither route changes account membership, grants access to protected files, or converts standard users into administrators. A task opened from All Tasks still enforces the permissions required by the underlying Windows component.
Why the CLSID suffix matters
A CLSID is a registration identifier used by Windows components. In this naming convention, the identifier is not decorative text. Explorer parses the part after the period and uses it as a junction target in the Shell namespace. That is why two folders with different visible labels can open exactly the same view when their suffixes match.
Microsoft Learn’s “Specifying a Namespace Extension’s Location” describes the convention directly: “The simplest approach is to create a folder in the appropriate location and append a period to the folder’s name, followed by the string form of the CLSID of your extension.” The sentence applies to namespace extensions generally; the All Tasks mapping in this guide uses the specific identifier shown above.
Free tools Windows power users keep installed
One-click scans. No signup required.
The Shell namespace is a tree rather than a simple reflection of the disk. It can combine file-system locations with virtual objects, including Control Panel applications. The All Tasks object therefore presents links to settings and management pages as Shell items. It is not a second copy of Windows settings and it does not contain independent configuration data.
Rank #3
Because the identifier selects a registered object, arbitrary strings are not interchangeable. A CLSID that belongs to a different extension will resolve to that extension, if it is registered on the system. An unregistered or unsupported identifier may open nothing, produce an error, or behave differently across Windows releases.
Creating other CLSID shell folders safely
The general pattern is:
DisplayName.{CLSID}
Replace DisplayName with the label you want and replace {CLSID} with the exact identifier of a registered Shell namespace extension. Microsoft documents this as a way to define a file-system folder as a junction point to a namespace extension.
Verify the identifier before using it
This Windows 11 guide does not establish a primary-source catalog of additional built-in CLSIDs with dependable behavior. Do not copy an unverified list from a random post and assume every entry works on every edition or build. Before creating a new junction, confirm all of the following:
- The identifier is documented for the Shell extension you intend to open.
- The documentation applies to your Windows edition and build, or clearly states its compatibility limits.
- The identifier includes braces, hyphens, and characters exactly as published.
- You have a recovery plan if Explorer opens an unexpected namespace object.
Testing an identifier by creating a clearly named folder in a temporary location limits confusion. If it does not resolve, delete that test folder and do not infer that a similar-looking identifier is valid.
The Desktop.ini alternative
Microsoft also documents an alternative for a conventionally named folder. The folder is made read-only and a system folder, then a hidden Desktop.ini file is added with a [.ShellClassInfo] section containing CLSID={Extension CLSID}. This lets a folder retain a conventional visible name while associating it with a namespace extension.
This method is documented for namespace extensions, not as a universal recipe for every built-in Windows folder. It involves hidden and system attributes and can make troubleshooting harder. For a personal All Tasks shortcut, the direct DisplayName.{CLSID} method is simpler and easier to undo.
Registry-based namespace placement
For registered namespace extensions, Microsoft describes registry-based placement beneath a virtual folder’s NameSpace key. Examples include locations such as Control Panel, Desktop, My Computer, and Users Files. This is an administrator or developer technique, not a necessary step for the God Mode folder.
Do not create arbitrary registry entries based only on a name found online. A wrong identifier or key can add confusing Explorer items and complicate recovery. Use registry registration only when you have a verified CLSID, a documented target location, and a backup or rollback procedure appropriate for the machine.
What All Tasks can and cannot show
The All Tasks view is a convenience index into Windows’ Shell and Control Panel tasks. The exact entries shown are not established as identical across every Windows 11 edition and build. Components installed, policy settings, and the current release can affect what appears. Treat the view as a navigation aid, not a guaranteed inventory of every setting on every computer.
Some entries may open a modern Settings page, while others may open a legacy Control Panel dialog or an administrative console. The namespace does not rewrite those tools into one interface. If a particular task is absent, the absence does not prove that the underlying capability has been removed; it may be edition-specific, policy-controlled, or exposed elsewhere in your build.
Rank #4
Practical workflow for using the view
Use the All Tasks folder as an index, not as a replacement for learning what each setting changes. Open an entry, read the page title and available controls, and confirm that you are changing the intended scope before selecting Apply, Save, or an administrative action.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If you manage several PCs, keep the shortcut name descriptive rather than relying on the informal “God Mode” label. A name such as Windows 11 - All Tasks tells another user what the icon opens without implying elevated rights. The same label can be used for a Desktop shortcut and a CLSID-named folder, but only the suffix or command determines the target.
For troubleshooting, first test the known All Tasks identifier in a temporary location. Once it opens correctly, move or rename the entry by changing only the label portion. This separates a syntax problem from a location or Explorer-refresh problem and avoids experimenting with several unknown CLSIDs at once.
Remember that opening a task and completing it are separate operations. A page may be visible to a standard account while a specific change requires administrator approval, a policy exception, or access to a service that is not installed. The namespace makes the page easier to find; it does not alter those prerequisites.
Troubleshooting a folder that does not work
The name remains an ordinary folder
- Check that the period appears immediately before the opening brace.
- Compare every CLSID character with
{ED7BA470-8E54-465E-825C-99712043E01C}. - Make sure the closing brace is present.
- Rename the folder again, then press Enter and wait for Explorer to refresh.
If the name was pasted with an extra space or a typographic dash, replace it with the plain ASCII period and hyphens shown above.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Explorer reports that the location is unavailable
The identifier may be mistyped, unregistered, or unsupported by that Windows build. Delete the failed test folder and try the documented All Tasks identifier again. If the standard identifier also fails, use the direct command in the Run dialog to distinguish a naming problem from a broader Explorer problem.
The command does nothing or opens a search
Enter the command as one line, including explorer.exe, the three colons, braces, and hyphens. Do not wrap the CLSID in quotation marks unless you are placing the command in a context that specifically requires quoting. Running it from the Run dialog avoids path parsing issues caused by a different shell.
A task asks for administrator approval
That prompt belongs to the task you selected, not to God Mode itself. The namespace view does not elevate privileges. Approve the operation only when you understand what the underlying tool will change and your account is authorized to make that change.
A task is missing from the view
Do not assume the folder is damaged. The available entries can vary by Windows 11 edition, build, installed components, and policy. Use the specific Settings or Control Panel search for the function you need, and avoid claiming that the All Tasks view is exhaustive.
Recommended Free Tools
Remove, rename, or relocate the shortcut
To remove the entry, close any Explorer window displaying it, select the CLSID-named folder or shortcut, and delete it as you would any other user-created item. Deleting the junction does not uninstall Windows components and does not remove the settings it links to.
Best Value
To relocate it, move the folder to another location in File Explorer. The namespace target remains the same because the CLSID suffix travels with the folder name. To keep the icon but change its wording, rename only the text before the period and preserve the suffix exactly.
If you created a shortcut with the Explorer command, delete the shortcut rather than changing system files. A shortcut is independent of the namespace registration and can be recreated from the documented command whenever needed.
Safety and scope checklist
- Use the exact identifier:
{ED7BA470-8E54-465E-825C-99712043E01C}is the identifier used by the common All Tasks recipe. - Keep expectations realistic: this is a navigation shortcut, not a hidden administrator account or security bypass.
- Preserve the syntax: the folder form needs
DisplayName.{CLSID}; the command form needsexplorer.exe shell:::{CLSID}. - Verify other CLSIDs: do not treat an unverified identifier list as a dependable Windows 11 catalog.
- Limit registry changes: registry-based placement is for documented extensions and controlled administration, not casual experimentation.
- Expect build differences: the tasks displayed by All Tasks are not established as identical across all Windows 11 editions and releases.
Bottom line
Create GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} in File Explorer for a persistent All Tasks icon, or run explorer.exe shell:::{ED7BA470-8E54-465E-825C-99712043E01C} for immediate access. The CLSID—not the “GodMode” label—does the work. Use the documented DisplayName.{CLSID} pattern for other namespace folders only after verifying each identifier for the Windows build you manage.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Does Windows 11 God Mode provide administrator privileges?
No. It is a Shell namespace view that gathers links to tasks. It does not add your account to Administrators, bypass User Account Control, unlock protected files, or change permissions. Individual tools may still request approval when you attempt a restricted operation.
Can I rename the God Mode folder after creating it?
Yes. Change only the text before the period, such as replacing GodMode with System Tools. Keep the period and the complete {ED7BA470-8E54-465E-825C-99712043E01C} suffix unchanged.
Is the folder safe to delete?
Yes, when it is the user-created CLSID folder or shortcut described here. Close Explorer windows that use it, then delete the item normally. Removing the junction removes only the entry point; it does not uninstall Windows components or erase settings.
Why does my folder stay ordinary instead of opening All Tasks?
The usual causes are a missing period, an incorrect brace or hyphen, an extra space, or a typographic dash introduced while copying. Rename it with the exact ASCII string, press Enter, and allow Explorer to refresh. You can also test the direct Explorer command to separate a naming error from an Explorer issue.
Will every Windows 11 PC show the same All Tasks entries?
Not necessarily. The visible tasks can vary by edition, build, installed components, and policy. Some entries open modern Settings pages and others open legacy Control Panel or administrative tools. The view should not be treated as an exhaustive inventory.
Can I create folders for other CLSIDs?
The documented general form is DisplayName.{CLSID}, but the identifier must belong to a registered namespace extension and be verified for the Windows build you use. An unknown CLSID can fail, open an unexpected object, or behave differently between releases. Test unfamiliar identifiers in a temporary location.
What is the difference between a CLSID folder and the Explorer command?
Both target the same Shell object when they use the same identifier. The folder leaves a reusable icon in a location you choose. The command, or a shortcut containing it, is better for one-time access or a cleaner Desktop. Neither method elevates privileges.
Do I need Desktop.ini or a registry edit for the common recipe?
No. The direct folder name is sufficient for the All Tasks shortcut. Microsoft documents Desktop.ini and registry-based placement as alternatives for namespace-extension scenarios, but they add hidden attributes or system configuration and are not required for this personal shortcut.
The Bottom Line
Use GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} for a reusable All Tasks folder, or run explorer.exe shell:::{ED7BA470-8E54-465E-825C-99712043E01C} for immediate access. The CLSID selects the namespace object; the label does not grant extra rights.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

