Shortly after associating Notepad++ with .txt files, I noticed that the Text Document option had disappeared from the Windows Explorer menu. Using regedit, I took a look in the Windows registry:
HKEY_CLASSES_ROOT\.txt
The first thing I noticed was that the registry key was actually .TXT instead of .txt. Not only that, but the contents of the registry were not at all what they were supposed to be:
- Default was set to Notepad++_file
- Notepad++_backup was set to textfile
- ShellNew was set to Nullfile
This key obviously belongs to Notepad++ or one of it's plugins. However it is completely unnecessary to associate Notepad++ with the creation of text files in Windows Explorer's New context menu. Fortunately there is a very easy and quick fix.
IMPORTANT: Always have recent a backup before making any changes to the Windows registry. A mistake can result in Windows failing to work correctly or even starting up again.
In my case, right-clicking on the .TXT key, renaming it to .TXT2 and pressing F5 immediately revealed the original .txt key.
If it doesn't for you, you can re-create it by copying and pasting the following as text file into Notepad or Notepad++ and saving it as fix-new-text-document.reg. Last, double click on the file to import it into the registry. Windows will likely ask you to confirm that you really want to do it.
Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.txt] "PerceivedType"="text" @="txtfile" "Content Type"="text/plain"
October 16, 2014 at 11:18 AM
Had same exact problem…
I fixed it by simply changing the default from “Notepad++_file” to “txtfile” with regedit.
November 13, 2018 at 2:04 PM
Thanks a lot. It worked for me, too.
OS = Windows 10
November 25, 2018 at 2:09 PM
You are very welcome Tom! Glad it helped you out 🙂
December 3, 2018 at 1:48 PM
I had same exact problem and using REGEDIT to change the default from “Notepad++_file” to “txtfile” fixed it!
April 3, 2019 at 2:30 PM
I had the same issue, but in my case default handler was set to CuteFTP, still shaking my head about this. Creating the fix-new-text-document.reg with the code above and executing it fixed it right away.
Thanks for this awesome help!!!
May 28, 2022 at 3:50 PM
Thank you so much! It worked like a charm!