[SOLVED] [Win8Pro] Corrupt files/unable to fix/CBS files posted

schillist

Active member
Joined
Sep 5, 2013
Posts
32
Hello,

I'm using Win 8 Pro via Parallels 9 on my mac.

Recently, some program icons have been disappearing, so I thought I should run sfc /scannow.

It said there were corrupt items, and that it could fix them. I want to upload the CBS file, but I did compress it, it's 19MB and this site won't allow it.

I uploaded it via SendSpace. It was the best I could manage. I hope this isn't a problem.

http://www.sendspace.com/file/b2igy0

Thank you very much for your help. I love sysnative.com.
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Hello schilist, welcome to Sysnative!

SFC is reporting that thousands of files are corrupt on your computer but I don't believe it - I dealt with a very similar thread a few days ago where SFC reported most, if not all, system files as corrupt, but running SFC again came back clean, so let's try that:

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

I've typed the copy command exactly and it does not copy anything to the desktop at all.
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

It says one file copied, but nowhere on the Desktop is the file. Furthermore, when I do a system-wide search/scan for the cbs.txt file, it is non existent!
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

128MB!? Wow, must be a new record! If I remember correctly, Windows should archive the CBS log when it reaches the 50MB mark so I have no idea why it hasn't done so here. It's no problem, but just for future reference, it would have been better if you'd uploaded the compressed file to SendSpace :)

463,181 lines of CBS log, this is going to be fun! After a little fiddling with your CBS log, I've got a list of files that are corrupt on your computer and I can say that the grand total is 12,271. It's just absurd, there's no way that many files are corrupt on your computer. This is the fourth time I've seen this happen in the last 5 days, where SFC thinks everything is corrupt, so I don't know what's happening to be honest. In one of the threads, the problem simply disappeared on the second SFC run, so let's see if that sets things straight:

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

I'm running that now. It's going to take 75-80 minutes for it to complete though.

Do you think it's because i'm using Parallels 9 and it's a virtual machine?

Also, what's happening to my programs' icons? Some are there, some are not. I have no idea how to recover them.

I'll post the cbs.txt results when it is completed.

Thank you!
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

I'm running that now. It's going to take 75-80 minutes for it to complete though.

Do you think it's because i'm using Parallels 9 and it's a virtual machine?

Also, what's happening to my programs' icons? Some are there, some are not. I have no idea how to recover them.

I'll post the cbs.txt results when it is completed.

Thank you!


Thanks for the log, but I'm afraid the 'problem' is still here. I still don't believe it's correct though, the three threads that also have this problem have 11,889, 12,271 and 2,055 files corrupt which is more than I've ever seen, all put together. It's just too coincidental for my liking. I think we should ignore it for the time being, then run SFC again in say a week's time to see if the problem persists.

Let's rebuild the icon cache and see if that makes a difference:

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    ie4uinit.exe -ClearIconCache
    taskkill /IM explorer.exe /F
    DEL "%localappdata%\IconCache.db" /A
    shutdown /r /f /t 00

  4. Your computer will now reboot.

Let me know if the problem still exists after this :)

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Thank you for helping me. I appreciate it!

Do you really think there is something wrong with my Windows 8 Pro installation? Maybe it's because it's being run in a virtual machine via Parallels? It has me upset that it might be corrupt.
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Hi schillist,

Sorry, I forgot to answer your Parallels question! I don't think it's a Parallels issue, simply because of the other similar threads I'm dealing with at the moment. If it was just your thread with this scale of corruption, then I might suspect Parallels or a failing hard disk.

Let's check the files ourself :)

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    dir %windir%\winsxs /s > %SYSTEMDRIVE%\tom982.txt

  4. This will create a text file called tom982.txt in the root folder of your main drive (e.g. C:\tom982.txt). Zip this up and attach it to your next post please.

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Excellent! You really do have nothing to worry about now :)

If we look at the CBS log, taking the top few files as an example:

Code:
2013-09-08 12:15:10, Info                  CSI    0000000f [SR] Beginning Verify and Repair transaction
2013-09-08 12:15:10, Info                  CSI    00000010 [SR] Cannot repair member file [l:32{16}]"1394ohci.sys.mui" of 1394.inf.Resources, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-09-08 12:15:10, Info                  CSI    00000011 [SR] Cannot repair member file [l:24{12}]"1394.inf_loc" of 1394.inf.Resources, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-09-08 12:15:10, Info                  CSI    00000012 [SR] Cannot repair member file [l:24{12}]"1394ohci.sys" of 1394.inf, Version = 6.2.9200.16384, 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, file is missing
2013-09-08 12:15:10, Info                  CSI    00000013 [SR] Cannot repair member file [l:16{8}]"1394.inf" of 1394.inf, Version = 6.2.9200.16384, 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, file is missing
2013-09-08 12:15:11, Info                  CSI    00000014 [SR] Cannot repair member file [l:32{16}]"1394ohci.sys.mui" of 1394.inf.Resources, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-09-08 12:15:11, Info                  CSI    00000015 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Common-Drivers-Package-drivers~31bf3856ad364e35~amd64~en-US~6.2.9200.16384.INF_1394"
2013-09-08 12:15:11, Info                  CSI    00000016 [SR] Cannot repair member file [l:24{12}]"1394.inf_loc" of 1394.inf.Resources, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-09-08 12:15:11, Info                  CSI    00000017 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Common-Drivers-Package-drivers~31bf3856ad364e35~amd64~en-US~6.2.9200.16384.INF_1394"
2013-09-08 12:15:12, Info                  CSI    00000018 [SR] Cannot repair member file [l:24{12}]"1394ohci.sys" of 1394.inf, Version = 6.2.9200.16384, 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, file is missing
2013-09-08 12:15:12, Info                  CSI    00000019 [SR] This component was referenced by [l:192{96}]"Microsoft-Windows-Common-Drivers-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.INF_1394"
2013-09-08 12:15:12, Info                  CSI    0000001a [SR] Cannot repair member file [l:16{8}]"1394.inf" of 1394.inf, Version = 6.2.9200.16384, 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, file is missing
2013-09-08 12:15:12, Info                  CSI    0000001b [SR] This component was referenced by [l:192{96}]"Microsoft-Windows-Common-Drivers-Package-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.INF_1394"
2013-09-08 12:15:12, Info                  CSI    0000001c [SR] Verify complete

Okay, from the errors we can see that the following files are missing, not corrupt, but missing:

1394ohci.sys.mui
1394.inf_loc
1394ohci.sys
1394.inf

All of which are version 6.2.9200.16384 (Windows 8 RTM).

Now looking at the file you just gave me, which is a list of the Windows components on your computer:

Code:
 Directory of C:\Windows\winsxs\amd64_1394.inf.resources_31bf3856ad364e35_6.2.9200.16384_en-us_bb849515aba3cd8f

07/26/2012  03:48 AM    <DIR>          .
07/26/2012  03:48 AM    <DIR>          ..
07/26/2012  03:48 AM             3,910 1394.inf_loc
07/26/2012  03:48 AM            11,776 1394ohci.sys.mui

 Directory of C:\Windows\winsxs\amd64_1394.inf_31bf3856ad364e35_6.2.9200.16384_none_53f8fe038fac2809

07/26/2012  04:02 AM    <DIR>          .
07/26/2012  04:02 AM    <DIR>          ..
07/25/2012  04:15 PM            11,232 1394.inf
07/25/2012  10:26 PM           226,304 1394ohci.sys
               2 File(s)        237,536 bytes

They're still here! :) Now we need to know why SFC (and maybe Windows as well) thinks these aren't here.

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following command into it, press enter afterwards.

    DISM.exe /Online /Cleanup-image /Restorehealth

  4. Right-click on the Command Prompt window and click Select All, now press enter. All of this text is now copied.
  5. Paste (Ctrl+V) it into your next post please.

Tom
 
Last edited:
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

I'm not understanding the directions with the DISM commands. I press enter after the DISM.exe and after the online? I'm really confused by this as well as inverting the color.
 
Last edited by a moderator:
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Hi Schillist,

I have amended the instructions and hope they are a little clearer now, let me know if you're still unsure :)

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\Windows\system32>DISM.exe /Online /Cleanup-image /Restorehealth


Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384



Is this what you were looking for?

I don't know if I did this properly. I don't even know if it is still running.
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

That's perfect, thank you. Now can you upload your CBS log again please :)

Tom
 
Re: Windows 8 - Corrupt files/unable to fix/CBS files posted

I got rid of it. I didn't think we would need it any longer.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top