Skip to content
TroubleGrid

PowerToys Settings won't open on Windows 10 – only the tray icon appears (0x80131506)

Last verified November 2026Tested against PowerToys 0.102.3101.0 (November 2026) - current reports, PowerToys 0.101.2432.0 and 0.101.2712.0, PowerToys 0.99.1 - same shadow-stack crash reported at startup, Windows 10 22H2/21H2 builds older than KB5044273 (Oct 2024; builds 19045.5011 / 19044.5011), Reported KERNELBASE/ntdll versions: 10.0.19041.2193, 10.0.19041.2913Good evidence

If PowerToys sits in the tray but its Settings window never opens on Windows 10, check Event Viewer for PowerToys.Settings.exe crashing with 0x80131506. That is the .NET runtime PowerToys ships with failing at startup on a Windows 10 build that lacks Microsoft's shadow-stack (CET) fixes. Install all pending Windows updates (October 2024's KB5044273, build 19045.5011, or later is confirmed fixed); if you can't update yet, turn off Hardware-enforced Stack Protection for PowerToys.Settings.exe only, in Windows Security's Exploit protection settings.

Reinstalling PowerToys, wiping its AppData folders, installing .NET 8 or running sfc /scannow does not fix this, because nothing is wrong with the PowerToys install. Since .NET 9, Microsoft builds the .NET app host with hardware-enforced stack protection (CET) switched on, and PowerToys now ships its own .NET runtime (0.100 moved it to .NET 10). Windows 10 builds that missed the fixes Microsoft shipped for CET make those apps die during runtime start-up, before a window is drawn. Every report so far is on Windows 10, and Microsoft's .NET team says fully patched Windows 10 is supported.

Symptoms

  • PowerToys starts and its tray icon appears, but double-clicking it or choosing Settings opens nothing
  • Event Viewer > Windows Logs > Application shows an Application Error (Event ID 1000) or Windows Error Reporting APPCRASH (Event ID 1001) for PowerToys.Settings.exe
  • The error lists faulting module KERNELBASE.dll and exception code 0x80131506
  • Other PowerToys tools such as Awake, Color Picker, Text Extractor (PowerOCR) or the FancyZones editor may crash the same way
  • A clean reinstall of PowerToys, installing .NET 8 or running as administrator makes no difference

Why this happens

.NET 9+ apps require Windows 10's CET fixes, and the PC doesn't have them

Microsoft marked the .NET 9 app host CET-compatible, so .NET 9 and later apps run with hardware-enforced stack protection where Windows and the CPU support it. Microsoft's .NET team says some older Windows 10 builds have bugs in that support and that only fully patched Windows 10 is supported; on those builds .NET 9+ apps fail at start-up with 0x80131506 while .NET 8 apps on the same machine still run. Both current PowerToys reports show a KERNELBASE/ntdll version (10.0.19041.2913 or older) that predates the fixed 10.0.19041.5007 delivered by KB5044273.

Confirm it is this crash: check Event Viewer and your Windows build · Install every pending Windows 10 cumulative update · If you can't update yet: turn off Hardware-enforced Stack Protection for PowerToys Settings only

Fixes

Confirm it is this crash: check Event Viewer and your Windows build

about 3 min

The fix only applies if Settings is crashing with 0x80131506 on an older Windows 10 build; two minutes here saves an unnecessary reinstall.

Applies to: Windows 10 22H2 and 21H2

  1. Try to open PowerToys Settings once so a fresh crash is logged.
  2. Press Win+R, run eventvwr.msc, and open Windows Logs > Application. Look for an Error from Application Error (Event ID 1000) or Windows Error Reporting (Event ID 1001) naming PowerToys.Settings.exe.
    eventvwr.msc
  3. In the event details, check for faulting module KERNELBASE.dll and exception code 0x80131506. If you see those, this article is your problem. Note the KERNELBASE.dll version shown (for example 10.0.19041.2913).
  4. Press Win+R and run winver. If it shows Windows 10 with an OS Build below 19045.5011 (22H2) or 19044.5011 (21H2), your Windows is older than the update confirmed to contain the fix.
    winver

Reported to work by 4 users; not confirmed by the vendor.

Source: Microsoft PowerToys (GitHub), Microsoft PowerToys (GitHub), Microsoft PowerToys (GitHub), Microsoft Support, .NET runtime (GitHub)

Install every pending Windows 10 cumulative update

about 45 min

The .NET team's position is that .NET 9+ supports only fully patched Windows 10; the October 2024 update KB5044273 delivers an ntdll.dll (10.0.19041.5007) confirmed to contain the CET fixes.

Applies to: Windows 10 22H2 and 21H2 below build 19045.5011 / 19044.5011

  1. Open Settings > Update & Security > Windows Update and select Check for updates. Install everything offered, restart, and check again until nothing new appears.
  2. Run winver again and confirm the OS Build is 19045.5011 / 19044.5011 or later. Microsoft has not published a complete list of which earlier builds already include the fix, so treat a build at or above KB5044273 as the known-good target.
    winver
  3. Quit PowerToys from the tray icon, start it again and open Settings. You do not need to reinstall PowerToys or install any separate .NET runtime: PowerToys Settings carries its own.

Confirmed by the vendor.

Source: .NET runtime (GitHub), .NET runtime (GitHub), Microsoft PowerToys (GitHub), Microsoft Support

If you can't update yet: turn off Hardware-enforced Stack Protection for PowerToys Settings only

Check before applyingabout 5 min

Microsoft documents opting a single .NET app out of hardware stack enforcement in Windows Security as a workaround for CET start-up failures; it leaves every other program protected.

Applies to: Windows 10 with the Hardware-enforced Stack Protection option shown in Exploit protection

Before you do this

This switches off a security mitigation (protection against return-oriented-programming exploits) for the PowerToys executables you add. Apply it per program, never system-wide, and undo it after you update Windows. If the PC is managed by work or school, exploit protection may be controlled by policy and your change can be overridden.

  1. Open Windows Security and go to App & browser control > Exploit protection settings, then the Program settings tab.
  2. Select Add program to customize > Choose exact file path and pick PowerToys.Settings.exe. For a per-user install it is in %LocalAppData%\PowerToys\WinUI3Apps; for a machine-wide install look under C:\Program Files\PowerToys.
    %LocalAppData%\PowerToys\WinUI3Apps\PowerToys.Settings.exe
  3. In the list of mitigations, find Hardware-enforced Stack Protection, tick Override system settings, switch it Off, and select Apply.
  4. Quit PowerToys from the tray and start it again, then open Settings. App-level changes do not need a Windows restart.
  5. If another PowerToys tool crashes the same way (check Event Viewer for its .exe name), add the same override for that file too - one user needed it for %LocalAppData%\PowerToys\PowerToys.FancyZonesEditor.exe.
  6. Once Windows is fully updated, remove these overrides from the Program settings list so PowerToys is protected again.

Confirmed by the vendor.

Source: Microsoft Learn, Microsoft Learn, Microsoft PowerToys (GitHub), Microsoft PowerToys (GitHub)

Known issues

  • .NET 9 and later apps, including PowerToys, fail at start-up with 0x80131506 on Windows 10 builds that lack the CET fixes; Microsoft's position is that only fully patched Windows 10 is supported.

    Affects Windows 10 builds before KB5044273 (19045.5011 / 19044.5011), PowerToys 0.99.1 through 0.102.3101.0 · Status: workaround only

If none of this worked

If Event Viewer shows no PowerToys.Settings.exe crash, or a different exception code, this article is not your problem; use Report bug in the PowerToys tray menu to collect the logs maintainers ask for, and open a GitHub issue. If you are on Windows 11, or on Windows 10 already at build 19045.5011 or later, the CET explanation does not fit either. One user on PowerToys 0.101.2712 reported the same 0x80131506 crash and doubted CET was the trigger on their hardware, and no fix has been posted for them yet, so if updating Windows does not help, add your Event Viewer details to the existing GitHub issue rather than reinstalling Windows.

Common questions

Do I need to install .NET 8 or the .NET Desktop Runtime?
No. A PowerToys collaborator confirmed that PowerToys Settings is self-contained when installed correctly, so separately installed .NET runtimes are not used and repairing them does not help.
Why did this start after a PowerToys update when Windows didn't change?
PowerToys moved to newer .NET runtimes (0.100 moved to .NET 10), and since .NET 9 those runtimes run with hardware-enforced stack protection. The Windows 10 bug was already there; the new runtime is what exposes it.
Should I just disable shadow stacks for the whole system?
No. One reporter did that, but it removes the protection from every program. Microsoft's documented workaround is a per-application opt-out, and updating Windows removes the need for any override.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • .NET runtime (GitHub) · GitHub issue · checked Nov 19, 2026

    • .NET 9 apps with CET enabled fail to launch on older, unpatched Windows 10 22H2 builds
    • A .NET team member said the problem is in out-of-support Windows builds with CET issues and that the runtime supports only fully patched operating systems
    • ntdll.dll 10.0.19041.5007 includes the fixes; KB5044273 (October 2024) was identified as an update that delivers it, and no complete list of fixed ntdll versions exists
    • The original reporter said installing KB5048652 resolved the launch failure
  • .NET runtime (GitHub) · GitHub issue · checked Nov 19, 2026

    • 0x80131506 at startup on Windows 10 22H2 affects .NET 9 and later apps while .NET 8 apps still run on the same machine
    • The reporter saw PowerToys 0.101 modules (PowerOCR, Awake, ColorPickerUI) crash the same way
    • A .NET team member closed it as CET-related on .NET 9+, saying the OS is too old and misses fixes from summer 2022 and only fully patched Windows 10 is supported
  • Microsoft Learn · Documentation · checked Nov 19, 2026

    • Starting in .NET 9, apphost and singlefilehost are marked CET-compatible (/CETCOMPAT), adding hardware-enforced stack protection
    • Microsoft's documented workaround includes using the Windows Security app or Group Policy to opt a specific .NET application out of hardware-supported stack enforcement
  • Microsoft Learn · Documentation · checked Nov 19, 2026

    • Per-app mitigations are set in Windows Security under App & browser control, Exploit protection settings, Program settings, Add program to customize
    • Choose exact file path selects a specific executable; Override system settings must be selected for the per-app value to apply
    • App-level exploit protection settings do not require a device restart
  • Microsoft Support · Knowledge base · checked Nov 19, 2026

    • KB5044273 was released on 8 October 2024 and brings Windows 10 to OS builds 19044.5011 and 19045.5011
  • Microsoft Windows Command Line blog · Release notes · checked Nov 19, 2026

    • PowerToys 0.100 (9 June 2026) upgraded the project to .NET 10
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 19, 2026

    • On PowerToys 0.102.3101.0 under Windows 10 22H2, PowerToys runs in the tray but the Settings window never opens
    • Event logs show PowerToys.Settings.exe crashing in KERNELBASE.dll with exception code 80131506
    • Clean reinstall, deleting PowerToys AppData folders, installing or repairing .NET 8, running as administrator and sfc /scannow did not fix it
    • A PowerToys collaborator diagnosed a .NET runtime startup failure caused by an ntdll (10.0.19041.2913) that predates the Windows fixes needed for CET, and said Windows needs KB5044273 or a superseding update
    • The collaborator said installing .NET 8 is irrelevant because PowerToys Settings is self-contained when installed correctly
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 19, 2026

    • A second user on PowerToys 0.102.3101 reports the app only appears as a tray icon and does not open
    • The Application Error event (ID 1000) shows PowerToys.Settings.exe 0.102.3101.0 faulting in KERNELBASE.dll 10.0.19041.2913 with exception code 0x80131506
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 19, 2026

    • Users on PowerToys 0.101 under Windows 10 report double-clicking the tray icon does nothing, with 0x80131506 Application Errors in KERNELBASE.dll
    • Workaround: in Windows Security, Exploit protection, Program settings, add PowerToys.Settings.exe and set Hardware-enforced Stack Protection to Off with Override system settings
    • PowerToys.Settings.exe is usually in %LocalAppData%\PowerToys\WinUI3Apps for per-user installs or under C:\Program Files\PowerToys for machine-wide installs
    • One user confirmed the exploit protection override worked and needed the same override for PowerToys.FancyZonesEditor.exe in %LocalAppData%\PowerToys
    • The original reporter said the same PowerToys install worked on their Windows 11 laptop
  • Microsoft PowerToys (GitHub) · GitHub issue · checked Nov 19, 2026

    • PowerToys 0.99.1 on Windows 10 22H2 fails fast at startup inside coreclr.dll with the assertion !AreShadowStacksEnabled() || UseSpecialUserModeApc()
    • The reporter stopped the crash by disabling user-mode shadow stacks