Jump to content
Sign in to follow this  
Followers 0

11 posts in this topic

Posted

I have a piece of data that I want to pull out of a Windows registry file. It was generated by XP, but it's in the System Restore folder, and I do NOT want to go back to a few days ago for this little bit of info. Is there a way to convert a .REG file into plain text from the command line? Or perhaps a GUI to read this info?

Thanks,

- brad

Share this post


Link to post
Share on other sites

Posted

i think you can just rename the extention... i know you it works the other way around (txt to reg)

Share this post


Link to post
Share on other sites

Posted

to read it, just use notepad, to convert it to txt, change the file extension to .txt... that's all....^^

Share this post


Link to post
Share on other sites

Posted

to read it, just use notepad, to convert it to txt, change the file extension to .txt... that's all....^^

*sigh* that's the solution yes........my how some people underestimate how useful notepad is.

Share this post


Link to post
Share on other sites

Posted

Cmon what do you take me for, a n00b? :wacko:

If it were a plain text file i would have found the data already. It's a machine code file, that starts with this:

regf'1  '1  

Share this post


Link to post
Share on other sites

Posted

That's not really a .reg file then. Or maybe it's just compressed?? You're probably screwed if windows update encodes all of its data.

Share this post


Link to post
Share on other sites

Posted

That's not really a .reg file then. Or maybe it's just compressed?? You're probably screwed if windows update encodes all of its data.

actually, it is. once i had a look at the .reg file of the reset crack and it also was like that :p

Share this post


Link to post
Share on other sites

Posted

Just adding my two cents worth to the discussion, even though I can't solve the problem for you.

Since WinXP and Win2000, regedit writes exports into .reg files, which are binary and can not be read with notepad or any other texteditor. If you want to have a readable export from regedit under WinXP you must choose a different file type (REGEDIT 4) when doing the export.

However, I do not know how to convert from regedit5 to regedit4 formats.

But what you could do is to export exactly those keys that are in your unreadable .reg file from your current installation (so with different values) into another file, then re-import the .reg file you can't read. Re-export it into a regedit4 format, and finally re-import your original settings. That way your system will be unchanged and you can then read you registry keys and values. All this is of course assuming that you know which keys are in that .reg file you have.

Share this post


Link to post
Share on other sites

Posted

[1] export your .reg file from XP

[2] find the exported .reg file

[3] right click and select 'Edit'

[4] Go to the 'File' menu and then click 'Save As...'

[5] In the Encoding section, Change it from 'Unicode' to 'ANSI'

[6] Click save, you might also have to change 'Windows Registry Editor Version 5.00' to 'REGEDIT4'

if that doesn't work, I think that wordpad can also open Unicode files

Share this post


Link to post
Share on other sites

Posted

if that doesn't work, I think that wordpad can also open Unicode files

Notepad can open and edit Unicode as well. So need to use wordpad.

Share this post


Link to post
Share on other sites

Posted

This reg file was already generated by Windows - it's in my System Volume Information folder, as part of a restore point. That's why I didn't want to import it.

Hasn't someone invented a Reg5 > Reg4 / Text converter? :p

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.