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

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.

 

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:




2. Download and run Macrorit Diskscanner and scan your disk. Please post the result. Thanks.

 

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.... *sarc

 

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.

 

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

*Sad1250): The filename, directory name, or volume label syntax is incorrect.
[7868] [0xc142011c] UnmarshallImageHandleFromDirectory*Sad793)
[7868] [0xc142011c] WIMGetMountedImageHandle*Sad3047)

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.

 

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

 

You could try the same in Safe Mode.
(I have 3 demi-johns bubbling away- many years since we did that... don't think I'll graduate to a home still tho').

If that fails, then you can try an in-place upgrade repair.. I've done it several times.
An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.

For this you need an installation medium with the same base build as you have installed, and x64 if you have a 64 bits OS, else x86 (32 bits).

Recommendation:
Before you perform the following major repair procedure, do create a disk image (see below).

Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums
- this includes a link from which you can obtain Windows 10 iso file (" download a Windows 10 ISO"), or create a bootable medium.

I would recommend creating the bootable medium, as this can be used
- for any future in-place upgrade repair install
- to boot from and use its recovery options should Windows become unbootable.
- to clean install Windows

This will refresh Windows, after the manner of a Windows installation.
- all/most associations will be unchanged
- all your programs will be left installed
- no personal data should be affected
- you will lose any custom fonts
- you will lose any customised system icons
- you may need to re-establish your Wi-Fi connection
- you will need to redo Windows updates subsequent to the build you have used for the repair install
- Windows.old will be created
- system restore will be turned off- you should turn it on again and I recommend you manually schedule a daily restore point.
- you will need to redo any language downloads including the display language if you changed that)
- inactive title bar colouring (if used) will be reset to default
- if Qttabbar is installed, you need to re-enable it in explorer (Options, check Qttabbar)
This is one of the better features of Win10: as each major build comes out, that's your updated reference build, and as updates are mostly cumulative, there will be few to do.


Please consider using disk imaging regularly. It's a brilliant way to
- preserve your system (and your sanity)
- back up your data
- restore your system to a previously working state in a relatively short time

Recommended: Macrium Reflect (free/commercial) + boot disk/device + large enough external storage medium.

 

OK... I'll give it a shot.

You said An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.

For this you need an installation medium with the same base build as you have installed, and x64 if you have a 64 bits OS, else x86 (32 bits).

What do you mean not those where the settings are not changed by the procedure.

Anyway.. I'm going to proceed.

Well... actually I'm "Not" going to proceed. The link instructions indicate you have to turn off "secure boot". I don't have "UEFI Setting" option on the "trouble shooting" "advanced options" screen. I searched and can't find anything about how to turn off "secure boot" on my machine.

Do you suggest I go back to DISM where before we failed at end of step 4. I believe steps 5 and 6 go into image recovery. Hell I don't know. I made an image of disk with the "Macrium Reflect" program. I also made a cd that does boot to that "Reflect" program.

Just read that apparently that is something from Windows 8 and up. I upgraded from Win7. A little more reading mentions something about kernals or whatever*Confused

Kinda Lost at this Point?

Clean Install option.... Since I now have an image file from "Reflect"... is that the same as a backup? Can I restore programs from that if I did clean install?

I just don't know what to do. Feeling like I just created a boat anchor out of the machine? Maybe it's time for a new laptop? Which sucks, but not sure what to do.

 

You know, maybe I'm getting way off my original question. My computer seems to run fine other than the errors I get from SFC. Maybe those errors are just going to be "Ghosts in the Machine"?

Anyway, any help of suggestions would be most appreciated. Should I start a "New" forum entry? God I just don't know what the heck to do.

 

To eliminate the problems you've found requires one of the following:
1. a build upgrade (e.g. 1511 to 1607
2. an in-place upgrade repair install
3. a clean install

Of those I've used (2) successfully 3 times I think, and of course have done the others too.

Your laptop was first sold with Win 7, so you don't have UEFI at all - but a traditional BIOS.
That means you won't have secure boot.

So you should be able to do an in-place upgrade repair.

I wonder if most tutorials are now based UEFI only where they mention it, and don't show the legacy BIOS case...

 

I have gone through my Bios Settings.. "secure boot" is not one of the options. From other things I've read, secure boot is a Windows 8 and up thing?

How do I boot from a windows 10 Disk. Or.. how do i "create" and windows 10 disk?

Please ... I'm desperate at this point.

I think I found answer to my above question at Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10 on a different PC (click to show more or less information)

I guess thats correct?

 

I've explained the issue about secure boot above- see amended post. Yours is a legacy BIOS.

Win 10 iso / bootable flash drive:
Windows 10 ISO Download - Windows 10 Forums
For a DVD just burn the iso to a DVD.

For an in-place upgrade repair: log in as normal, insert DVD, run setup.exe from the DVD.
Follow the tutorial.

Good luck!

 

Yes.. everything I've seen talks about UEFI. So you're saying that using the upgrade repair "should in theory" work.. just disregard the disable secure comment in the instructions?

Ok thanks for all your help.