Corrupt File recovery/Translating raw ASCII data to Text

[richards688]

I got this text file(attached) that is not readable but it is important. any suggestion please?

[Hagar Delest]

Hi and welcome to the forum!

Anyway 908 Bytes, it's quite nothing. So nothing to recover at all.
What happened exactly? You can have a look at this topic: [Tutorial] The Dreaded Pound Signs: file reduced to ####. It may apply to your case also.

[RoryOF]

I got nothing from it with a plain text editor.

[robleyd]

Linux describes it thus:

Code: Select all

bash-4.3$ file weird.txt
weird.txt: Little-endian UTF-16 Unicode text, with very long lines, with no line terminators

You could try some software that converts UTF-16 to a more useful format but it may not work - I tried iconv and got an error. In any case, it seems not an AOO issue.

[richards688]

If I don't remember it wrongly, it was saved as UTF-8 or Unicode format. Somehow I can not successfully recovered context. It has bitlocker drive recovery key to unlock the important storage drive. I have not found BEK file. So this becomes only chance to unlock the bitlocker drive. Any suggestions are appreciated !

[robleyd]

I suggest you try asking on a Windows forum as it seems to be a Microsoft product bundled with Windows.

As I mentioned, Linux recognises it as being UTF-16 Unicode format.