attempt to recover files after NPP blank 2 files after error(missed the error msg)

kingtls

I am trying to recover two text files which were somehow became blank (zero byte) after notepad++ caused an error.

Briefly,

I receive error message from NPP and notice one of my file was blank (have multiple tabs/files opened), tried Undo multiple times but the file still blank. I notice another file/tab also blank, Undo did nothing to make any text to re-appear. Sadly as I was in the meeting at the time, I did not read the error message.
I re-open the first file (I did not save it) but it was also blank. Upon checking with File Explorer, noticed that the file is of zero byte size. Similarly with the 2nd file.
I then checked then Preferences settings:
```
  - checked Enable session snapshot (backup every 7 seconds)
  - Backup path C:\Users\xxx\AppData\Roaming\Notepad++\backup\									
```
and check the Backup folder. Only a single but different file exist in the folder, and is dated more than 2 months ago.
I browse the Temp directory, could not find any meaningful file similar to the two files above. I opened all the last two weeks temp files but found nothing.
Environment is Notepad++ v7.5.1 64-bit, Windows 7 SP1, SSD is encrypted by McAfee

I see two problems i.e.
1. NPP’s backup mechanism failed as I didn’t find any recent backup files
2. What is that error message and why 2 files were blanked by NPP and not other files (at least 8 others)?

Is there any other way to recover these two files?

chcg

At least you are not the only one:
https://notepad-plus-plus.org/community/topic/15106/all-code-disappears-after-npp-becomes-not-responding-win7-32-bit
https://notepad-plus-plus.org/community/topic/14945/rare-null-write-glitch

, could also happen if your disk is full.

Scott Sumner

@chcg

Well, if we are making a list so the OP has “companionship”…

:-D
…but it’s not funny. It attacks the core basis of any text-editor: Data safety/integrity is Job #1…within realistic limits.

kingtls

oh no … i should have checked before I reluctantly accept to use this editor (that attitude of we are corporate we know better)!!!

thanks for the links, chcg and Scott…I shall see if there are of any help.

my problem is that npp stays working as though there is nothing happen(indeed I continue to work with other files), that gives you a sense that that error message I missed may not be that critical after all!!!

Claudia Frank

@kingtls

the default backup settings, creates a backup of a currently changed file or a never
saved file only.
What means, as soon as you open a new file and start typing a backup file will be created,
the same is true if you open an existing file and modify it.
As soon as you save the file and this is action is reported being successful npp will delete the
backup file. If you want to have a backup on saved files as well, you need to change the settings
under backup section.

Your case is different than the other because npp kept running so I assume the error message
would be really helpful to see what happened and I assume that you got a message pointing
to a file change and if you want to reload the file, something like that.

As the file has been overwritten already I don’t see how this could be recovered other then
having a backed up version. As you say you are working in company it might be that your
windows setting is set to make backups of your file like when right-click on a file you should
see a tab where it is possible to reload a previous version of that file.

Cheers
Claudia

chcg

@kingtls I’m using n++ heavily now for over 10 years and never observed that behaviour on my own. So it seems to be a rare case and not easy to track. There are also multiple root causes in a widespreaded environment (WinXP-WIn10, Wine, 32bit/64bit, different plugin installations, etc.):

some of the issues happen due to power fails, which might need a transaction save file system to avoid
editing data on a network drive with corruption due to network errors
coredumps either by n++ itself or some plugin

And at least the reproducible issues I think get fixed.