How do you replace the System32 and SysWOW64 folders

[zaza]

I copy pasted about a 100 dll files in both folders and replaced the existing dlls when someone claimed they would make a certain game work, well not only did the game not work but now half of my other games don't work either (windows still works fine though). Is there any way to restore the System32 and SysWOW64 to their original form without reinstalling windows?

Like for example maybe there's a System32 and SysWOW64 folders you can just download off the net since they're the same for all windows 7 installations?

Edit: Also tried using system file checker in a command prompt and it says it found errors but it could not fix them, tried it in safe mode and still could not fix them, opened the log file and found the bad dlls and replaced them and still it gave the same error.

 

[Phynaz]

Do you have a restore point from before you copied the files?

You could also so a Windows repair instead of an install, although I've never had luck with that myself.

 

[zaza]

Do you have a restore point from before you copied the files?

No, system restore is turned off.

And I've tried Windows repair in the past, it seems the installation disc has some compatibility issues that makes repair not work (even if it worked I think windows repair is just for when windows is unable to boot)

 

[Ketchup]

sfc might help here.

You could also try a repair install:
http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[sweenish]

That's hilarious.

 

[flexy]

No, system restore is turned off.

And I've tried Windows repair in the past, it seems the installation disc has some compatibility issues that makes repair not work (even if it worked I think windows repair is just for when windows is unable to boot)

You're talking about startup-repair. We're talking about a repair install which will replace all system files with the original ones from DVD. This is what you want.

 

[ArisVer]

Question here. When you do a repair install, do you have to install again the applications? I came across this and because I did not have the original software disks and their appropriate key codes I decided against it. Any workarounds?

 

[VirtualLarry]

That's hilarious.

Indeed. LOL.

 

[Hugh Jass]

LMAO!

 

[destrekor]

Question here. When you do a repair install, do you have to install again the applications? I came across this and because I did not have the original software disks and their appropriate key codes I decided against it. Any workarounds?

A repair install keeps everything intact but replaces Windows system components with fresh versions, to include all Windows DLLs.

If games installed any custom DLLs in the System folders (can't remember if any do or not), those might need to be fixed on their own. A game reinstall would do it, or sourcing the DLLs from trustworthy locations would be the other.


OP: Here's a hint... never listen to people who suggest changing a large number of files within system directories. Like... ever. Except on the rare occasion (0.0000000001% of the time), you should never, ever need to touch system files and folders.

I learned that lesson removing a critical DLL as a kid that killed the whole system. lol

 

[vailr]

As a last resort, maybe give this free program a try:
Tweaking.com - Windows Repair
http://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html
As you may or may not be aware: each .dll file needs to be individually registered from the command prompt.

Go to the Run item on the Start menu, and type:
regsvr32 <path & filename of dll or ocx>


There may also be a batch command to register/re-register all files in a given folder, which would likely fix your error.
See:
https://support.microsoft.com/en-us/kb/282747

 

[Billb2]

A repair install will replace all the .dlls that you replaced, but if you added any new ones they won't be touched. But if any of you software added their own .dlls with the same name, they will be overwritten with the original ones.

And as other have said LMAO at such a nOOb move!

My nOOb move was the first time I was dual booting and found all these duplicate files. You can guess the consequences of that..........