SFC Unable to fix some files by Laptop seems to run fine.

Page 1 of 3 123 LastLast

  1. Posts : 16
    Windows 10
       #1

    SFC Unable to fix some files by Laptop seems to run fine.


    Hi People,

    I'm new so forgive me if this is in the wrong place. I have an older Toshiba laptop that I upgraded to windows 10 via the free upgrade offer. I know enough just to be dangerous and so just for the heck of it, decided to run sfc just to see how things checked out.

    It did find some problems it was unable to fix and created a CBS Log. However, the laptop seems to run fine other than being a little slow. I basically have chaulked that up to being an old laptop with limited ram.

    I did try and run DICM and came up with an error 87 in think on the 3rd step.

    Anyway, like I said, Laptop basically seems to do what I want, so should I be concerned about the files SFC can't fix?

    In other words, should I pursue the resolution? Is the fact if found errors an indication things are heading down the can?

    Any Help is Much Appreciated.

    Thanks People

    Mac
      My Computer


  2. Posts : 42,965
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, that certainly does happen, and I can't give you a good reason as to why it happens. SFC compares your system files with a stored backup in Winsxs and tries to replace those it finds are damaged or incorrect.
    Sometimes permissions errors arise, or files are not found. You can look thru your CBS log, but if you also had errors running DISM commands (which is quite common too) there is another means of (probably) correcting this.

    First try this to check your file system's integrity and to some extent your disk:
    From an admin command prompt
    [Windows key + X, click command prompt (admin)]
    chkdsk C: /F
    Your PC will need to restart.
    Make sure the result is clear or fixed- else do not proceed.
    Post back the result, which you can get after a restart as follows:
    How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

    What is your current build? (Windows key + R, winver). Pro or Home?
      My Computers


  3. Posts : 16
    Windows 10
    Thread Starter
       #3

    Thanks Very much for trying to help. Very much appreciated.

    Ran chkdsk C: /F

    Reviewed Event Viewer however after running through the list I found NO Wininit Entries. I found lots of win listener adapter /windows error reporting/ winlogon/ WMI one winsrv. But no wininit.

    I did find a "bunch" of wininit under "system" in the windows logs section. But nothing in the "Application" section of the windows logs.

    My Build info is : Windows 10 Version 1511 (OS Build 10586.589)

    Any other suggestions?

    (Damn... how in the world do you know all this stuff?)

    Anyway... thanks very much for any help already provided and any further recommendations.

    Mac
      My Computer


  4. Posts : 42,965
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    Hi, could you post the result of chkdsk please? I need to know your disk is ok before proceeding.

    Noting you are on 1511, is there any reason you haven't applied the anniversary update yet - do you have Windows update enabled?
      My Computers


  5. Posts : 16
    Windows 10
    Thread Starter
       #5

    CbsPersist Data and Cbs data


    My apologies... I don't know how to post that. I ran the (Chkdsk C: /F) I followed the info on the link you provided ( In that link Post back the result, which you can get after a restart as follows: How do I see the results of a CHKDSK that ran on boot? - Ask Leo!) In that link it shows how to view results using "event viewer" where it recommends you look for an entry in (Application / Logs I think?) with source of wininit.

    As noted, I could not find that entry. But otherwise, I don't know how to post the results from "event viewer"? Sorry, I wish I knew more.

    As far as updates, I did not realize they were not updating. I checked and it does indicate there are updates available, however now I'm not sure if I should do that now or wait for further instruction?

    I really do appreciate the help though. I could always send you a bottle of scotch? : )
    ------------

    ok.. .REALLY confused. Saltgrass... went back that link.. ran sfc /scannow from the comand prompt in the new boot option area I found. This time instead of running it said it could run on and that site it said if that happens.. run in safe mode. Huh? Thought I was already there SOOOOO... Rebooted, went to windows start menu... admin command prompt ... sfc /scannow (from C:\windows\system>) this time... I did not prompt to run at reboot. It just started. So I'm totally confused... may "I" need more scotch or MAYBE I should just go buy a new copy of Win 10... format C: and reinstall?

    Thoughts or do any of you still think this is salvageable?

    OH.... Its currently at 38% I gotta hit the rack. I'll post what it says tomorrow and I guess we'll go from there. Thanks People.... you all really are quite amazing at this stuff.

    Oh Hell.... It's chkdsk that prompts for run at reboot not sfc... man my head is swimming. Again... I'll post what "sfc" say tomorrow.

    ---------------

    Here is top section of CbsPersist:
    2016-09-28 00:11:15, Info CBS TI: --- Initializing Trusted Installer ---
    2016-09-28 00:11:15, Info CBS TI: Last boot time: 2016-09-27 23:51:19.492
    2016-09-28 00:11:15, Info CBS Starting TrustedInstaller initialization.
    2016-09-28 00:11:15, Info CBS Ending TrustedInstaller initialization.
    2016-09-28 00:11:15, Info CBS Starting the TrustedInstaller main loop.
    2016-09-28 00:11:15, Info CBS TrustedInstaller service starts successfully.
    2016-09-28 00:11:15, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2016-09-28 00:11:15, Info CBS Startup processing thread terminated normally
    2016-09-28 00:11:15, Info CBS TI: Startup Processing completes, release startup processing lock.
    2016-09-28 00:11:15, Info CBS Starting TiWorker initialization.
    2016-09-28 00:11:15, Info CBS Ending TiWorker initialization.
    2016-09-28 00:11:15, Info CBS Starting the TiWorker main loop.
    2016-09-28 00:11:15, Info CBS TiWorker starts successfully.
    2016-09-28 00:11:15, Info CBS Universal Time is: 2016-09-28 06:11:15.347
    2016-09-28 00:11:15, Info CBS Loaded Servicing Stack v10.0.14393.0 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb\cbscore.dll
    2016-09-28 00:11:15, Info CSI 00000001@2016/9/28:06:11:15.347 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fffcf596c49 @0x7fffcf8d55bb @0x7fffcf8d6372 @0x7ff6d81e2d9d @0x7ff6d81e35e0 @0x7fffec1e7de3)
    2016-09-28 00:11:15, Info CBS NonStart: Set pending store consistency check.
    2016-09-28 00:11:15, Info CBS Session: 30546255_513353714 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-28 00:11:15, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-28 00:11:15, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-28 00:11:15, Info CBS Session: 30546255_513353715 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-28 00:11:15, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-28 00:11:15, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-28 00:11:58, Info CBS WU creates the package, AppIDevice Driver Retrieval Client, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201
    After this it all seems to be ok?

    CBS Data:
    2016-09-29 00:10:23, Info CBS TI: --- Initializing Trusted Installer ---
    2016-09-29 00:10:23, Info CBS TI: Last boot time: 2016-09-29 00:05:13.492
    2016-09-29 00:10:23, Info CBS Starting TrustedInstaller initialization.
    2016-09-29 00:10:23, Info CBS Ending TrustedInstaller initialization.
    2016-09-29 00:10:23, Info CBS Starting the TrustedInstaller main loop.
    2016-09-29 00:10:23, Info CBS TrustedInstaller service starts successfully.
    2016-09-29 00:10:23, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2016-09-29 00:10:23, Info CBS Startup processing thread terminated normally
    2016-09-29 00:10:23, Info CBS TI: Startup Processing completes, release startup processing lock.
    2016-09-29 00:10:23, Info CBS Starting TiWorker initialization.
    2016-09-29 00:10:23, Info CBS Ending TiWorker initialization.
    2016-09-29 00:10:23, Info CBS Starting the TiWorker main loop.
    2016-09-29 00:10:23, Info CBS TiWorker starts successfully.
    2016-09-29 00:10:23, Info CBS Universal Time is: 2016-09-29 06:10:23.369
    2016-09-29 00:10:23, Info CBS Loaded Servicing Stack v10.0.14393.82 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.82_none_5be7b69702339d1d\cbscore.dll
    2016-09-29 00:10:23, Info CSI 00000001@2016/9/29:06:10:23.385 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fff60236c49 @0x7fff606055bb @0x7fff60606372 @0x7ff634c82d9d @0x7ff634c835e0 @0x7fff8cc27de3)
    2016-09-29 00:10:23, Info CBS NonStart: Set pending store consistency check.
    2016-09-29 00:10:23, Info CBS Session: 30546456_705152133 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-29 00:10:23, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 00:10:23, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-29 00:10:23, Info CBS Session: 30546456_705152134 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-29 00:10:23, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 00:10:23, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-29 00:10:26, Info CBS WU creates the package, AppID:UpdateOrchestrator, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201

    After This it all seems ok???

    Good night and thank you.
    Last edited by Mac762; 29 Sep 2016 at 01:18. Reason: I stayed Up
      My Computer


  6. Posts : 16
    Windows 10
    Thread Starter
       #6

    Oh.. it looks like the only update available is "• Microsoft Office File Validation Add-in."

    Not seeing any other update options.
      My Computer


  7. Posts : 16
    Windows 10
    Thread Starter
       #7

    It looks like it "May" have created another CBS file? Is that what I should post? If so, do I post the entire thing? It's pretty long.
      My Computer


  8. Posts : 16
    Windows 10
    Thread Starter
       #8

    Ok... just verified. I ran "chkdsk C: /f" from administer command prompt and it did create another CBS file. I'm guess that the data you want, however I don't know how to post it? I doubt you want me to cut and past the entire thing?
      My Computer


  9. Posts : 31,630
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #9

    Mac762 said:
    I'm guess that the data you want, however I don't know how to post it?
    The FAQ explains how to add attachments to a post.
    https://www.tenforums.com/faq.php?faq...b3_attachments
      My Computers


  10. Posts : 42,965
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #10

    Hi chkdsk doesn't create cbs.log files.
    sfc /scannow creates those.

    The article I posted:
    How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
    is full of pictures as to how to find the results- there's even an audio.

    There it gives the shortest report you're likely to see:


    Did you actually run chkdsk from an admin prompt - and did you then restart your PC to allow it to run as it should have prompted you?

    If for some reason you're unable to do this (many have), then another way could be to create a bootable disk:
    Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
    and run chkdsk from that. That would take a lot more time to do though, so I suggest retrying what I described.

    Rather than create a sequence of separate posts, you can Edit Post and amend or add to a post, making it easier to read.

    (My father would have appreciated the scotch :))
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:20.
Find Us




Windows 10 Forums