Can't set notepad++ as default program in Windows 10???
I used to be able to right click->open with->more apps->look for another app on this pc->find notepad++ in correct directory.
I noticed that this stopped working recently when I changed computers and had to reinstall everything. Was this another convoluted update for Windows 10?
andrecool-68 last edited by
For myself, I add a right click using the bat file:
Prahlad-Makwana4145 last edited by
Please follow this step ,To set notepad++ as default program in Windows 10
step 1 :- Run Notepad++ as administrator.
step 2 :- Go to Settings > Preferences > File Association.
step 3 :- Select Notepad “.txt” in Supported extensions panel.
step 4 :- Click the "-> " to move it to Registered extensions panel.
step 5 :- Close and try to reassociate.
I hope this information will be usefull for you.
@Prahlad-Makwana4145 thanks, but this doesn’t work for me. When I click Choose a Default, the only programs that shows up are Notepad and Wordpad, along with option to look for an app in the MS store.
There is a Notepad++ in the app store, but it is not the official version.
Seems almost like MS isn’t recognizing it as a possible default app, even though it’s clearly installed and visible under Apps&Features.
PeterJones last edited by
If you have a 64-bit Notepad++ installed in
C:\Program Files\Notepad++, search your registry for
C:\Program Files (x86)\Notepad++and replace any such instance with
C:\Program Files\Notepad++– it may be that something wrote the wrong value into the registry (maybe a previous 32-bit installation), and so Windows 10 looks for a nonexistent location, cannot find it, and then refuses to associate an OpenWith action for Notepad++.
(I’d do a full search of the registry, but I think it’s something like
HKLM\Software\Classes\Applications\Notepad++.exe, both of which might map to
HKCR\Applications\Notepad++.exe. From what I remember, each extension gets an OpenWithList which includes notepad++.exe, and then the registry looks in Applications\Notepad++.exe to find out the actual path to that command; so if that key points to a non-existent executable, Windows ignores that OpenWith option. And I have a memory that something occasionally goes wrong and leaves the x86 version in the registry, even after the 64-bit is installed.)
@PeterJones thanks, this sounded so promising, but alas, doesn’t seem to be the problem.
I even uninstalled (revounistaller) and reinstalled, no change. Also tried the 32 bit version, same problem.
Now I’m really scratching my head because it sounds like it’s just my system, not some crummy Windows change :-(