How to Disable InPrivate Browsing in Microsoft Edge on Windows 10 and 11

·
5 min read

Help Desk Geek is reader-supported. We may earn a commission when you buy through links on our site. Learn more.

If you need to block InPrivate browsing in Microsoft Edge, whether for company policy or household monitoring, Group Policy or a registry value gets it done in under five minutes. Windows Home users without gpedit.msc should go straight to Fix #2.

Fix #1: Disable InPrivate browsing in Edge via Group Policy

Group Policy is the cleanest approach on Windows 10 or 11 Pro, Enterprise, or Education. The setting you want is Configure InPrivate mode availability, inside the Microsoft Edge administrative template.

  1. Press Windows + R, type gpedit.msc, and press Enter to open Local Group Policy Editor.
  2. In the left pane, go to Computer Configuration > Administrative Templates > Microsoft Edge.
  3. In the right pane, double-click Configure InPrivate mode availability.
Local Group Policy Editor open at Computer Configuration > Administrative Templates > Microsoft Edge, with "Configure InPrivate mode availability" visible and highlighted in the right pane
  1. Select Enabled.
  2. In the Options drop-down, choose InPrivate mode disabled.
Configure InPrivate mode availability policy dialog with Enabled selected and "InPrivate mode disabled" chosen in the Options drop-down
  1. Click OK.
  2. Open an elevated Command Prompt, run gpupdate /force, and press Enter, or just restart Edge.

The New InPrivate window entry in Edge’s menu will be greyed out after that.

Don’t see “Configure InPrivate mode availability”? Your Edge ADMX templates may be outdated. Look for Allow InPrivate browsing under Computer Configuration > Administrative Templates > Windows Components > Microsoft Edge instead. Setting that to Disabled has the same effect on older template versions.

Fix #2: Disable InPrivate browsing in Edge via Registry

This method works on every Windows edition, including Home. It writes the same policy the Group Policy Editor applies, directly into the registry.

  1. Press Windows + R, type regedit, and press Enter to open Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge.

– If the Edge key doesn’t exist, right-click the Microsoft key, choose New > Key, and name it Edge.

  1. In the right pane inside the Edge key, right-click and select New > DWORD (32-bit Value).
  2. Name the value InPrivateModeAvailability.
Registry Editor at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge with a new DWORD value named InPrivateModeAvailability highlighted in the right pane
  1. Double-click InPrivateModeAvailability and set Value data to 1.
  2. Click OK and close Registry Editor.
  3. Fully close Edge and confirm no msedge.exe processes remain in Task Manager, then reopen it.

The InPrivate option should now be greyed out in Edge’s menu. To undo this later, set InPrivateModeAvailability back to 0 or delete the value entirely.

Heads up on older registry guides. Many instructions still point to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\MicrosoftEdge\Main with a value called AllowInPrivate. That path doesn’t work with Chromium-based Edge. The correct location for modern Edge is InPrivateModeAvailability under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge.

Legacy: Internet Explorer and IE Mode

Internet Explorer is retired and disabled on modern Windows. If your organization still runs IE Mode inside Edge for specific legacy web apps, you can disable InPrivate browsing for that context separately.

  1. Open Registry Editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Privacy.

– Create the Internet Explorer and Privacy subkeys under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft if they don’t already exist.

  1. In the Privacy key, right-click the right pane and choose New > DWORD (32-bit Value).
  2. Name it EnableInPrivateBrowsing and set Value data to 0.
  3. Close Registry Editor. No restart needed. Just close and reopen IE or reload the IE Mode tab in Edge.
Registry Editor showing HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Privacy with EnableInPrivateBrowsing DWORD value set to 0

For most environments running current Windows, the Edge fixes above are what you actually need.

Troubleshooting

“Configure InPrivate mode availability” doesn’t appear in the list. The Edge ADMX templates are likely missing or out of date on that machine. Look for Allow InPrivate browsing under Windows Components > Microsoft Edge and set it to Disabled. That’s the older policy name for the same control.

Users can still open InPrivate after the registry edit. Four things to verify:

  • The key path is exactly HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge, not under HKEY_CURRENT_USER, not under any non-Policies path.
  • The value name is exactly InPrivateModeAvailability, not AllowInPrivate.
  • The value data is 1.
  • Edge was fully closed. Open Task Manager, end all msedge.exe processes, and relaunch Edge.

InPrivate is blocked but users are opening Guest mode. The InPrivate policy doesn’t affect Guest mode. That’s a separate Edge policy setting you’d need to configure independently.

Does disabling InPrivate cover all unmonitored browsing? InPrivate only prevents local history and cookies from being saved when the window closes. Network traffic stays visible to proxies and logging tools regardless. For stricter compliance, pair the InPrivate policy with a network-level proxy or secure web gateway that captures traffic at the infrastructure layer. If you manage a larger fleet, Microsoft Intune lets you push InPrivateModeAvailability across every device through configuration profiles, which is far more consistent than editing individual machines by hand.

Conclusion

Fix #1 (Group Policy) is the right pick for Pro, Enterprise, and Education machines. One policy setting, no registry work, and it holds across Edge updates. For Windows Home, the InPrivateModeAvailability registry key gets the same result just as reliably. Worth keeping in mind: a determined user can route around any browser restriction using a VPN or a mobile hotspot, so a network-level proxy or secure web gateway that logs traffic independently will always be a more durable audit trail than browser policy alone.