i am awre about the back up process but
The FAQ explains more than the backup process. It also explains where the backups are kept, and it mentions what to do in the “Scenario: My (unsaved) files are missing!” section.
why again and again file getting lost from notepad++
Because you don’t have AutoSave plugin, or you don’t have the plugin set up right, or you are relying on “periodic backup and session snapshot” to do something it wasn’t intended to do.
while all suggested checks already done as per suggestion ,
And who but you knows what settings you actually have? If you don’t tell us, we cannot read your mind. Give us a screenshot of that preferences screen, for example.
because sometimes backed up files also not updated very much as comparision to original file
Then you haven’t read or understood the FAQ, because it explains exactly when the “backups” of different types happen. The “unsaved” backups happen every 7 seconds (or whatever you have the setting at); and as soon as you save the file, that “unsaved backup” is deleted. If you have backup-on-save turned on, then every time you save, it creates a new .bak file.)
I think notepad++ team have to work on this to resolved such frquent issue for better uptime .
It’s not frequent. It rarely happens to anyone. And the Notepad++ team has put hours and hours and hours and hours and revisions and revisions and revisions in eliminating many of the infinitude of reasons why the OS confuses Notepad++ and gets around all its backup code.
Right now, unexpected OS reboots (crashes; update restarts) are the only time that it seems to still be losing the data. If you have data to the contrary, then describe the exact sequence of events that leads to the data loss.
As explained in the user manual: Starting in v8.1.9.3, if you have the file nppLogNulContentCorruptionIssue.xml in the same directory as notepad++.exe (the installer should have put it there for you the last time you installed/updated), then if there really is a crash, it will create %AppData%\Notepad++\nppLogNulContentCorruptionIssue.log, which you can submit in an official bug report.