Hi Nova,
I'm on 26220.7070 and Notepad opens fine from
Run or the Start menu.
Have you tried Repair, Reset etc. from Settings?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
When I press Win + R, type notepad, and hit Enter, I get this error message:
The code execution cannot proceed because Microsoft.UI.Windowing.Core.dll was not found. Reinstalling the program may fix this problem.
However:
Running C:\Windows\notepad.exe directly works perfectly.
Opening Notepad from the Start menu also works fine.
The problem only happens when launching Notepad via Win + R (or the notepad command).
This makes me think the modern UWP version of Notepad (WinUI 3) is missing a dependency or has a broken link to the Windows App SDK, while the legacy executable still works.
Steps I have tried:
Reinstalled Notepad using:
dism /online /add-capability /capabilityname:Microsoft.Windows.Notepad~~~~0.0.1.0
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
None of these solved the issue.
Could you please confirm if this is a known issue in the Dev Channel build 26220.7052, or provide guidance on how to reinstall or restore the missing Microsoft.UI.Windowing.Core.dll / Windows App SDK runtime?
System Info:
Edition: Windows 11 Insider Preview 25H2 (Build 26220.7052)
Channel: Dev
Architecture: x64
Notepad version: UWP (Microsoft Store)
Thanks a lot for your help!
Hi Nova,
I'm on 26220.7070 and Notepad opens fine from
Run or the Start menu.
Have you tried Repair, Reset etc. from Settings?
AI answer
It appears that you are encountering an issue with launching the UWP version of Notepad via the Win + R command in Windows 11 Insider Dev Channel (Version 25H2, Build 26220.7052). The error message regarding the missing Microsoft.UI.Windowing.Core.dll suggests that there may be a dependency issue with the modern version of Notepad, which is likely linked to the Windows App SDK.
Since you have already tried reinstalling Notepad and running system checks like sfc /scannow and DISM, here are a few additional steps you could consider:
As this is a known issue in the Dev Channel, it may be resolved in subsequent updates, so keeping your system updated is crucial.
References: