Yep, evidently there's left over files that whatever you used left behind.
Unless you know exactly what files it added and where, about all you can do is do a system restore using a restore point dated before you installed gpedit.msc.
Otherwise, it's not going to hurt anything to leave them as is if you wanted though.
I have a restore point, but it is only limited, what I mean is the restore point I created before installing gpecit.msc is no longer available because every after three weeks I make restore points, and also while uninstalling program using revo, it creates a restore point.
What d you mean by it doesn't hurt? Is it okay that it is still here in my unit?
Thank you for your willingness to hep. :)
Since those files are the only thing found wrong by SFC, and you are not having any other issues, then it wouldn't hurt to not worry about trying to find and remove all the files that were added when you installed gpedit to avoid potentially causing more harm by deleting the wrong file.
These files will not cause any issues other than they just will not work if you try to open gpedit.msc.
Is it odd that I am unable to check the particular file I think is corrupted?
C:\windows\system32\rundll32.exe
Can't open sound devices from the tray after running SFC and fixing integrity. Is a restart required?
Big thanks to Brink though :)
Hello Bental, and welcome to Seven Forums. :)
To scan that specific file, the command would be this below.
sfc /scanfile=C:\windows\system32\rundll32.exe
Restarting may sort sound devices.
Hi thanks a lot of the sfc scan detailed post i went thru the steps as im having a lot of problem with my new upgraded PC lot of bluescreen try to check with memtest ran into few more problems and i was not able to restore system to previous date finally i managed to do it and ran sfc scan and im getting this error now.
I will post BSOD in the proper thread if i get it again.
Also attached the .txt file of the sfc details.
I'm not running on a AMD processor, im on intel i5 4670.
"main.cpl" of Microsoft-Windows-main, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
Hello humanoutlaw,
Your SFC details show that the main.cpl system file in the folder locations below cannot be repaired. It's showing a hash mismatch for both the system file and copy in the component store.
This file is the Mouse Properties control panel item.
- C:\Windows\System32
- C:\Windows\SysWOW64
- C:\Windows\WinSxS\amd64_microsoft-windows-main_31bf3856ad364e35_6.3.9600.16384_none_98badf7befde219d
- C:\Windows\WinSxS\x86_microsoft-windows-main_31bf3856ad364e35_6.3.9600.16384_none_3c9c43f83780b067
If you have not already, do all of the listed items in the blue note box under step 4 in OPTION TWO to see if that may allow SFC to be able to repair the file afterwards.
Quote