New
#470
OK
I will do that.
I thought maybe you might be able to tell from the unable to fix list what may be a problem.
Thank You
OK
I will do that.
I thought maybe you might be able to tell from the unable to fix list what may be a problem.
Thank You
Hi,
I would like to know whether this will fix the missing cleanup.dll error.
I get this kind of error after removing some malwares from my lappy.
Hello Nio, and welcome to Seven Forums.
Windows 7 does not come with a cleanup.dll file by default.
In this case, I would recommend that you create a new thread in our System Security forum with details about this issue to help make sure that your system is clean.
Hello,
I tried to run : sfc/ scannow but it says that i need to be an administrator to do this. But i am one! Anyone could help me, please? I have the issue with windows opening every folder in a new windows instead of the same window and this could help me alot!
Type "cmd" in search pgms & files then right click on it from the list & left click "Run as Administrator".
Elevated Command Prompt
hi,
i ran a sfc scan telling me that there are corrupted files which cant be repaired.
i checked on the CBS.log but only found 4 entries all related to a file called
PINTLGB.IMB
i dont know what to do next since i dont have a win7 installation DVD with me. im currently living in cambodia and my DVD is at home
right now im trying to fix a problem with my internal DVD/BD-Rom drive...thats why im trying to fix the sfc entries as far as i can.
it would be great if someone could just have a short look on my cbs.log?
i realy dont know how to do to solve my problem.
thanks
Hello Ozelot, and welcome to Seven Forums.
From the blue Note box under Option Two, you could download and run the 64-bit (x64) System Update Readiness Tool to repair the component store, restart the PC afterwards, and try the sfc /scannow command again to see if may be able to repair the system files.
Hope this helps, :)
Shawn
Thanks, that was fast
i tryed allready this option 2.
but since it still wasnt able to fix the file i ran sfc /scannow some more times afterwards, without results.
the logfile doesnt look ok to me, many strange entries, although it only finds 1 corrupted file,
but im not that familiar with this matter.
Did you already install the 64-bit (x64) System Update Readiness Tool when you previously gone through Option Two?
The log file you posted is the full CBS.LOG file instead of the sfcdetails.txt file created from Option Three. The sfcdetails.txt file only contains the details from the SFC scan, and not any of the other system information not from the SFC scan.