Notepad++ v6.9.2 released
-
as of version 6.9.2 npp is only available as a 32bit version.
New npp 7 offers a 64bit version.With npp <7, if one tries to edit a file in system32 and this file
has a copy in SysWOW64 it get’s redirected as MS thinks
this is the file which should be edited instead of the one you
might have chosen.So the edited file isn’t the one expected which could lead to the issue you’ve reported.
There are workarounds like sysnative alias or links available but because npp offers
a 64bit version I would go this way. Unfortunately the new version hasn’t all plugins
available yet but I assume this will change over time.Cheers
Claudia -
Thanks for the explanation. So the solution, in your opinion, is to wait for version 7 and then get the 64bit version of it?
-
@Gilad-Denneboom, From a 32bit app in a 64bit Windows OS (Vista or above), you can access the actual 64bit System32 file (
%windir%\System32\filename) using the alias%windir%\Sysnative\filename: see File System Redirector at MSDN. (FYI: TheSysnativealias only works from a 32bit app; a 64bit app cannot see that alias.) -
So the solution, in your opinion, is to wait for version 7 and then get the 64bit version of it?
I don’t know because you didn’t state if this is your issue.
And if it is, you don’t have to wait as the rc version is already out.
I use it already, in the way I use npp - no extensive tests, and didn’t came across any problems yet
and, as already stated, there are workarounds for earlier versions like sysnative alias and links.Cheers
Claudia -
PS. This is a very serious issue, I think (work being lost without notification or a way of restoring it). Maybe it’s a good idea to make a note of it on the download page, so that others don’t have the same issues I did… Or even withdraw this version altogether until a solution can be found for it.
-
(work being lost without notification or a way of restoring it)
?? - maybe you wanna reread my explanation of this.
Cheers
Claudia -
Sorry, but your explanation was not very clear. I’m a fairly technical person but I really don’t feel like having to mess around with all of these settings just to get the application working correctly, as it did until recently. I think I’ll just stick with the older version until a more reliable one comes out. Thanks for your time, though.
PS. My OS is Windows 7. There is no %windir%\Sysnative\ folder on it.
-
My OS is Windows 7. There is no %windir%\Sysnative\ folder on it
Because it is an alias, not a folder.
Open the file dialog of npp and put it %windir%\Sysnative, press enter
and you will see the files and folders.Sorry, but your explanation was not very clear
I’m always eager to improve my English, so you are welcome
to let me know what I’ve done wrong.Cheers
Claudia -
@Claudia-Frank said:
Because it is an alias, not a folder.
Open the file dialog of npp and put it %windir%\Sysnative, press enter
and you will see the files and folders.What do you mean by “the file dialog of npp”? Do you mean the npp executable? The entire application folder? Some dialog from within the application itself? Please be a bit more specific.
-
- The file dialog is reached in Notepad++ by clicking on the
Filemenu, then theOpenmenu item - In either the top folder bar, or the File Name box, type
%windir%\Sysnative
(the image shows the typing in both; it’s only needed in one or the other) - Select your file in the usual manner
- Hit
Open
- The file dialog is reached in Notepad++ by clicking on the
-
@PeterCJ-AtWork
That does not work for me. And I’ve already downgraded to 6.9 and am still getting the same behaivour. This is getting really troubling…
What version can I downgrade to where this issue is not present? -
I completely erased NP++ and then re-installed 6.9 (before I just installed it over 6.9.2 and the problem persisted). Hoping for the best…
If the issue still happens I will have to stop using NPP, which is a real shame since I love it, have used it for years on a daily basis, and have donated multiple times to the developers for their hard work on it. -
do you really think, that one can give you precise answer about your problem
but you don’t give detailed informations what you are doing?
We still have to assume that the file system redirector is the problem you encountered.
This might be true, … maybe it isn’t.
I don’t go into detail about what to do, as the links provided, give a good description what happens and
how to workaround and because you stated that you are “fairly technical person” I don’t want to annoy you.But you should reconsider your information strategy - there might be cloudy days and this could affect our crystal balls.
Cheers
Claudia -
@Claudia-Frank
I’ve provided all the information I have available to me that I thought was relevant. What else are you missing? I’m happy to answer any questions.
I tried the suggestions given above (ie, open the file after accessing the Sysnative alias folder), the results were the same. -
@Gilad Denneboom, I cannot help you on this specific problem but I can help on general debugging techniques. I see posts from Claudia and Peter who are trying hard to help you. From the information you are giving they are, I believe, having difficulty understanding the problem and are unable to reproduce the issue.
When they ask a question or request information it is in your interests to supply as much detail as you can to explain how and when the problem occurs and how you can reproduce it so that they can try and reproduce it. Often when I reply to people (on other forums) who ask for help I ask them several questions. Providing my reasons for each question would be time consuming. Generally my question are intended to rule out or to rule in various theories I have about where the problem might be.
I have written this post because you wrote “that I thought was relevant” in your last answer. Claudia and Peter are experts on Notepad++, they ask questions and ask for information that they think relevant. One thing I do not see in your message is a clear list of actions to reproduce the fault you observe with Notepad++. Two days ago Claudia wrote “you don’t give detailed informations what you are doing”.
-
@Gilad-Danneboom,
Please note that “that does not work for me” does not provide much information to the people who are trying to help you debug your issue. The fact that it does the same thing when you downgrade from 6.9.2 to 6.9 shows that it’s not just a specific version of the software – and hints that it might not be on Notepad++ end at all. My default, when asking for help, is to be as verbose and detailed as possible; sometimes there is extraneous information included, but that’s better than not including enough. There have been many people (easily hundreds, probably thousands) using NPP 6.9.2 with the majority of files being properly saved.
Those that weren’t saved, in my experience (and as Claudia and I have said, previously) were because it was an issue with the way that Windows handles 32bit apps trying to access certain directories that are 64bit-specific. Thus, our debug attempts were pointed in that direction. But there’s another two circumstances I thought of that have similar behavior: 1) trying to edit a Notepad++ configuration file: those files will be overwritten when NPP exits, so your changes will be overwritten. 2) If the file is open in another process (Word, Excel, web browser, etc), or can be written to by some background process (a .log file, a database application, etc), maybe the file is being overwritten by something else after you’ve saved the changes.
But now I will admit, I failed you in my first debug attempts: I made the assumption that since your brief problem description sounded like (gave the same symptoms as) the filesystem redirector, I thus assumed you were trying to edit a file somewhere in
%windir%\System32(or a subdirectory thereof; note that %windir% is the variable-notation for the main windows directory; on windows 7, it’s oftenc:\windows, but not always; thus,%windir%\system32will bec:\windows\system32), and only went in that direction in my responses. But I now see that no one has clarified the file’s location, so this could be wrong.The following are the series of steps I would take if the problem were happening to me. If you share the results of the steps (more than just “it doesn’t work”), you might be able to find the problem, or we might be able to help you find the problem. My two major sections of debug that I will describe below “what version of stuff am I using and what exactly am I looking at?”, and “making the same assumptions that PeterCJ was using, why would
%windir%\sysnativenot be working for me?”: the second group only applies if the file really is in the%windir%hierarchy.What Version of Stuff Are You Using? and What Exactly Are You Looking At?
- Does it do it with all files, or just some? What’s the same (or different) about the files that work vs the files that don’t?
- What is the exact sequence of events that you use to edit, save, and discover that it’s not saved?
- How do you load the file in Notepad++?
- How do you save the file?
- How do you confirm that the file actually saved?
- Do you close Notepad++ at this point, or just close the file from Notepad++, but leave the application running?
- What are the results of the following: From notepad, Notepad++ choose
?MENU >Debug Info>Copy debug info into clipboard(paste it in your response, indenting by 4 characters to make it a block of preformatted text) - Have you verified 64bit OS?:
START MENU> RightClick onComputer>Properties: what does theSystemsection say theSystem Typeis? - What is your
%windir%: Open a command window (START MENU>cmd.exeorWINKEY+Rthencmd.exe), and typeecho %windir%, what gets printed? - What is the full path of the file you are trying to edit that fails?
- If it’s in the
%windir%hierarchy, it’s probably because of the filesystem redirector - If it’s a Notepad++ configuration file, NPP will overwrite the file when it closes
- If it’s in the
If you do not have a 64 bit OS, stop here, as we will have to process the new information before further debug is possible.
If your file is outside of the
%windir%(c:\widowsor equivalent), stop here.
%windir%\SysnativedebugSince you’ve continued this far, you are confident you are on a 64bit OS and that the file is somewhere in the %windir% hierarchy. Thus, we need to determine why the
sysnativealias does not appear to work for you.- Open a 64bit cmd.exe:
WIN+R>%windir%\system32\cmd.exe- note, when I do this, it opened in
c:\windows\system32 echo %PROCESSOR_ARCHITECTURE%=> should give AMD64 or similarecho %PROCESSOR_ARCHITEW6432%=> should be undefined, so it will just print%PROCESSOR_ARCHITEW6432%dir %windir%\system32\cmd.exe %windir%\syswow64\cmd.exe=> these should give different filesizesdir %windir%\sysnative\cmd.exe=> should tell you it doesn’t existecho DEBUG64 >> %windir%\system32\DEBUG64.txtecho DEBUGWOW >> %windir%\syswow64\DEBUGWOW.txt- remember to copy/paste your results into your response
- close the 64bit cmd.exe window
- note, when I do this, it opened in
- Open a 32bit cmd.exe:
WIN+R>%windir%\syswow64\cmd.exe- note, when I do this, it opened in
c:\windows\syswow64 echo %PROCESSOR_ARCHITECTURE%=> should give x86 or similarecho %PROCESSOR_ARCHITEW6432%=> should give AMD64 or similardir %windir%\system32\cmd.exe %windir%\syswow64\cmd.exe=> these should give the same filesizes (which match the syswow64 version from 1.4, above):%windir%\system32\gets magically redirecteddir %windir%\sysnative\cmd.exe=> this should give a different filesize than 2.4; it should be the same as the system32 version from 1.4, above.- if this one says “No such file or directory”, then there is something wrong with your computer’s sysnative alias
- if it reports the expected value, we can continue
echo DEBUG64_WILL_GO_INTO_WOW_DIR >> %windir%\system32\DEBUG64.txtecho DEBUGWOW_FROM_32BIT >> %windir%\syswow64\DEBUGWOW.txtecho DEBUGNATIVE_FROM_32BIT >> %windir%\sysnative\DEBUGNATIVE.txtcd %windir%\sysnativedir DEBUG*.txt=> should find DEBUG64.txt and DEBUGNATIVE.txttype DEBUG64.txt=> “DEBUG64”type DEBUGNATIVE.txt=> “DEBUGNATIVE_FROM_32BIT”
cd %windir%\syswow64
*dir DEBUG*.txt=> should find DEBUG64.txt and DEBUGWOW.txt
*type DEBUG64.txt=> “DEBUG64_WILL_GO_INTO_WOW_DIR”
*type DEBUGWOW.txt=> “DEBUGWOW\nDEBUGWOW_FROM_32BIT”cd %windir%\system32=> trying to cd into main, but really will be syswow64
*dir DEBUG*.txt=> you might expect this to be the system32 contents (similar to sysnative above), but it will actually be the same results as syswow64.
*type DEBUG64.txt=> “DEBUG64_WILL_GO_INTO_WOW_DIR”
*type DEBUGWOW.txt=> “DEBUGWOW\nDEBUGWOW_FROM_32BIT”- remember to copy/paste everything into your response
- close this 32bit cmd.exe window
- note, when I do this, it opened in
- Open Notepad++ 6.9.2
- File > Open
- type in the File Name box:
%windir%\syswow64\DEBUG* - you should be able to see the same files as listed in 2.10, above: DEBUG64.txt and DEBUGWOW.txt
- use CTRL+CLICK on the two files to open both simultaneously.
- The contents should match 2.10
- type in the File Name box:
- File > Open
- type in the File Name box:
%windir%\system32\DEBUG* - results should be the same as 2.10, 2.11, and 3.1 above.
- type in the File Name box:
- File > Open
- type in the File Name box:
%windir%\sysnative\DEBUG* - available files should match 2.9, above: DEBUG64.txt and DEBUGNATIVE.txt
- CTRL+CLICK to open both files
- the contents should match 2.9.
- type in the File Name box:
- File > Open
As one possible solution, as has already been pointed out, you could just download the 64bit Notepad++ 7.0 candidate (see the thread NPP 7 Release Candidate for the download locations).
-
@AdrianHHH
I appreciate the need for exact details in order to solve a problem. I’m usually on the other end of the “negotiations”, trying to get relevant information from users with problems. As I said, I’m happy to answer any specific questions asked regarding the problem, but I was not asked any such questions until Peter’s latest reply…@PeterCJ-AtWork
Thank you for the detailed reply and instructions.
When I first re-installed 6.9.0 it was over the 6.9.2 version I had and then the problem persisted. Since then I uninstalled NPP, manually removed its folder from Program Files with all the left-over files that were there, and then re-installed it (6.9.0). The problem has not re-occurred since then (knock wood). So I don’t know if answering all of your questions has any point now, since the problem seems to be gone.
Just to clarify:- The files I was opening where this problem happened were not located under C:\Windows, they were also not NPP configuration files, but files created by me, located under my own folders on the C drive.
- I was opening them via the File menu of NPP, and maybe also by double-clicking them in my file manager application, can’t be sure exactly.
- I was saving the files using Ctrl+S in NPP.
- I confirmed they were saved because their title changed from red to black and I was not prompted to save them when I closed them.
- I noticed this happening while NPP was still running. It might have also happened between sessions when I re-opened a file after closing NPP down (along with the entire computer), but can’t be sure of that, either. As I wrote, this did not happen all the time, so it was very difficult to keep track of the exact circumstances when it did.
- System type is 64-bit (Windows 7 Home Premium)
- %windir% is C:\windows
Thanks for your support so far, Gilad.
-
Hi all,
I didn’t follow this topic, But I noticed something strange, in the last Gilad’s reply !
Gilad said, in his previous post :
I confirmed they were saved because their title changed from red to black
AFAIK, when the file status is “saved”, the colour should be blue, shouldn’t it ?
Best regards,
guy038
-
@guy038
Sorry, I meant blue… Didn’t double-check it, it was from memory. -
I am glad that the problem hasn’t re-occured since the fresh re-install. But that clue could give insight into the cause: it may be that some specific configuration setting or plugin was different in your 6.9.2; when you downgraded overtop of the old installation, that setting or plugin remained, but when you deleted and reinstalled, you removed that setting.
You probably don’t want to spend more time on it, but this is what I would suggest if you ever need to debug the problem again, instead of just hoping 6.9.0 will continue to work for you. I’d grab the
?>Debug Infofrom this working setup, move all of the Notepad++ 6.9.0 directory to a backup location; install 6.9.2, and see if it starts happening again. If it does happen, I would look at the 6.9.2?>Debug Infoand the config files and plugins, and try to determine what’s different. If just a simple compare didn’t give enough insight to finish the debug, I’d archive 6.9.2 to a backup location as well, do another clean 6.9.0 install, and start copying things, one at a time, from 6.9.2-backup to the “test” installation.Other debug ideas I had: use the Notepad++
File>Open Containing Folder>Explorerto open an Explorer window in the folder it’s actually editing from; then, after hitting save, watch the file’s timestamp and size change (and maybe even record it somewhere). Then, the next time you open the file and it’s not the most recent edit you saved, you can open the local Explorer again, and see if it perhaps regressed backward in time, or if it was somehow edited again after you’d saved the last time.But, like I said, either are probably more than you want to do while it’s working. I’m glad it’s working, and hope it continues for you.
