Recovering a corrupted .txt file

I would like to recover a corrupted Notepad (actually, Notepad2, but I guess its's the same) file: I previously saved it, then edited, and with the unsaved edits, a power outage made it unreadable. The file is full of [NUL].

I tried CHKDSK. It has found no errors.

I tried this as well: https://superuser.com/questions/2236...upted-txt-file
Here, the 2nd answer with the Recuva method. Now, previosly I had a very similar instance, when this one worked very well, now not so.

What other hope do I have?

I'm sorry, I'm honestly not sure if I posted this to the right forum. (Where else?)

If it is a small file, try using a HEX editor. You will be able to see the available text then create a new text file in Notepad.

Other option is to learn the structure of text files and rebuild the corrupt file in the HEX editor but that takes some work.

Regards,
GEWB

@GEWB

All the HEX editor editor sees of my file is, zeros. Lots of zeros. That's it.

@RolandJS

Actually, my text file contains, (contained?) sensitive information, I cannot send it to you. I tried to replicate it, like writing full a text file, saved it, writing some more, then without save, unplugged the computer, to no avail; I did not managed to replicate it, with non-sensitive text so far. ;(

RolandJS said:

Is the file now in a safe place, where it cannot be accidentally deleted

Yes, sure, I made copies of the file.

RolandJS said:

Meaning, you have already tried to find and recover earlier and later versions of this textfile, correct?

Yes. All I found was, Recuva converted all the NULs into something different.

The alternative file starts with:

Code:

SQLite format 3

Besides NUL, it contains also EOT, SOH, ETX, ENQ (maybe etc.)

And extended ASCII characters like:

Code:

ÐGOR‹Š

RolandJS said:

Download and install both editplus [free version] and metapad, we might need their reading and editing powers.

What's the methodology with these two editors? What are my hopes?

Thanks for both of your help!

Text files contain no redundancy or defined format. That means any recovery of a corrupted file is going to be problematic at best. A hex editor is just a tool that allows you to examine and edit the file in it's raw form, including portions that are corrupt. A standard text editor would likely remove most of the file. But a hex editor is just a tool and requires human judgement and knowledge of the file to make it work. Likely you could do little more than remove corrupted portions of the file. What's left may or may not be useful.

Edit: If the corruption is the result of the file being completely overwritten with junk or unrelated material then there is no possibility of recovery.

xcr said:

@GEWB

All the HEX editor editor sees of my file is, zeros. Lots of zeros. That's it.

@RolandJS

Not a good sign.

Did you view it all the way to the end file marker?

Regards,
GEWB

There a this prog
PDF, DOC, DOCX, DAT, BIN, PHP Viewer - FreeFileViewer

There is a possibilities the text file still exist somewhere.

Go to Windows\Users\your_username\AppData\Local\Temp

The folder AppData is hidden.
You can change the "your_username" to your account name
Then highlight from "Windows\.......\Temp"
Open your explorer, select the C: drive and paste it on top

This is the Temp files for all types of files that was saved (depend on setting) while you are working even when sudden system cut-off.
You can arrange by Date/Time of the files.
Check the latest, and ignore with or without .txt &or funny chars.

Everyone,

On your recommendation I tried common HEX editor, Metapad, EditPlus, and even FreeFileViewer (Though the latter installed clickware on my machine, for what it's worth, even though I was as careful as possible).

Basically, with all editors, the result is the same: my original text file is full of zeros.

This aspect, however is a little bit more interesting I mentioned before: when I ran the text file through Recuva (see this: https://superuser.com/questions/2236...upted-txt-file; Here, the 2nd answer with the Recuva method. Now, previosly I had a very similar instance, when this one worked very well, now not so) it didn't turn my text file readable, like in the Super User example, but something like this (I quote myself again):

One

Code:

SQLite format 3

And the other:

Code:

ÐGOR‹Š

And many more like this.

The two questions I ponder:

- Why Recuva didn't recover my file, if it recover the file of the Super User user?

- Even if my text file can't be saved, how did it turn to all zeros, if I saved it previously, I just didn't save the incremental changes before the the power outage? For my technical interest. It was on an NTFS partition.

@Eric3742: I sure don't have any backup of Windows, Temp, System Files, AppData, things like that, I use Toolwiz Time Freeze which restores my Windows after every restart.