Notepad breaking in Windows 11 is more common than it should be for an app that’s been around since 1983. Whether it won’t open, disappeared after an update, refuses to save files, or the new tabs feature is acting up — the fixes are different for each problem, and most guides only cover one of them. I’ve run into three of these four issues personally, so this covers all of them in one place.
Why Notepad Breaks on Windows 11
Notepad isn’t the simple built-in tool it used to be. Microsoft rebuilt it as a Store app starting with Windows 11, which means it now has an update cycle, a separate installation state, and dependencies it didn’t used to have. That’s actually the root cause of most Notepad problems — it behaves more like a Store app than a system utility, and it fails like one too.
Specific causes across the four main failure types:
Notepad not opening or crashing — usually a corrupted app package, a failed Store update stuck mid-install, or a conflict with a third-party app that registered itself as the default .txt handler.
Notepad missing after a Windows update — Windows 11 feature updates have a known habit of uninstalling optional components and Store apps during the upgrade process. Notepad gets caught in this occasionally, especially if you’d previously reset or repaired it.
Files not saving correctly — encoding mismatches (UTF-8 vs ANSI), permission issues on the target folder, or the autosave/session restore feature writing to a temp location instead of your actual file path.
Tabs not working — the tabs feature in Notepad requires a specific minimum version. If your Notepad didn’t update properly through the Store, or if you’re on an older Windows 11 build, tabs either don’t appear or open files in separate windows instead of tabs.
And there’s one cause that cuts across all of these that almost nobody mentions: a corrupted Windows identity cache can break Store app authentication, which prevents Notepad from launching or updating at all. It looks like a Notepad problem but it’s actually a broader Store issue.
Fix 1: Notepad Won’t Open or Keeps Crashing
Start with the obvious: try opening Notepad from a fresh Run dialog (Win + R → notepad.exe). If it opens that way but not from the Start menu or a .txt file double-click, the problem is a broken file association or Start menu shortcut, not Notepad itself.
If it crashes on launch regardless of how you open it:
Step 1: Repair the Notepad app package
Go to Settings → Apps → Installed apps → search for “Notepad” → click the three dots → Advanced options → Repair. Wait for it to complete, then try opening Notepad again.
If Repair doesn’t work, come back to the same screen and click Reset. Reset clears all app data and reinstalls the package from scratch. You’ll lose any saved sessions, but that’s usually fine.
Step 2: Reinstall via PowerShell
If the Settings repair fails, the package is likely corrupted beyond what the built-in repair can fix. Open PowerShell as Administrator and run:
powershell
Get-AppxPackage *Microsoft.WindowsNotepad* | Remove-AppxPackageThen reinstall from the Microsoft Store — search “Windows Notepad” and install it. Don’t install third-party “Notepad” apps that appear in the results; you want the one published by Microsoft Corporation.
Step 3: Check the default app association
If Notepad opens fine but won’t launch when you double-click a .txt file, go to Settings → Apps → Default apps → search for .txt → make sure it’s set to Notepad. Sometimes after a Windows update or a third-party text editor install, this gets quietly changed.
So if you’ve reset Notepad and it’s still crashing, check Event Viewer (search for it in Start) → Windows Logs → Application. Filter by “Error” and look for entries with source “Application Error” around the time of the crash. The faulting module name will tell you whether it’s a Notepad DLL or something injecting into the process.
Fix 2: Notepad Is Missing After a Windows 11 Update
This one’s annoying because there’s no error — Notepad just isn’t there anymore. Search returns nothing, the executable is gone, and the Store shows it as “available” rather than installed.
Step 1: Reinstall from the Microsoft Store
Open the Microsoft Store, search “Windows Notepad,” and install it. Takes about 30 seconds. This is the fix for most people.
But — and this trips people up — if the Store shows Notepad as already installed but you can’t find it, the package is in a broken state. Run this in PowerShell as Administrator:
powershell
Get-AppxPackage *Microsoft.WindowsNotepad* -AllUsers | Select Name, PackageFullName, InstallLocationIf the output is empty, it’s genuinely uninstalled. If it returns a result but with no valid InstallLocation, the package is registered but the files are missing — this needs a full remove and reinstall:
powershell
Get-AppxPackage *Microsoft.WindowsNotepad* | Remove-AppxPackageThen install fresh from the Store.
Step 2: Re-register for all users
On some systems — especially ones that were upgraded from Windows 10 rather than clean-installed — Notepad only gets installed for one user account and disappears when you switch profiles. Fix it by running in PowerShell as Administrator:
powershell
Get-AppxPackage -AllUsers *Microsoft.WindowsNotepad* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}This re-registers the existing package for all user accounts without reinstalling.
Fix 3: Notepad Not Saving Files Correctly
This covers a few different symptoms — files saving as the wrong encoding, save dialogs failing silently, or the file appearing to save but changes being lost after closing.
Encoding Problems (UTF-8 vs ANSI)
Windows 11 Notepad defaults to UTF-8 with BOM for new files. This breaks things in specific situations — particularly if you’re editing config files, .htaccess files, batch scripts, or anything that expects plain ANSI or UTF-8 without BOM.
When saving, click the Encoding dropdown in the Save As dialog. For most config and script files, you want “UTF-8” (without BOM) or “ANSI” depending on what the file expects. The default “UTF-8 BOM” adds three invisible characters at the start of the file that some parsers choke on.
That’s not entirely accurate — let me clarify. “ANSI” in Notepad’s save dialog doesn’t mean true ANSI; it means your system’s current code page, which on English Windows is typically Windows-1252. For anything that needs to be genuinely portable, UTF-8 without BOM is the safer pick.
Permission Errors When Saving
If you’re editing a file in a protected location (Program Files, Windows directory, system32) and Notepad silently fails to save — or saves to a different location — it’s a permissions issue. Notepad doesn’t run elevated by default.
Right-click Notepad → Run as administrator, then open the file from within the elevated session. Or better: copy the file to your Desktop, edit it, then move it back.
Autosave Writing to Temp Instead of Your File
Notepad in Windows 11 has a session restore feature that saves open files to a temp location. In rare cases — particularly after a crash or forced close — the temp version and the real file get out of sync, and reopening Notepad shows you the old temp content instead of your last saved version.
Check %LocalAppData%\Packages\Microsoft.WindowsNotepad_8wekyb3d8bbwe\LocalState\ for any .tmp files. These are Notepad’s autosave cache. If your “lost” content is anywhere, it’s here.
Fix 4: Notepad Tabs Not Working
The tabs feature in Windows 11 Notepad was introduced in version 11.2302 and requires Windows 11 22H2 or later. If you don’t see tabs, you’re either on an older Windows build or Notepad hasn’t updated.
Step 1: Check your Notepad version
Open Notepad → click the gear icon (Settings) → scroll down to “About.” If the version is below 11.2302, tabs won’t be there.
Step 2: Force a Store update
Open the Microsoft Store → Library (bottom left) → Get updates. Let it run. If Notepad has a pending update, it’ll install here. After updating, restart Notepad completely.
Step 3: Check your Windows build
Settings → System → About → Windows specifications. If you’re on Windows 11 21H2, you won’t get tabs — that build doesn’t support the feature. You’d need to update to 22H2 or later via Windows Update.
And if Notepad is on the right version but tabs still aren’t appearing: go to Notepad Settings (gear icon) → make sure “Open files in a new tab” is toggled on. It’s off by default in some update paths, which I find mildly baffling.
Advanced: When Nothing Above Works
Reset the Windows Store Cache
A corrupted Store cache can prevent Notepad from installing, updating, or repairing correctly. Run wsreset.exe from Run (Win + R). This clears the Store cache and relaunches the Store automatically. Try the Notepad repair or reinstall after this.
Check Windows Identity Cache
From what I’ve seen, this is the fix for the genuinely stubborn cases — Notepad won’t install, the Store throws vague errors, and everything else looks fine. The Windows identity cache (used for Store app authentication) can get corrupted, particularly after account changes or domain/Azure AD modifications.
Open Credential Manager (search in Start) → Windows Credentials tab → look for any entries starting with MicrosoftAccount or SSO_POP_Device. Remove them, then sign out and back into your Microsoft account. Try the Store reinstall again.
SFC and DISM
If Notepad problems started right after a Windows Update, system file corruption is possible. Run in PowerShell as Administrator:
powershell
sfc /scannowIf that finds and fixes issues, try Notepad again. If SFC itself reports errors it can’t fix:
powershell
DISM /Online /Cleanup-Image /RestoreHealthThis pulls clean system files from Windows Update and takes longer — let it finish before rebooting.
What Actually Worked in Practice
The missing-after-update issue: Store reinstall fixed it every time, but once I had to do the PowerShell remove first because the package was in a zombie state — registered but not actually there. The Get-AppxPackage command to check install location is worth running before assuming it needs a full reinstall.
The crashing issue: I had one machine where Notepad crashed immediately on launch and neither Repair nor Reset did anything. Turned out a Markdown editor I’d installed had injected a shell extension that was loading into Notepad’s process and crashing it. Found it via Event Viewer — the faulting module wasn’t a Notepad DLL at all. Disabling the shell extension in ShellExView fixed it. Wouldn’t have found that without checking the crash logs.
Prevention Tips
- Don’t skip Windows 11 feature updates indefinitely — older builds lose Notepad tab support and sometimes have Store sync issues that cause app packages to go stale
- If you install alternative text editors (Notepad++, VS Code, etc.), check your
.txtdefault app association afterward — installers sometimes claim the association without asking - After any major Windows Update, open Notepad once just to confirm it’s still there and functioning before you need it for something important
- Keep an eye on the Store’s Library tab for pending Notepad updates — the app doesn’t always update silently the way it should
FAQ
Notepad opens but immediately closes. What’s wrong?
Check Event Viewer → Application log for crash entries. If the faulting module isn’t a Notepad file, a third-party shell extension is likely injecting and crashing the process. ShellExView can identify and disable it.
Can I get Notepad back without the Microsoft Store?
Yes. The PowerShell command Add-AppxPackage can sideload the Notepad package if you have the .msixbundle file. But honestly just using the Store is faster and less error-prone unless your Store is also broken.
My Notepad doesn’t have a gear icon or settings menu. Why?
You’re on a very old version. The settings UI was added in later builds. Update via the Store first.
Files I edit in Notepad keep reverting after I close it. What’s happening?
Session restore is loading an autosave instead of your actual file. Check %LocalAppData%\Packages\Microsoft.WindowsNotepad_8wekyb3d8bbwe\LocalState\ and clear the cache files there, then reopen your file directly.
Notepad tabs work for some files but not others. Why?
Files opened via command line arguments or certain shell context menus sometimes bypass the tab behavior. Try opening files from within Notepad (File → Open) and see if tabs work consistently that way.
Will reinstalling Notepad delete my unsaved files?
The Reset option in Advanced options clears app data including autosave sessions. If you have unsaved content in open Notepad windows, save them first. A fresh reinstall via the Store shouldn’t touch your actual saved files on disk.
Is Notepad in Windows 11 the same as the old one?
No. It’s been rebuilt as a Store app with tabs, session restore, dark mode support, and a settings menu. The core editing experience is the same but the underlying architecture is completely different, which is why it can break in ways the old Notepad never could.
Editor’s Opinion
honestly the fact that notepad can just disappear after a windows update is kind of embarrassing for an OS built-in. but the store reinstall is fast and the powershell remove-then-reinstall fixes the stubborn cases. the encoding thing trips up more people than you’d think — especially anyone editing web config files and wondering why their server is throwing errors. check the encoding dropdown before assuming the file is broken. and if notepad is crashing, event viewer first — don’t spend an hour reinstalling things when a shell extension is the actual problem.
