Page 2 of 3 FirstFirst 123 LastLast
  1.    28 Sep 2016 #11
    Join Date : Sep 2014
    DFW Area
    Posts : 431
    Windows 8&10

    If you want to see what the SFC is finding, you can run the command below in an Administrative Command prompt. Check the resulting text file near the bottom for any comments about "Cannot repair member file" and make note of the name of the file. The link explains the process.

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    https://support.microsoft.com/en-us/kb/929833
      My ComputerSystem Spec
  2.    28 Sep 2016 #12
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    Wow


    Ok... I screwed up. I wasn't paying attention and didn't realize a different person got in on this. You "both" prob. aren't going to be too happy with me, but I said H with it and installed anniversary. It actually made some things appear that weren't there before like in settings and searching for updates.

    Anyway.. still seems running fine. Should I start over?

    Dalchina - yes I ran chkdsk from admin command prompt. It said something about not being able to lock nfts drive or something like that? It then said do you want to run on next restart.. I hit yes but it didn't do anything. Than I manually restarted, but it didn't show or act like it was doing anything at all. However it apparently did it in the background because event viewer did show results.

    I'll read through the recommendations after work and try to get what you both want posted. Again, can't thank you enough for the help.

    Mac
    -------

    Ok.. Dalchina - In Admin Command prompt I ran the chkdsk c: /f It promoted to run on reboot. When reboot, it doesn't show a thing. I finally searched setting for I think boot options? Anyway, I found a number of boot options one of which was command prompt. I hit that one, it boot to command prompt and ran chkdks c: /f again. THAT TIME.... it ran through the full series. However at the end... it said. "Failed to transer logged message to the event log with status 50"

    That being said, it showed total disk space number of files/ indexes in use by system occupied by current log / available disk AND bad sectors. ZERO bad sectors. I don't know if thats what we were trying to find out. But thats where that is.

    Saltgrass...
    I went to the link and "TRIED" to get through and understand it all.. bud DAMN .. my head is spinning. I seriously have no clue how you guess can do this or make sense or follow the multitude of different angles/ options.. wait.. what??? : )

    I am going to run sfc in admin command promp... find the ares it "appears" to have an issue with and try to post that. Thanks Guys... really. Seriously... drinks on me. Where do I send the bottles?
    Last edited by Mac762; 29 Sep 2016 at 00:17. Reason: Udate Info
      My ComputerSystem Spec
  3.    28 Sep 2016 #13
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,367
    Win 10 Pro (1703)

    Chkdsk can't run if files are in use, which is why it runs on restart when you do this on your system drive. It is important to make sure your drive is ok before proceeding, as it's possible your initial failures were linked to some sort of disk/file corruption. It would have been much wiser to run that before upgrading.
      My ComputerSystem Spec
  4.    29 Sep 2016 #14
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    Hope This Helps


    OK People... think I found something. The previous info was from the most recent CBS and CBSPersist Files.. This Morning I searched those files for "Cannot" (As Recommended by SaltGrass) and found this in the CBS Persist file only: I separated sections by a line of hash marks.

    10d7 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:34:31, Info CSI 000010d8 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 19:34:31, Info CSI 000010d9 [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 19:34:31, Info CSI 000010da Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:34:31, Info CSI 000010db Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:34:31, Info CSI 000010dc [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted

    2016-09-24 19:59:03, Info CSI 00005d4c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d4d [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 19:59:03, Info CSI 00005d4e [SR] Repairing corrupted file [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell"\[l:26]"Windows PowerShell ISE.lnk" from store
    2016-09-24 19:59:03, Info CSI 00005d4f [SR] Repairing corrupted file [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell"\[l:32]"Windows PowerShell ISE (x86).lnk" from store
    2016-09-24 19:59:03, Info CSI 00005d50 [DIRSD OWNER WARNING] Directory [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell" is not owned but specifies SDDL in component Microsoft-Windows-PowerShell-ISE, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

    2016-09-24 19:59:03, Info CSI 00005d51@2016/9/25:01:59:03.486 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d52@2016/9/25:01:59:03.491 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d53 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d54 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 19:59:03, Info CSI 00005d55 [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 19:59:03, Info CSI 00005d56 Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d57 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d58 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted
    2016-09-24 19:59:03, Info CSI 00005d59@2016/9/25:01:59:03.538 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d5a [SR] Repair complete
    2016-09-24 19:59:03, Info CSI 00005d5b [SR] Committing transaction
    2016-09-24 19:59:03, Info CSI 00005d5c [SR] Cannot commit interactively, there are boot critical components being repaired
    2016-09-24 19:59:03, Info CSI 00005d5d [SR] Repairing 2 components
    2016-09-24 19:59:03, Info CSI 00005d5e [SR] Beginning Verify and Repair transaction
    2016-09-24 19:59:03, Info CSI 00005d5f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d60 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 19:59:03, Info CSI 00005d61 [SR] Repairing corrupted file [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell"\[l:26]"Windows PowerShell ISE.lnk" from store
    2016-09-24 19:59:03, Info CSI 00005d62 [SR] Repairing corrupted file [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell"\[l:32]"Windows PowerShell ISE (x86).lnk" from store
    2016-09-24 19:59:03, Info CSI 00005d63 [DIRSD OWNER WARNING] Directory [l:93 ml:94]"\??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell" is not owned but specifies SDDL in component Microsoft-Windows-PowerShell-ISE, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    -------------------------------------------
    2016-09-24 19:59:03, Info CSI 00005d64@2016/9/25:01:59:03.599 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d65@2016/9/25:01:59:03.604 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d66 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d67 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 19:59:03, Info CSI 00005d68 [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 19:59:03, Info CSI 00005d69 Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d6a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 19:59:03, Info CSI 00005d6b [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted
    2016-09-24 19:59:03, Info CSI 00005d6c@2016/9/25:01:59:03.651 Primitive installers committed for repair
    2016-09-24 19:59:03, Info CSI 00005d6d [SR] Repair complete
    2016-09-24 19:59:03, Info CSI 00005d6e Creating NT transaction (seq 2), objectname [6]"(null)"
    --------------------------------------------
    2016-09-24 20:57:17, Info CSI 000010dc Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 20:57:17, Info CSI 000010dd [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 20:57:20, Info CSI 000010de@2016/9/25:02:57:20.851 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010df@2016/9/25:02:57:20.868 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010e0@2016/9/25:02:57:20.899 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010e1@2016/9/25:02:57:20.915 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010e2@2016/9/25:02:57:20.931 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010e3@2016/9/25:02:57:20.964 Primitive installers committed for repair
    2016-09-24 20:57:20, Info CSI 000010e4@2016/9/25:02:57:20.968 Primitive installers committed for repair
    2016-09-24 20:57:21, Info CSI 000010e5@2016/9/25:02:57:21.00 Primitive installers committed for repair
    2016-09-24 20:57:21, Info CSI 000010e6@2016/9/25:02:57:21.015 Primitive installers committed for repair
    2016-09-24 20:57:21, Info CSI 000010e7@2016/9/25:02:57:21.031 Primitive installers committed for repair
    2016-09-24 20:57:21, Info CSI 000010e8@2016/9/25:02:57:21.047 Primitive installers committed for repair
    2016-09-24 20:57:21, Info CSI 000010e9 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 20:57:21, Info CSI 000010ea [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 20:57:21, Info CSI 000010eb [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 20:57:21, Info CSI 000010ec Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 20:57:21, Info CSI 000010ed Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 20:57:21, Info CSI 000010ee [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted
    --------------------------------------------
    Info CSI 00005cff Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d00 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 21:21:37, Info CSI 00005d01@2016/9/25:03:21:37.911 Primitive installers committed for repair
    2016-09-24 21:21:37, Info CSI 00005d02 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d03 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 21:21:37, Info CSI 00005d04 [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 21:21:37, Info CSI 00005d05 Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d06 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d07 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted
    2016-09-24 21:21:37, Info CSI 00005d08@2016/9/25:03:21:37.962 Primitive installers committed for repair
    2016-09-24 21:21:37, Info CSI 00005d09 [SR] Repair complete
    2016-09-24 21:21:37, Info CSI 00005d0a [SR] Committing transaction
    2016-09-24 21:21:37, Info CSI 00005d0b [SR] Cannot commit interactively, there are boot critical components being repaired
    2016-09-24 21:21:37, Info CSI 00005d0c [SR] Repairing 1 components
    2016-09-24 21:21:37, Info CSI 00005d0d [SR] Beginning Verify and Repair transaction
    2016-09-24 21:21:37, Info CSI 00005d0e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d0f [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 21:21:37, Info CSI 00005d10@2016/9/25:03:21:37.978 Primitive installers committed for repair
    2016-09-24 21:21:37, Info CSI 00005d11 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:37, Info CSI 00005d12 [SR] Cannot repair member file [l:11]"autochk.exe" of Microsoft-Windows-Autochk, version 10.0.10586.589, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-09-24 21:21:37, Info CSI 00005d13 [SR] This component was referenced by [l:80]"Package_1765_for_KB3185614~31bf3856ad364e35~amd64~~10.0.1.5.3185614-3561_neutral"
    2016-09-24 21:21:38, Info CSI 00005d14 Hashes for file member \??\C:\WINDOWS\System32\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:38, Info CSI 00005d15 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_10.0.10586.589_none_4ed86f4b20e293de\autochk.exe do not match actual file [l:11]"autochk.exe" :
    Found: {l:32 z3admfwq6kYDxbBSME5QzzjTsd0YMf9kga4P8azqeEE=} Expected: {l:32 1TzBaebn+KYmplIvCPnP4R0kZ3JQDm7vWaS19nhWpvo=}
    2016-09-24 21:21:38, Info CSI 00005d16 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\System32"\[l:11]"autochk.exe"; source file in store is also corrupted
    2016-09-24 21:21:38, Info CSI 00005d17@2016/9/25:03:21:38.031 Primitive installers committed for repair
    2016-09-24 21:21:38, Info CSI 00005d18 [SR] Repair complete
    2016-09-24 21:21:38, Info CSI 00005d19 Creating NT transaction (seq 2), objectname [6]"(null)"
    2016-09-24 21:21:38, Info CSI 00005d1a Created NT transaction (seq 2) result 0x00000000, handle @0x1130
    2016-09-24 21:21:38, Info CSI 00005d1b Poqexec successfully registered in [l:12 ml:13]"SetupExecute"
    2016-09-24 21:21:38, Info CSI 00005d1c@2016/9/25:03:21:38.093 Beginning NT transaction commit...
    2016-09-24 21:21:38, Info CSI 00005d1d@2016/9/25:03:21:38.389 CSI perf trace:
    CSIPERF:TXCOMMIT;313082
    2016-09-24 21:21:38, Info CBS TI: CBS has signaled that a reboot is required.
    2016-09-24 21:21:38, Info CBS Reboot mark set
    2016-09-24 21:23:45, Info CBS Trusted Installer successfully registered to be restarted for pre-shutdown
    2016-09-24 21:23:45, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2016-09-24 21:23:45, Info CBS TiWorker signaled for shutdown, going to exit.
    2016-09-24 21:23:45, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
    2016-09-24 21:23:45, Info CBS Ending the TiWorker main loop.
    2016-09-24 19:59:03, Info CSI 00005d6f Created NT transaction (seq 2) result 0x00000000, handle @0xdec
    2016-09-24 19:59:03, Info CSI 00005d70 Poqexec successfully registered in [l:12 ml:13]"SetupExecute"
    2016-09-24 19:59:03, Info CSI 00005d71@2016/9/25:01:59:03.722 Beginning NT transaction commit...
    2016-09-24 19:59:04, Info CSI 00005d72@2016/9/25:01:59:04.08 CSI perf trace:
    CSIPERF:TXCOMMIT;292612
    2016-09-24 19:59:04, Info CBS TI: CBS has signaled that a reboot is required.
    2016-09-24 19:59:04, Info CBS Reboot mark set
    2016-09-24 20:01:10, Info CBS Trusted Installer successfully registered to be restarted for pre-shutdown
    2016-09-24 20:01:10, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2016-09-24 20:01:10, Info CBS TiWorker signaled for shutdown, going to exit.
    ------------------------------

    HOPE this helps or means something.
    Last edited by Mac762; 29 Sep 2016 at 08:40. Reason: Modifiy Ending
      My ComputerSystem Spec
  5.    29 Sep 2016 #15
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,367
    Win 10 Pro (1703)

    Hi, as I understand it you have
    - upgraded to the anniversary edition
    - run chkdsk
    I don't believe we have a real result for that.
    - run sfc /scannow
    This appears to show failures.

    It is not expected that SFC /SCANNOW should fail immediately after you have done an upgrade as everything is new.

    As you are unable to get the chkdsk result, let's try something else.


    1. Download install and run Crystal Diskinfo and post the result- it should look like this:
    Click image for larger version. 

Name:	Snap 2016-09-29 at 22.16.08.jpg 
Views:	2 
Size:	103.8 KB 
ID:	103674

    2. Download and run Macrorit Diskscanner and scan your disk. Please post the result. Thanks.
      My ComputerSystem Spec
  6.    29 Sep 2016 #16
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    Lets see if this file attaches


    Here is Crystal Scan.

    Norton says something about the msi on the other scan program you recommended. So... opted to skip that one.

    Again, sure you don't want me to send you a bottle? What don't drink? If not.... you've got a lot to learn about messing up your life....
    Attached Thumbnails Attached Thumbnails Crystal Scan.JPG  
      My ComputerSystem Spec
  7.    29 Sep 2016 #17
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    CBS Errors


    Actually... that previous were the errors. Sort of...

    Wrong Date Run...

    Following is the correct date run errors.
    -----------------
    016-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 07:28:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 07:28:13, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-29 07:28:13, Info CBS Session: 30546517_1416188081 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-29 07:28:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 07:28:13, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    ------------------------
    2016-09-29 19:57:56, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 19:57:56, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2016-09-29 19:57:56, Info CBS Session: 30546622_268016309 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2016-09-29 19:57:56, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2016-09-29 19:57:56, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    ------------------------
    2016-09-29 20:04:00, Info DPX Extraction of file: update.ses failed because it is not present in the container (\\?\C:\WINDOWS\SoftwareDistribution\Download\84ab2cdc1d449ef2f2e073c078afd2b1\Windows10.0-KB3194496-x64-EXPRESS.cab).
    2016-09-29 20:04:00, Info DPX DpxException hr=0x80070002 code=0x020109
    2016-09-29 20:04:00, Info CBS Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    -----------------------
    2016-09-29 20:13:54, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2016-09-29 20:13:54, Info CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2016-09-29 20:13:54, Info CBS WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2016-09-29 20:13:54, Info CBS Reboot mark cleared
    -------------------

    Again, honestly can't thank you enough for all the time and effort you have put into this. Please let me know if there's anyway I can help or repay you.
      My ComputerSystem Spec
  8.    30 Sep 2016 #18
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    OK... heres the latest.

    Went to this websites "DISM - Repair windows 10 image page.

    Dism /Online /Cleanup-Image /CheckHealth - Went perfect
    Dism /Online /Cleanup-Image /ScanHealth - Again.. perfect.
    Dism /Online /Cleanup-Image /RestoreHealth - Error

    Click image for larger version. 

Name:	DISM Error at Step 5.JPG 
Views:	15 
Size:	31.5 KB 
ID:	103741

    The following from the DISM log.

    2016-09-28 07:27:57, Warning DISM DISM Provider Store: PID=7868 TID=10796 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    [7868] [0x8007007b] FIOReadFileIntoBuffer1250): The filename, directory name, or volume label syntax is incorrect.
    [7868] [0xc142011c] UnmarshallImageHandleFromDirectory793)
    [7868] [0xc142011c] WIMGetMountedImageHandle3047)

    The above error occurred appox. 6 times throughout the report with a number of other 1 line errors.

    Any of this make sense?

    Let me ask you, if I were to go out and buy a copy of Windows 10... That would probably resolve all the issues. Would that thought be accurate?

    Any help is appreciated. Little Discouraged.

    Thanks for any help.
      My ComputerSystem Spec
  9.    30 Sep 2016 #19
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,367
    Win 10 Pro (1703)

    Hi, DISM failing with 1726 & RPC call is relatively common.

    I suggest you do a clean boot
    Clean Boot - Perform in Windows 10 to Troubleshoot Software Conflicts - Windows 10 Forums
    part 1 only

    then retry the DISM command from an admin command prompt

    There's no need to buy Win 10 as you've installed it- you can freely download a copy. Only if you wanted to upgrade from Home to Pro, or bought a new barebones PC (no OS). (I bought a Win 8 Pro license for $40 when they had the early offers, and used that on my new PC)

    If you have everything backed up, and are willing to clean install, that may turn out to be quicker, if you only have a few programs to install. (For me, it's days...manually..but I don't normally do it manually)
    Last edited by dalchina; 30 Sep 2016 at 03:48.
      My ComputerSystem Spec
  10.    01 Oct 2016 #20
    Join Date : Sep 2016
    SLC Utah
    Posts : 16
    Windows 10
    Thread Starter

    Maybe Maybe


    Quote Originally Posted by dalchina View Post
    Hi, DISM failing with 1726 & RPC call is relatively common.

    I suggest you do a clean boot
    Clean Boot - Perform in Windows 10 to Troubleshoot Software Conflicts - Windows 10 Forums
    part 1 only

    then retry the DISM command from an admin command prompt

    There's no need to buy Win 10 as you've installed it- you can freely download a copy. Only if you wanted to upgrade from Home to Pro, or bought a new barebones PC (no OS). (I bought a Win 8 Pro license for $40 when they had the early offers, and used that on my new PC)

    If you have everything backed up, and are willing to clean install, that may turn out to be quicker, if you only have a few programs to install. (For me, it's days...manually..but I don't normally do it manually)
    I'd prefer not too, would be a pain. Ok.. I give it a few more shots. Thank You for helping.

    Maybe Maybe..., : )
    You might be onto something here. I just ran the Dism /Online /Cleanup-Image /CheckHealth and last time it showed as on the repair tool instructions "No Corruption Detected".

    THIS time.. it says "The component store is repairable". Moving onto next step. Keeping fingers crossed, pouring scotch : )

    Oh Be Still My Heart....
    Dism /Online /Cleanup-Image /ScanHealth ... Last Time.... No Issues.
    This Time indicates "The component Store is Repairable".

    Movin' On....
    (Dism /Online /Cleanup-Image /RestoreHealth)...
    {Deployment Image Servicing and Management tool}.......................

    Repair Tool Instructions indicate this can take 10-15 minutes up to a few "Hours"...

    May need more Scotch... hahahaha (Damn I crack myself up).

    OOoooooo : ( Sooooo close. 93.7%
    Error 1726
    The remote procedure call failed. Created DISM log.

    BuuuuuaaaaaMMMmmmmErrrrrrrrr
    Last edited by Mac762; 01 Oct 2016 at 02:37.
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
Solved New laptop, trouble xferring files/settings from working Win7 laptop
I recently purchased an ASUS A555DG-EHFX to take over for my wife's Win7 ASUS K50IJ-BBZ5 (both are 64-bit). Obviously getting Windows 10 up and running out of the box was a breeze. Configuring WLAN connectivity was also easy, even though I have...
Installation and Upgrade
Laptop boots into LOGO screen then restart, then again reboots fine.
Hi, I have been facing with this strange issue lately. On pressing the power button the laptop powers up with the lenovo logo then it again goes blank, then it again comes with the same lenovo screen and then boots fine directly into the welcome...
BSOD Crashes and Debugging
Solved Homegroup, was fine now unable to access any other PC or Laptop
Had HomeGroup running fine until yesterday. My PC on Win10 could access our Laptop on Win 8.1 and the Laptop access my PC. Today both are 'unavailable' to the other :(. I tried leaving the HomeGroup on both machines then created a new HG on My PC,...
Network and Sharing
Favorites and Bar don't work on one Laptop but work fine on Desktop
Here is info from both computers that might assist in troubleshooting my problem. Trying to Import from IE shows "couldn't import favorites." In both of the following instances identical lists of my favorites and contents of Favorites Bar appear...
Browsers and Email
Stuck at "Attempting Repairs" on second laptop, first one worked fine
I'm at my wits end. I took advantage of the Windows 10 update on my Samsung laptop several weeks ago, and everything went fine. I've been using it daily with no issues. So, when my wife asked if she should allow the update on her (identical)...
General Support
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 19:35.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums