Try this. It can't hurt. It will just load the default registry settings for Defender:
https://dl.dropboxusercontent.com/u/47644676/7%20defender.reg
https://dl.dropboxusercontent.com/u/47644676/7%20defender.reg
Try this. It can't hurt. It will just load the default registry settings for Defender:
https://dl.dropboxusercontent.com/u/47644676/7%20defender.reg
Mine is nothing more than an export of the Win 7 registry settings for the Defender service.
Not sure of the source of that link you gave, but it doesn't match with mine.
If you aren't going to let me connect and play would you post a reg dump of the following locations for me:
Hey Jimbo, check this out:
http://chentiangemalc.wordpress.com/2011/05/01/case-of-the-ie9-partial-download-fail/
ProcMon with filter settings may help you nail the perp.
I know you said you ran the AV uninstallers but, I had this same problem last week and fixed it by running Avast and Norton's uninstallers. I ran them one after the other so I'm not sure which one did the trick. Might be worth another shot.
Jimbo, you might want to check Windows Defender's program dir - seems a very similar if not exact problem you are having was for the most part solved on my forums here, where he says the defender program dir had it's files / subdirs replaced with shortcuts and symbolic links to system32\config.
Seems replacing the dir with known good files/subs from a working system fixed it for him. Note it's better to rename the existing dir first instead of an outright delete attempt (since it's pointing to system32\config!) until you destroy the symlinks, which you can use the NTFS Junctions in d7 for (tweaks > all versions)
Ok....might be a little off the wall.....
But did/could you try a registry cleaner such as the one with Ccleaner?
It's funny, yesterday I went in there and I think all the icons looked ok but I tried to go into the en_us folder and got a permission denied. I decided to leave it until today so I will go in later and see if that's the issue. Last night when I got home I remember the "en_us" thing and was able to go into it on two machines. This really looks like the issue, but I wont be in until later.