1903: Notepad freezes

tcebob · 08 Jun 2019

Just upgraded to 1903. Tried to run Notepad from shortcut and then from .exe in Windows. Freezes and calls home when I try to close it. Other editors (Text Pad, Sciteforautohotkey, Notepad++) work OK. Worked fine in 1809. Help!

- Later: can open an existing .txt file with Notepad using "Open with" in context menu. So might work around by constructing a shortcut to an almost empty file. But . . .

pps: tried ms store: Notepad For Windows 10. What a piece of . . .

pepanee · 08 Jun 2019

You cant try: How to reset Notepad to default settings on Windows 10

tcebob · 09 Jun 2019

Didn't work. Same response.

Found old Notepad.exe in Windows.old and it works. As long as I start it in Windows.old. Copying to a different directory or making a shortcut doesn't work; it refuses to run at all. Need a copyable version.

dalchina · 12 Aug 2019

Hi, I'm experiencing the same on two PCs recently upgraded to 1903.
Notepad hanging on launch, using a fair bit of CPU time.

A quick search only found a very few similar problems reported.

I think I'll simply substitute for it.

Bree · 12 Aug 2019

Odd, I've not had a problem with Notepad on any of my 1903 machines.

Maybe it's a problem with a corrupt item in its recent files lists? You could try clearing you 'recent files'...

Reset and Clear Recent Items and Frequent Places in Windows 10

dalchina · 12 Aug 2019

Reasonable guess- unfortunately no effect. As per initial post, Notepad is fine opened via 'Open With'. Problem is only if launched directly (double click exe or via shortcut).

thomaseg1 · 12 Aug 2019

You might try cleaning the temp files as well as what Bree suggests.
If all else fails may be re registering Notepad. exe
Registering DLLs and EXEs Manually | Razorleaf

dalchina · 12 Aug 2019

Having examing the tree related to Notepad in Process Explorer, the two non-MS items were Avast (not that) and Actual Window Manager (which adds buttons to the title bar).

Disabling the latter seems to resolve the problem with Notepad.

Odd because there's no evidence of a problem with any other window or dialogue.