I unwittingly installed a bit of Adware, which is now gone, but the damage remains.

AdAware didn't catch it. Neither did AVG AntiVirus. I uninstalled the program before it did any significant damage, but one annoying problem persists: I can no longer run RegEdit (directly). The program had deleted RegEdit.exe, but I was able to copy it back from the XP cd.

When I try to run RegEdit, I get an error: "The application failed to initialize properly (0xc0000005). Click OK to terminate the application."

But here's the kicker: if I RENAME Regedit (ex: "xRegedit.exe"), it opens just fine.

Every "fix" I've researched online doesn't address this specific problem. I've run "sfc /scannow", did a System Restore, msconfig and HiJack show no suspicious programs running. I suspect some odd permission was changed, but I have no clue what.

I ran the "Doug Knox XP Security Console", and "Disable RegEdit" is unchecked. Checking and Unchecking changed nothing.

This isn't a catastrophe since I can always just rename the programs that are affected to get them to run, but it is INCREDIBLY annoying.

Anyone know a fix (short of a reinstall)? Thx.

System: 32bit WinXP Pro with SP2.

Sometimes Virus leave traces that is very difficult to change or remove even they got deleted. The best way will be to try a repaire with the XP disc or if this don't work then try a fresh install of Windows.

Yeah, that seems to be it.

It's looking more and more to be the case.

I would do a repair install, except that after doing so, I'd have to reinstall the 180+ "service updates" from MS all over again. I'm not about to do that just to get "RegEdit.exe" to work again (when I can still run it by simply renaming it).

There's GOT to be another way. Something less drastic than a reinstall.

Thanks for replying though. I think this problem is too obscure to be solved here. (I'm a tech, and have never seen... or even heard... of a problem like this before.)

I found this which seems bit similar like your problem, not sure it will help but no harm if you choose to have a look at it.

Interesting info, but doesn't seem to apply.

Thanks for the link. It's a link I hadn't seen before, and the fact it mentions "renaming" to get a program to work certainly catches my interest, though their solution didn't seem to apply to me.

Checking the particular Reg entry they point to, I find only valid audio/video drivers. I searched through nearly the entire registry looking for other "phantom drivers" in the registry, but nothing turned up, and there are FAR too many drivers to check them all by hand.

I use a good registry cleaner ("Registry Mechanic") that would of caught any driver entries with no corresponding file, and I've personally checked by-hand every entry that contains "Regedit.exe" to see if something was doing something it shouldn't. I found nothing unusual.

If the problem is in the Registry itself, I don't see it (nor does "Registry Mechanic").

Thanks for the reply though. This is the weirdest mystery. But at least I now have another avenue to consider (an errant driver).

One more thing; can you make an icon of regedit executable on your desktop; then right click on it and run it as administrator?

Let me know what it does.

Mugsy,
If you do not want to format, Fred Langa had a Windows Secret that I have used successfuly many times. check it out at:
http://www.informationweek.com/news...9400897&queryText=fred langa do not format xp

No go.

Interesting idea.

I just tried it. No difference. I right-dragged RegEdit.exe to the desktop to create a shortcut, then clicked Properties, the Advanced button, and checked "run with different credentials".

By default, the credentials was my User account. I selected "Administrator" instead, but still get the same error when it tries to run.

Interesting idea, but it seems there's something else going on.

Interesting, but problemmatic

Interesting information, but that tip overwrites the entire Windows directory, which would re-initialize Windows, resulting in having to reinstall all those Windows Service Pack patches that I described earlier (there's over 190 of them now), which I'd REALLY rather avoid.

I run the free Belarc System Advisor on the first of every month so that I always have the latest Security Releases from MS installed. When you reinstall Windows, all those patches are wiped out and you must reinstall them all over again... an unbelievable pain.

Whatever is causing this problem, it MUST be simply a matter of "permissions". But I've given every Account ("User", "Administrator", etc) "Full Control" and still the problem remains.

Thanks for the idea though.

But, you do not have to re-install applications, jst SP3 and 60 some patches. Much less painless than a format and fresh install.

I use SP2 (don't like SP3), so the number of patches is far more than 60.

One more thing; you say when you try to run and nothing happens, check processes running on your system while you do that; does regedit shows up in running processes?

A warning. Not, nothing

I shouldn't have said "nothing".

If I run "regedit.exe", I get an error message dialog entitled "regedit.exe - Application Error" that reads:

"The application failed to initialize properly (0xc0000005). Click on OK to terminate the application."

Clicking OK results in the same error message appearing a second time. Clicking OK again gets rid of it.

I opened up the Task Manager while the error message was on screen, but found no unusual or unfamiliar processes running.

If I rename regedit.exe to "xregedit.exe" or "regedit.com", it runs just fine. Something just seems to be preventing "regedit.exe" specificly from running (and yes, I did scour the Registry looking for unusual references to "regedit.exe").

(I should note, "regedit.exe" won't run from Safe Mode either. Same error (unless I rename it, same as regular mode).

Well having tried so many things, i think there is no harm in trying one more:

keep your regedit executable's original file name

1. Open command prompt with administrator account
2. type: sfc /scannow

This will scan all windows files; and should repair any which are damaged if possible.

Its a long shot frankly but what the hell

Tried it.

Thanks for the reply, but check my original post. That's one of the first things I tried.

Oops sorry missed that out; only issue then is to find some other/untried solution to try out

This is probably of no help with your specific problem, but I had a similar problem on my XP system - only with screen savers. I had several screensavers that I particularly liked from an old W95 machine, a couple of them I knew also worked in W98, ME and 2000. I installed these on my XP system and they didn't appear in the list. Couldn't figure what was wrong but renamed them all (placed an underscore at the start) then copied the same files from my W95 machine to the XP machine. Went to the screensaver list ...and there were the renamed screensavers! I could never get these files to appear with their original names, but could alter the names in any way, including completely renaming them, and they worked fine.

Perhaps this is some arcane glitch in XP that we have both managed to trigger.

In your case, what happens if another program calls regedit? For example, in some of the windoze help files there is the "click here to run registry editor". There are also some system utilities, such as vid driver tweak programs, that can call regedit.

regedt32.exe, same thing.

The most obvious example of that would be "regedt32.exe" in the system32 folder. As of XP, it merely calls "regedit.exe" ("regedt32.exe" was kept simply for compatibility reasons). Running it gives the same error, as does any shortcut to regedit.exe that I create.

Theoretically, something is telling XP not to allow a program named "regedit.exe" to run, but I tried renaming another, completely different program "regedit.exe", and it ran just fine. So there isn't anything obstructing the filename specifically (which explains why I didn't find anything unusual in the Registry).

Registry cleaning programs like "Registry Mechanic" run just fine, but doesn't detect/fix the problem. Ditto for AdAware or AVG AV.

For some unfathomable reason, it is simply THAT one program ("regedit.exe") that won't run while it has THAT name. Even if I copy it to another folder, or try to run it in Safe Mode, I get the same error. So far, I have not found any other program/exe that won't run.

Well another idea to try out is:

Make a copy of regedit.exe in another location (leave the original in windows\system32, but rename it once you create a copy); e.g. copy regedit.exe in Windows folder (that way you wouldn't need to define a path for it/or shortcut).

Try running it and see what it does.

Tried all that.

Actually, "regedit.exe" exists in BOTH the Windows and system32 folders.

"Regedit.exe" will not run as is. No matter where I copy it to or shortcuts I direct to it. I even tried running it from a "regedit.bat" batch file. Same thing.

I've tried running it from Safe Mode, I've tried disabling EVERY system/start-up file using msconfig. Nada.

The program just will not run, from anywhere, using its true filename. Nor can Windows be "tricked" into calling it from a shortcut or bat file.

But it DOES run if I rename it.