windows 7 sfc scannow found corrupt files but unable to fix Results


Sponsored Links:



i've been having some unusual computer behavior. when checking the disk, i got the following message:

"windows resource protection found corrupt files but was unable to fix some of them." it mentioned a log that was saved (CBS.log), though i'm not sure what to make of it.

what can i do to fix this? i have a lot of data on here that i don't want to lose. the computer does seem to be working mostly ok, but i did just get a BSOD and the above message.

this is Windows 7 Pro, 64-bit. and i ran malwarebytes and kaspersky but they came up clean.

thanks.

btw, i did run sfc/scannow, but still have an issue.




After killing off a minor Virus nuisance; I noticed some system functions like Event Viewer and MMC were not working properly and died with errors. After researching through Windows 7 forums and such the only official answer for restoration was SFC /scannow or using system restore to got back to a better time. Since I couldn't be sure of the proper restore point I decided to give SFC a chance. Well I did elevate a CMD promt to admin and started to run SFC /scannow. I took about 10 minutes to run what it called verification:
Beginning verification phase of system scan.
Verification 26% complete.
till it then completed verification. Then continued without updating the CMD screen till it ended with:
C:Windowssystem32>sfc /scannow
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windirLogsCBSCBS.log. For example
C:WindowsLogsCBSCBS.log

The maximum number of files have been repaired. To repair the remaining corrupted
files run sfc again.

OK so I just hit the up arrow key and put the command in again. same results exactly Di it again. you get the idea now I didn't count how many times I did it but it had to be at least ten (10). So I created a little script with 20 SFC /scannow and kicked it off ; still the same. So I did some research and could not find a way to increase the "maximum" files in the SFC end message. I checked each CBS log and noticed that the same files would error over and over.
2010-08-01 13:13:50, Info CSI 0000000b Hashes for file member SystemRootWinSxSamd64_1394.inf_31bf3856ad364e35 _6.1.7600.16385_none_572448461f98f8b91394ohci.sys do not match actual file [l:24{12}]"1394ohci.sys" :
Found: {l:32 b:7vx/jVsSrFzkxojky+qpWRqmgQPE3bbcbDVFu2INUpY=} Expected: {l:32 b:00UBTPFG+leyaCwYnV5/J9THjzIfJyPZEtYj53fCu3A=}
2010-08-01 13:13:50, Info CSI 0000000c [SR] Cannot repair member file [l:24{12}]"1394ohci.sys" of 1394.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

Well this then limits the number files it's going to "fix" since this group of files it can't fix grows I am guessing till SFC /scannow doesn't fix anything.

Right now my system is ok; I think. but not because of SFC /scannow but I used system restore.

So has anyone else noticed this little Windows 7 problem? SFC has been around since Windows XP but I have never tried it till Windows 7 since they don't have "repair" since Windows XP.

I'd have sent this to Microsoft but I have done similar things and they just pass it off with " have you tried System restore? "




I am running Windows 7 Pro x64, and I recently decided to try out System File Checker, just to ensure that everything in my OS was shipshape. After I entered sfc /scannow in Command Prompt, the verification phase began. After it completed, I received the message: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log."

I checked the log, but it was just programming language to me, and I couldn't decipher any of it. Does this message mean Windows is permanently corrupted, and I will have to perform a clean install? Or is there a workaround, found in the CBS log, which would permit me, or SFC to fix the trouble? Or could it even be a false positive, in the sense that I've installed something that Windows didn't like (such as a browser add-on or software) and everything is actually fine?




If Windows 7 develops a problem it can often be fixed by running this utility. The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed, or damaged versions with the correct versions if possible.

It needs to be run from an Elevated Command Prompt.
Right click: "Command Prompt" in "Start Menu - Accessories".
Click: "Run as Administrator".
Click past the UAC Screen.
In the Command Prompt Type: sfc /scannow and press "Enter"

It might or might not need your Windows Installation Disk in case it needs to fix something. It will let you know if it does. I've seen it go both ways. It'll take a while.

If you get a message saying it couldn't fix some files you can find out which ones. When SFC runs, it logs it's actions to the C:WINDOWSLOGSCBSCBS.LOG.

Open the Elevated command prompt again.
Type in: findstr /c:"[SR]" %windir%logscbscbs.log >%userprofile%Desktopsfcdetails.txt and press "Enter". This will place a sfcdetails.txt file on your desktop with the SFC scan details from the CBS.LOG.
Open the sfcdetails.txt and look for the unfixable entries.

The last time I ran this I found this entry.
"2009-08-09 13:16:27, Info CSI 000002db [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation".

All I had to do was reboot to fix it. There were others that it was able to fix. I've had great luck running this utility on Windows 7 and Xp in the past.

Once we get Service Packs for W7 that will open up another issue but not until then. In order to run this on XP SP3 I had to make a Windows XP SP3 Slipstream Disk. It's not a problem on W7 now though. We'll cross that bridge when we come to it.

There's a lot of other info out there on this. You could google for it if you like.




I have been getting these bluescreen errors since I have had my PC for 1 year. Most of them went away and some came back now. It only happens when I play games, like COD4 or Bad Company 2. It might have been direct x stuff I messed with the other day, but other than that here is the info. Punkbuster seems to be the problem here.
Windows 7 Ultimate 32-bit
Full Retail
1 year old
I installed the new OS again about 3 months ago.
Okay, so when I first purchased my parts, I got bluescreens installing Windows 7, and it ended up being I returned every part, got the same exact parts back but newer. The only new part I did not get back was my mobo because I sent it in for an RMA and they said everything passed the stress test. Then, I found Memtest+86 gave me errors for my RAM, returned my RAM 5 times and got the same exact time again because no money for new part. I did not do the Memtest this because I know after like 10 tries I will probably get an error.

So, the SFC /SCANNOW gave me this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:Windowssystem32>SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windirLogsCBSCBS.log. For example
C:WindowsLogsCBSCBS.log

I cannot open that file, and I tried to give me full permission to do so but cannot view it so now what can I do?

RAM Type: DDR3-1333
Speed: 666.67
Timings: 9-9-9-24
CBS.zipWindows_NT6_BSOD_jcgriff2.zip




Hi, all!

I know how to perform a nondestructive repair install of Windows 7 under ordinary circumstances, but everything I've read so far says that you simply cannot perform that procedure if you can't boot into Windows 7 full mode first (using the hard disk partition that you want to perform the repair install onto). Even Safe Mode just won't cut it, apparently.

But since I'm now always getting the dreaded "Black Screen of Death" (not its Blue cousin), the nondestructive repair install option is reportedly out of the question...

So my question is: Is there ANY workaround that would allow me to perform a nondestructive repair install anyway, even if the procedure is difficult and/or requires third-party tools, either freeware or commercial?

For just one possible alternative, would booting from an old backup partition on a separate USB harddisk allow me to do a repair install on the internal HDD & partition with the Black Screen problem? If so, how?

I realize that I could rewrite the internal disk partition that causes the Black Screen with the backup partition I just mentioned (and then run the repair install), but of course that would destroy all the updates and changes I've made since the backup, which is exactly what I'm trying to avoid by doing the nondestructive repair install in the first place!

I also realize that if I were able to fix the Black Screen problem in the first place, there would be no need to do a repair install. Unfortunately, nothing I've tried has worked! Here's what I've already tried that have failed...

I booted up with the installation DVD and tried "Startup Repair" (in fact, I tried it three times in a row, as one site recommended), but that always fails with the message "Startup Repair cannot repair this computer automatically" with one of the problem signatures reading "MissingOsLoader". I found dozens of support sites explaining how to fix that, including:Use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows,

BCDEDIT - How to Use,

Command Prompt - Repair Missing or Corrupt Files,

How to Fix Windows 7 When It Fails to Boot,

Windows 7 will not boot past Starting Windows or in Safemode,

Troubleshooting Windows 7 Failure to Start,

Windows 7 does not boot into any mode (Normal or safe), neither the Recovery partition nor the recovery discs work,

Failed to Find OS Load. Startup Repair FAILED,

Automated Startup Repair fails. Cannot find OS Loader.,
...but I've tried everything they've suggested and nothing yet has solved my problem.

I've even tried the "Nuclear Holocaust" option described in this very good tutorial from the makers of EasyBCD: Recovering the Windows Bootloader from the DVD, but even after doing all that, the Black Screen always appears when I try to boot (even from Safe Mode and Safe Mode with Command Prompt, etc.)

For the record, I've tried using System Restore with either of the two recent Restore Points, but no luck there (the older restore points were too old). I've also tried booting with the "last known good configuration", but the results were the same. I also ran "CHKDSK C: /F /V /R", which found and repaired a single corrupt sector, and when I ran it again, no problems were reported. Also, I ran "SFC /scannow /offbootdir=C: /offwindir=C:windows" a few times and it found and reportedly repaired a few problems. Here's the log's contents:

Code: 2013-02-09 03:03:45, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:03:45, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:03:45, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:03:45, Info CBS Ending TrustedInstaller finalization. 2013-02-09 03:51:57, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:51:57, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:51:57, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:51:57, Info CBS Ending TrustedInstaller finalization. 2013-02-09 03:55:06, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:55:06, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:55:06, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:55:06, Info CBS Ending TrustedInstaller finalization. 2013-02-09 05:48:21, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 05:48:21, Info CBS Starting TrustedInstaller finalization. 2013-02-09 05:48:21, Info CBS Trusted Installer core was not initialized. 2013-02-09 05:48:21, Info CBS Ending TrustedInstaller finalization. 2013-02-09 05:59:58, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 05:59:58, Info CBS Starting TrustedInstaller finalization. 2013-02-09 05:59:58, Info CBS Trusted Installer core was not initialized. 2013-02-09 05:59:58, Info CBS Ending TrustedInstaller finalization. 2013-02-09 08:38:21, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 08:38:21, Info CBS Starting TrustedInstaller finalization. 2013-02-09 08:38:21, Info CBS Trusted Installer core was not initialized. 2013-02-09 08:38:21, Info CBS Ending TrustedInstaller finalization. I don't know what to make of any of that, however. But remember that the SFC scans were all done from the Win 7 Install DVD command line, so there was no networking in place and apparently the install DVD repair tools don't run with the "Server" or RPC services running, which perhaps explains those error messages.

If anyone's interested, I've attached a zip file named BlackScreenLogs.zip that contains two files: bcd.txt - which is the output from the bcdedit enum all command, and ntbtlog.txt - which is a recent boot log (from using F8 to boot with boot log option).

So now I'm pretty close to my wit's end, but I still absolutely LOATHE the idea of perfmoring a fresh new re-install, which -- considering all the third-party applications and such I'd need to re-install -- would require at least a week of horribly tedious work!

That's why I'm desperate to find a workaround to this baffling limitation imposed on doing nondestructive repair installs on MS operating sytems more recent than XP.

Any suggestions, folks? Attached Files BlackScreenLogs.zip (12.1 KB, 5 views) Last edited by Ninethe; 02-13-2013 at 08:06 AM. Reason: Added log zip file attachment Share Share this post on Digg Del.icio.us Technorati Twitter
Operating System Windows 7 Home Premium 32-bit (Not SP1 yet)
Computer Type Dell Inspiron 1526 Laptop
OS Service Pack SP1 (build 7601)
Internet Explorer Version 8
DirectX Version 11
CPU Type and Speed AMD Turion 64 X2 Mobile TL-60 - 2GHz
CPU Cooling (on board)
CPU Idle Temp ~ 140 F
CPU Load Temp ~ 165 F
Motherboard Chipset Mobo: Dell Inc. 0WP019 - Chipset: N: ATI RS690/RS690M - S: ATI SB600 rev. 00
System BIOS Revision A16
System Memory Type 2 GB DDR2
System Memory Speed 332MHz
System Memory Clocking 5-5-5-15
Video Card Type and Speed ATI Radeon X1200 Series - 27000 HDMI
Video Card Cooling (on board)
Video Card Temperature (not reported)
Sound Card IDT High Definition Audio HDMI
Hard Drive 250 GB WDC WD2500BEVS-75UST0 Sata
Optical Drives PBDS DVD+-RW DS-8W1P
Network Adapter NETGEAR WNA3100 N300 Wireless USB Adapter
Network Speed 50 Mbps
Anti-virus Software Avira 2013 / Comodo Firewal
Computer Skill Level Self-Taught Expert
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 02-13-2013 #2 patcooke Tier 2 Moderator Microsft Most Valuable
Professional  
Join Date May 2010 Age 67 Posts 2,167 Re: Is there ANY workaround for Win 7 nondestructive repair install when unable to boot? Black screen is cause by failure to access a critical system file - usually because it is missing/corrupt etc or because it has been compressed. If you can identify the mising frile from any report to the screen during failre you may be able to replace it. Failing that the prospect of reinstalling all from scratch (loathsome though it may appear) may be as nothing compared with the spectre of interminable problems raised by what seems to be a system which has suffered serious corruption and sooner or later would require a clean reinstall which in the long term I reckon is to be the lesser of two evils. I get the impression this problem has already consumed significant time, effort and head banging! For the future I would strongly recommend you look into implementing a regular backup regime of imaging your system drive on a regular basis using something like Acronis True Image. You can download a full working trial copy, it is not expensive and the very first time you need it (incircumstances such as this) it is worth every penny. It is also insurance against total hdd failure, bad malware infection, bad installs and host of other evils.




I recently tried to update Adobe reader when I received a notification that there was an update. It failed to install. After 3 tries, I went to help icon. It advised uninstalling Adobe reader and reinstalling it. The version that I uninstalled was 9. something. The version that I attempted to reinstall was Adobe 10. It downloaded but did not install. "Windows Installer service could not be accessed."
I went to Windows Help. It advised getting out my Windows 7 Home Premium installation disk , signing in as an administrator and running a scan "sfc/scannow" This scan said it found that some files were corrupted and it was unable to fix them.
Another suggestion in Windows Help (Answers) said that I should find Windows installer under Services(Administrative Tools), click on it, and if it said manual start, change it to automatic start. I did this. I'm still unable to install Adobe reader.
Any suggestions would be appreciated.
Thanks




Several months ago I purchased an upgrade package to move from Office 2007 to Office 2010 Professional Plus. Each installation fails giving the following message:

Error 1935: An error occurred during the installation of assembly component {3F-A0170E-227C-37C7-BACD-64691A992C81}. HRESULT: 0x80070003.

I have spent hours (HOURS!) searching for solutions including the Microsoft Answers website and various other "hits" from Google. I have also been getting an HRESULT error when attempting to update iTunes, and after updating to iTunes 10.4, I have to start it using XP compatibility mode.

I tried a "safe" reinstall of Windows 7 (running SP1, and uninstalled SP1 first), and when I did that, there was a major snafu resulting in having to select a boot option at each startup. I used Acronis and restored to an earlier point which fixed that problem.

I am convinced that it is a .NET problem or C++ file corruptions. However, running sfc/ scannow reveals no problems. I also ran several suggested Net Framework repair options I found; alas, no success. I have NOT uninstalled Office 2007 secondary to reports that after attempting to install Office 2010, users were unable to reinstall Office 2007.

I even considering buying Win7 Professional and installing that to fix files, but was told that would probably be a waste of money and time.

I am fairly computer literate (CompTIA A+ certified). I am close to just giving up and waiting until I replace this Dell XPS 720 in a year or so (oh, and again Windows 7, SP1, TONS of free space on C drive, 8 GB RAM, and all other programs except iTunes run fine - I have to now start iTunes running XP compatability). Just thought I would reach out to this talented and knowledgeable group.

Thanks for any input, suggestions, or insights.

Ed