NotePad++ 8.1.2 - Windows 10 x64 21H1.1151 - Save Dialog - Unable to enter filename



  • Hello,

    I’m currently having a problem in the save dialog box if I change my directory:

    • I am in “xx\name-contests\lib”.
    • I create a new tab via CTRL + N.
    • I’m typing in my initial code.
    • I open the dialog via CTRL + S.
    • I click in the address bar to go back to “xx\name-contests”, then “xx\name-contests\database”
    • I want to enter the file name: impossible.
    • I want to click on the save button taking the proposed name, to rename it afterwards: impossible.

    On the other hand, after reloading notepad ++, I can correctly save my tab.

    I will continue my investigation.



  • A little more precision on the case encountered:

    • when I say I’m in “xx\name-contests\lib”, I mean I have a file open in that directory, for example, “xx\name-contests\lib\index.js”.
    • I redid the tests by neutralizing all the addons.
    • In my case, I have a redirection of the download directory, which would give the full path:
      “E:\Download\Download.Store” for this directory.
      “E:\Download\Download.Store\name-contests\lib” for the example in absolute addressing.
    • The problem could be that the address displayed in the address bar is not in absolute addressing but takes into account the redirection
      “> This PC> Download> name-contests \ lib”


  • @alphacentauris44 ,

    Something similar has been seen on vista and win7, as discussed recently – it doesn’t happen to everyone, but it can happen. My guess is that it’s affecting you on your Win10 as well . There is a fix that has been proven on older systems; you might want to try the most recent build (described in my linked post) and see if it also fixes it for you.



  • I got the same issue.
    I’m on Windows 10 pro 20H2. Notepad++ 8.1.2



  • @James-Rosemary said in NotePad++ 8.1.2 - Windows 10 x64 21H1.1151 - Save Dialog - Unable to enter filename:

    I got the same issue.
    I’m on Windows 10 pro 20H2. Notepad++ 8.1.2

    Since @alphacentauris44 didn’t reply to my advice, did you see that advice that I gave to @alphacentauris44 ? If you did, did you try the advice? – That is, did follow the link to the other recent discussion and follow the instructions there? Those instructions tell you how to try out the latest unreleased build of Notepad++ (aka the “development version”). If the development version fixes the problem, then great, let us know, and you can use that version until the next release of Notepad++ which will include the fix. If the development version doesn’t fix it for you, then let us know soon, and we can direct you to where to post so that one of the developers can see that the development version fixed the problem for vista and win7, but not for win10.

    But until either @alphacentauris44 or @James-Rosemary (or some other future poster) replies with whether or not they tried the development version, and whether or not it fixed it for them, the developers will assume that the problem is fixed in the development version.



  • Same issue from version 8.1. To reproduce the error:

    1. Open the save window
    2. Change the save folder


  • @Gian-Carlo-C said in NotePad++ 8.1.2 - Windows 10 x64 21H1.1151 - Save Dialog - Unable to enter filename:

    Same issue from version 8.1. To reproduce the error:

    1. Open the save window
    2. Change the save folder

    That doesn’t reproduce the error for everyone. As I have posted multiple times – with video proving it – changing the folder in the Save dialog works perfectly for me on Windows 10, with NPP v8, v8.1, v8.1.1, and v8.1.2. It is only certain unique situations that trigger this bug apparently.



  • To everyone replying to this topic

    Just saying “it happens to me, too” doesn’t help. The bare minimum useful response would be to show your ?-menu’s Debug Info.

    We know about the problem; the developers know about the problem. There is a fix that should be in the next version that has been confirmed on Vista and Win7; but no one who has seen the problem on Win 10 has been willing to go through the steps of proving that the fixed version will work. It’s really simple to do. The best way you can help is by following the instructions linked above, and letting us know whether the fixed “development version” actually fixes it for you on your version and configuration of Windows.


Log in to reply