Main Forum > Tweaking.com Support & Help

Win 7 / 64 Numerous "Regedit.exe" missing messages during repair

(1/3) > >>

GHenry:
I clicked those Messages away each time; now I do not know whether the repairs were successful. In a subsequent search it turned out that c:\windows, c:\windows\sysWOW64 and two instances in c:\windows\winsxs did not contain that file.

What should I do?
G. Henry

Willy2:
- REGEDIT should be present in the "C:\windows\system32" and/or in "c:\windows"
- Do you know someone who has also a Win 7 system ? Then copy that file to one of the folders above.

GHenry:
Before running tweaking.com, c:\windows DID contain regedit.exe. When printing didn't work either after the repair (PRINTSPOOLER repair), I restored the original registry, and bang - regedit.exe was there again, and the printer worked fine.

So I'm not sure whether I should trust tweaking.com...

Willy2:
- Your problem makes it perfectly clear why making a backup is essential !!!!
- What version of Windows Repair did you use ? And what repairs did you run ?
- Based on my personal info (also a Win 7, 64 bit system) "Regedit.exe" is (physically) located somewhere in the in "winsxs" folder. But both "system32" & "c:\windows" contain a junction link to the file in the "winsxs" folder.

Shane:
My program doesnt remove any system file or anything like that and the repairs call regedit to apply the .reg files to the registry, by any chance did you get a screen shot of the error so I could see exactly what it said?

What is also strange is that restoring the registry wouldnt have restored any missing system files, it only restores the registry itself. So it is odd how the file showed back up after that. But the system file checker should have put regedit back if it was missing, which is most likely what happened when you had rebooted. :wink:

I havent had any other user ever report this problem with regedit missing, I would really like to find out why and what is happening.

If you dont mind helping, would you be willing to first do a backup of your system so that you can restore if needed and then try the repairs again and if you get the error take a screen shot of it so I can see it as it is? That way I can try to find out what is going on :-)

If not that is fine as well.

Shane

Navigation

[0] Message Index

[#] Next page