How To Enable Developer Mode On Windows 11 | Three Working Routes

Enabling Developer Mode on Windows 11 is done from Settings under System > Advanced, though the exact menu label varies by build—this guide covers all three verified methods.

Developer Mode unlocks a handful of system-level capabilities that developers need: sideloading apps, running Windows Subsystem for Linux, accessing the Device Portal, and using certain debugging tools. It’s not a hardware-killing switch—Microsoft’s own disclaimer calls it a development setting that “exposes additional developer-related settings” and changes some default system behaviors. The toggle takes about ten seconds to flip once you know where to look.

Where Microsoft Hides the Developer Mode Toggle

The Settings path changed between Windows 11 builds, and that’s where most people get confused. Current Microsoft Learn documentation places the toggle at Settings > System > Advanced—scroll to the For developers section, flip the switch, read the one-time disclaimer, and click Yes. Older builds and some third-party guides still show it under Privacy & security > For developers or simply System > For developers. If you open your Settings app and don’t see Advanced, check Privacy & security first—the toggle lives at whichever path your build uses.

What Happens After You Flip The Switch

Once confirmed, Developer Mode stays on until you turn it off. Here’s what it actually does for you:

• App sideloading opens up. You can install apps directly from outside the Microsoft Store without signing into a developer account.
• Windows Subsystem for Linux (WSL) and Windows Subsystem for Android become available for install and operation.
• Device Portal and Device Discovery features activate — these let you remotely manage and debug the machine over a network.
• SSH server becomes an optional install through Optional Features.
• A file-symlink creation permission grants developers the ability to create symbolic links without elevated privileges.

The change is immediate. No restart required, though some tools like WSL may need you to complete a separate setup after rebooting.

Method 1: Via Settings (Most Direct Route)

This is the primary method Microsoft documents, and it works on every edition of Windows 11, including Home. The only variable is the exact menu name your build uses.

1. Press Windows + I to open Settings.
2. Click System in the left sidebar.
3. Look for Advanced and click it. If you don’t see Advanced, click Privacy & security and then For developers.
4. Toggle Developer Mode to On.
5. Read the one-time warning that explains what changes—Microsoft is upfront that this “exposes additional developer-related settings and capabilities.”
6. Click Yes to confirm.

The toggle fills in blue and stays on. No reboot or additional steps are needed for the setting to apply.

Method 2: Via Group Policy (Pro, Enterprise, or Education Only)

For devices on Windows 11 Pro or higher, Group Policy offers an alternative path—useful when admins need to push the setting across multiple machines.

1. Press Windows + R, type gpedit.msc, and press Enter.
2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > App Package Deployment.
3. Double-click Allow development of Windows Store apps without installing a developer license.
4. Set it to Enabled, then click OK.

The policy shows as “Enabled” in the Group Policy Editor. You may need to run gpupdate /force in an admin Command Prompt for it to apply immediately.

This method doesn’t trigger the Settings toggle—the policy overrides it. If you check Settings afterward, the Developer Mode toggle may still appear off even though the behavior is active. That’s normal.

Method 3: Via Registry (All Editions, Including Home)

The registry method works on every edition and is especially useful when Group Policy isn’t available or when you’re scripting deployments.

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock.
3. If you don’t see a DWORD called AllowDevelopmentWithoutDevLicense, right-click in the right pane, select New > DWORD (32-bit) Value, and name it exactly that.
4. Double-click that DWORD and set the value to 1.
5. Click OK and close regedit.

The DWORD now shows a value of 1. A reboot is recommended to ensure all components pick up the change.

Microsoft also documents a related DWORD at the same path: AllowAllTrustedApps. Setting both to 1 handles both developer mode and sideloading of trusted (non-Store) apps in one trip.

When The Toggle Isn’t Visible At All

A few readers report opening Settings and finding no For developers section under either System > Advanced or Privacy & security. Microsoft’s own Q&A guidance says to check prerequisites first. The most common causes:

• Corporate-managed device. Group Policy or MDM settings pushed by IT can hide or disable the toggle. Check with your admin before trying workarounds.
• Outdated build. Developer Mode requires a relatively recent Windows 11 release. Run Windows Update and install all pending feature updates, then check again.
• Edition limitation. All Windows 11 editions support the Settings toggle—Home included—so this is rarely the cause, but it’s worth verifying under Settings > System > About if you’re stuck.

When the Settings toggle genuinely can’t be found after an update, the registry method (Method 3) bypasses the UI entirely and works on every edition.

Common Mistakes That Trip People Up

The most frequent error is looking under the wrong Settings section based on outdated documentation. Microsoft moved the path from Privacy & security to System > Advanced in newer builds, but many third-party guides still reference the old location. If your build doesn’t show it at first path, check the other—it’s there.

Another mistake is expecting Developer Mode to enable app sideloading without also setting the separate sideloading policy. The registry DWORD AllowAllTrustedApps handles that part independently. If you only enable Developer Mode, some sideloading scenarios still fail until you toggle that second DWORD.

Group Policy users on Windows 11 Home hit a wall—gpedit.msc simply isn’t installed. The registry method is your backup and requires no edition-specific features.

Verifying That Developer Mode Is Active

After enabling it through any method, the cleanest way to confirm it’s working is to check whether developer-specific features have unlocked. Look for these signs:

• WSL appears as an installable feature. Open Settings > Apps > Optional Features and search for “Windows Subsystem for Linux”—if it’s available to install, Developer Mode is on.
• Device Portal activates. Search for “Device Portal” in the Start menu. If the option appears, it’s working.
• App sideloading works. Download a trusted .appxbundle from a known source. If Windows allows the install without a developer license prompt, the setting is active.