Messages

1

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 18, 2017, 02:58:46 pm »

Thanks for the suggestions. Before I tried them, I've been searching for solutions and I found this:https://www.youtube.com/watch?v=uL_AvTLnchU  which describes what we've been trying. At about 1/2 way through the short video you can see in the offboot CMD he's starting with D:, not X: so I tried that and it still didn't work out. He also ran D:>dir which gave him a list of several files on his disk. I did they same and just got one file. However, I checked the disk via local Windows Explorer and it's got all the files and folders it's supposed to have and 4.1G full. Weird, although maybe it has to do with his Win 7, vs my Win 10?

I tried your latest commands and I got "Success" for the first one and " ...was started successfully." for the second one. I tried them in local Windows C: CMD and sfc /scannow resulted in "...unable to fix some ...." as usual. Also tried local D:, then off boot disk in both x: and d: . There the first two were "successful" but then the sfc /scannow resulted with "...could not start the repair service". Also tried the " sfc scannow /offbootdir=D:\ /offwindir=D:\windows in c:, d: and x: and all resulted with "... could not start repair service."

I have a suggestion. The CBS log I posted a few messages ago listed the 4 corrupted files I'm trying to replace, correct? These:
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b
Repair failed: Missing replacement manifest.
(p)   CSI Payload Corrupt         amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.10586.310_none_a5154d543e444fc6\clr.dll

Can they be manually and individually replaced with healthy ones? I recently read but cannot find now, an Microsoft post on how to do this. It involves having a separate PC and copying the needed files from it, then transferring them to the problem PC. Is this possible? I also found this:http://www.askvg.com/right-click-replacethis-free-portable-utility-to-replace-system-files-in-windows-7/ which is related, as well as this:http://www.technixupdate.com/delete-replace-system-files-in-windows/ . It's the same app but if it works for Win 7 with the same Trusted Installer feature in Win 10, would it do what I need?

2

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 17, 2017, 02:15:10 pm »

I've been following your last instructions relative to your message #3. The disk is in D: and is booted to D: and I'm at the CMD window and have entered "bcdedit_|find_"osdevice" and "sfc_/scannow_/offbootdir=D:\_/offwindir=D:\Windows" without the quotes or underscores. I'm getting "Windows Resource Protection could not start the repair service."

The prompt shows "x:\sources>", not the usual C: . Am I supposed to change the X: to D:, C: or anything else? If so, how?

3

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 16, 2017, 02:07:06 pm »

Ok. I think I understand now. So what I do exactly is put the disk in drive D: then reboot and it will first boot to D: and therefore access the disk and ask if I want to do a repair or install. At that point I do nothing with the disk. I then go to Start>Commmand Prompt (Admin) and enter "sfc_/scannow_/offbootdir=D:\_/offwindir=D:\Windows " in the CMD window and let that run until completion. Correct?

If not, what are the correct steps.

4

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 16, 2017, 12:07:47 pm »

Whaaaat??? LOL, I'm so confused now ...

Are you now saying I should forget about running the "sfc_/scannow_/offbootdir=D:\_/offwindir=D:\Windows " command in the CMD window with the disk in the D: drive and instead just set the BIOS to boot from the DVD first (that is already my default setting) and just run the repair option from the disk?

5

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 16, 2017, 08:11:30 am »

To double check with you before I do that:

1- I insert my disk with Windows 10 Repair Install with an In-Place Upgrade (downloaded Sept. 14, 2016) into my D: disk drive.

2- Should I be in Safe Mode?

3- Do I need to turn off Windows Defender?

4- In CMD (Administrator) I enter "sfc_/scannow_/offbootdir=D:\_/offwindir=D:\Windows" where D: is where the disk is.

5- Just let it run until completion on its own, then post the resulting CBS log?

6

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 15, 2017, 05:51:31 pm »

I did as you said while in regular mode and while running "...restorehealth", at about 20% the system crashed and rebooted. So I sent into safe mode with networking, with FF browser open and at the microsoft page.

After  "...checkhealth" it said "is repairable"
After "...componentcleanup" it said "100%. Operation completed successfully"
After "...restorehealth" it said "Error 0x800f0906 The source files could not be downloaded"
After "sfc /scannow" it said "...found corrupt files but unable to fix some ..."
After "findstr..." it said "cannot open ... sfcdetails.txt"

I went to the CBS.log file and here it its contents:

2017-02-15 17:29:20, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-15 17:29:20, Info                  CBS    TI: Last boot time: 2017-02-15 17:23:56.499
2017-02-15 17:29:20, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-15 17:29:20, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-15 17:29:20, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-15 17:29:20, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-15 17:29:20, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-15 17:29:20, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:29:20, Info                  CBS    Startup processing thread terminated normally
2017-02-15 17:29:20, Info                  CBS    Starting TiWorker initialization.
2017-02-15 17:29:20, Info                  CBS    Ending TiWorker initialization.
2017-02-15 17:29:20, Info                  CBS    Starting the TiWorker main loop.
2017-02-15 17:29:20, Info                  CBS    TiWorker starts successfully.
2017-02-15 17:29:20, Info                  CBS    Universal Time is: 2017-02-15 22:29:20.838
2017-02-15 17:29:20, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-15 17:29:20, Info                  CSI    00000001@2017/2/15:22:29:20.963 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe4b4a46d9 @0x7ffe4b8a2150 @0x7ffe4b8a1d2b @0x7ff641272ee0 @0x7ff6412738e1 @0x7ffe6231d533)
2017-02-15 17:29:21, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:29:21, Info                  CBS    Session: 30574554_4090945686 initialized by client DISM Package Manager Provider, external staging directory: (null)
2017-02-15 17:31:21, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2017-02-15 17:31:21, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:31:21, Info                  CBS    Ending the TiWorker main loop.
2017-02-15 17:31:21, Info                  CBS    Starting TiWorker finalization.
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: SrUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-02-15 17:31:21, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-02-15 17:31:21, Info                  CBS    Ending TiWorker finalization.
2017-02-15 17:31:21, Info                  CBS    Ending the TrustedInstaller main loop.
2017-02-15 17:31:21, Info                  CBS    Starting TrustedInstaller finalization.
2017-02-15 17:31:21, Info                  CBS    Ending TrustedInstaller finalization.
2017-02-15 17:33:03, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-15 17:33:03, Info                  CBS    TI: Last boot time: 2017-02-15 17:23:56.499
2017-02-15 17:33:03, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-15 17:33:03, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-15 17:33:03, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-15 17:33:03, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-15 17:33:03, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-15 17:33:03, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:33:03, Info                  CBS    Startup processing thread terminated normally
2017-02-15 17:33:03, Info                  CBS    Starting TiWorker initialization.
2017-02-15 17:33:03, Info                  CBS    Ending TiWorker initialization.
2017-02-15 17:33:03, Info                  CBS    Starting the TiWorker main loop.
2017-02-15 17:33:03, Info                  CBS    TiWorker starts successfully.
2017-02-15 17:33:03, Info                  CBS    Universal Time is: 2017-02-15 22:33:03.628
2017-02-15 17:33:03, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-15 17:33:03, Info                  CSI    00000001@2017/2/15:22:33:03.628 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe4b9346d9 @0x7ffe4bce2150 @0x7ffe4bce1d2b @0x7ff641272ee0 @0x7ff6412738e1 @0x7ffe6231d533)
2017-02-15 17:33:03, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:33:03, Info                  CBS    Session: 30574555_2021536382 initialized by client DISM Package Manager Provider, external staging directory: (null)
2017-02-15 17:33:03, Info                  CBS    No call is made on InitiateChanges, Synchronous Cleanup only.
2017-02-15 17:33:04, Info                  CSI    00000002 CSI Store 2354521967504 (0x0000022434720b90) initialized
2017-02-15 17:33:04, Info                  CBS    Maint: processing started.  Client: DISM Package Manager Provider, Session: 30574555_2021536382
2017-02-15 17:33:04, Info                  CBS    Maint: launch type: StartComponentCleanup
2017-02-15 17:33:04, Info                  CBS    Reboot mark set
2017-02-15 17:33:04, Info                  CBS    Winlogon: Registering for CreateSession notifications
2017-02-15 17:33:04, Info                  CBS    Winlogon: Loading SysNotify DLL
2017-02-15 17:33:04, Info                  CBS    Winlogon: Starting notify server
2017-02-15 17:33:04, Info                  CBS    Maint: begin archive logs
2017-02-15 17:33:13, Info                  CBS    Archived backup log: C:\WINDOWS\Logs\CBS\CbsPersist_20170215222920.cab.
2017-02-15 17:33:13, Info                  CBS    CAB compressed log file: C:\WINDOWS\Logs\CBS\CbsPersist_20170215222920.log
2017-02-15 17:33:13, Info                  CBS    Maint: end archive logs, archive time so far: 8 seconds
2017-02-15 17:33:13, Info                  CBS    Maint: begin scavenge
2017-02-15 17:33:13, Info                  CBS    Scavenge: Start CSI
2017-02-15 17:33:13, Info                  CSI    00000003@2017/2/15:22:33:13.723 CSI Transaction @0x22434732a30 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id [26]"TI6.30574555_2021536382:1/"

2017-02-15 17:33:13, Info                  CBS    Scavenge: Begin CSI Store
2017-02-15 17:33:14, Info                  CSI    00000004 Performing 1 operations as follows:
  (0)  Scavenge: flags: 00000037
2017-02-15 17:33:14, Info                  CSI    00000005 Scavenge: Begin processing lists
2017-02-15 17:33:14, Info                  CSI    00000006 Scavenge: Setting maximum delta file size limit to 32 MB.

2017-02-15 17:33:14, Info                  CSI    00000007 Scavenge: Begin planning
2017-02-15 17:34:28, Info                  CSI    00000008 Manifest hash for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236" does not match expected value.
 Expected:{l:32 b:ee6ffcf3b8ca47bb0f1ce56525986efc3eb8fdba5b87253e84d4756272188eaa}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:34:28, Info                  CSI    00000009 Looking for manifest in Backup Dir...
2017-02-15 17:34:28, Error                 CSI    0000000a (F) Unable to load manifest for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236"[gle=0x80004005]
2017-02-15 17:34:28, Error                 CSI    0000000b@2017/2/15:22:34:28.194 (F) base\wcp\componentstore\storelayout.cpp(2671): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource [122]"\winsxs\manifests\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236.manifest"[gle=0x80004005]
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20170215222920.cab to WER report.
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20170215152022.cab to WER report.
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20170215002254.cab to WER report.
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20170214145016.cab to WER report.
2017-02-15 17:34:28, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20170212162157.cab to WER report.
2017-02-15 17:34:28, Info                  CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-02-15 17:34:28, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-02-15 17:34:28, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-02-15 17:34:28, Info                  CSI    0000000c Failed to process component: [l:95]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236", move to the next one.
2017-02-15 17:35:38, Info                  CSI    0000000d Scavenge: Planning Complete.
The following actions will be performed:
    Regeneration Candidates: 0
    Removal Candidates: 2305
    Superseded/LDR (Delta Compression) Candidates: 0
    Null-Delta Compression Candidates:
        Mutable file Candidates: 0
        Boot-Recovery Candidates: 0
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 0

2017-02-15 17:35:38, Info                  CSI    0000000e Creating NT transaction (seq 1), objectname [6]"(null)"
2017-02-15 17:35:38, Info                  CSI    0000000f Created NT transaction (seq 1) result 0x00000000, handle @0x3b4
2017-02-15 17:35:43, Info                  CSI    00000010@2017/2/15:22:35:43.760 Beginning NT transaction commit...
2017-02-15 17:35:44, Info                  CSI    00000011@2017/2/15:22:35:44.182 CSI perf trace:
CSIPERF:TXCOMMIT;440283
2017-02-15 17:35:44, Info                  CSI    00000012 Creating NT transaction (seq 2), objectname [6]"(null)"
2017-02-15 17:35:44, Info                  CSI    00000013 Created NT transaction (seq 2) result 0x00000000, handle @0x3b4
2017-02-15 17:35:49, Info                  CSI    00000014@2017/2/15:22:35:49.244 Beginning NT transaction commit...
2017-02-15 17:35:50, Info                  CSI    00000015@2017/2/15:22:35:50.260 CSI perf trace:
CSIPERF:TXCOMMIT;1042989
2017-02-15 17:35:50, Info                  CSI    00000016 Creating NT transaction (seq 3), objectname [6]"(null)"
2017-02-15 17:35:50, Info                  CSI    00000017 Created NT transaction (seq 3) result 0x00000000, handle @0x3b4
2017-02-15 17:35:54, Info                  CSI    00000018@2017/2/15:22:35:54.620 Beginning NT transaction commit...
2017-02-15 17:35:55, Info                  CSI    00000019@2017/2/15:22:35:55.995 CSI perf trace:
CSIPERF:TXCOMMIT;1424937
2017-02-15 17:36:11, Info                  CSI    0000001a@2017/2/15:22:36:11.855 PopulateComponentFamiliesKey - Begin
2017-02-15 17:36:18, Info                  CSI    0000001b@2017/2/15:22:36:18.949 PopulateComponentFamiliesKey - End
2017-02-15 17:36:20, Info                  CSI    0000001c Scavenge: List processing complete.
2017-02-15 17:36:21, Info                  CSI    0000001d Couldn't mark for pending delete: [l:38 ml:39]"\SystemRoot\WinSxS\Temp\PendingDeletes"\[l:43]"7d396bc827e0d101480700009c18bc12.rpcrt4.dll".  Reason: [13]"Cannot Delete"
2017-02-15 17:36:25, Info                  CSI    0000001e ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=5
2017-02-15 17:36:25, Info                  CSI    0000001f Creating NT transaction (seq 4), objectname [6]"(null)"
2017-02-15 17:36:25, Info                  CSI    00000020 Created NT transaction (seq 4) result 0x00000000, handle @0x1b18
2017-02-15 17:36:25, Info                  CSI    00000021 Poqexec successfully registered in [l:12 ml:13]"SetupExecute"
2017-02-15 17:36:25, Info                  CSI    00000022@2017/2/15:22:36:25.965 Beginning NT transaction commit...
2017-02-15 17:36:26, Info                  CSI    00000023@2017/2/15:22:36:26.199 CSI perf trace:
CSIPERF:TXCOMMIT;255848
2017-02-15 17:36:26, Info                  CBS    Scavenge: Completed, disposition: 0X1
2017-02-15 17:36:26, Info                  CSI    00000024@2017/2/15:22:36:26.215 CSI Transaction @0x22434732a30 destroyed
2017-02-15 17:36:26, Info                  CBS    Maint: end scavenge, scavenge time so far: 192 seconds
2017-02-15 17:36:26, Info                  CBS    Maint: TransientManifestCache disabled in config.
2017-02-15 17:36:26, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2017-02-15 17:36:26, Info                  CBS    Maint: completed, interruptions: 0, (this pass: time: 201 seconds, used space change: 154112 KB, hr: 0x00000000, source: N/A)
2017-02-15 17:36:26, Info                  CBS    SQM: Upload requested for report: CBSScavengeSession, session id: 101457977, sample type: Standard
2017-02-15 17:36:26, Info                  CBS    SQM: Ignoring upload request because SQM is not initialized or not running online.
2017-02-15 17:36:26, Info                  CBS    Reboot mark cleared
2017-02-15 17:36:26, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2017-02-15 17:36:26, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-02-15 17:36:26, Info                  CBS    Maint: processing complete.  Session: 30574555_2021536382. [HRESULT = 0x00000000 - S_OK]
2017-02-15 17:36:26, Info                  CBS    Session: 30574555_2021536382 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2017-02-15 17:36:26, Info                  CBS    Received notification that the operation is complete.
2017-02-15 17:36:26, Info                  CBS    progress thread terminated normally
2017-02-15 17:38:26, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2017-02-15 17:38:26, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:38:26, Info                  CBS    Ending the TiWorker main loop.
2017-02-15 17:38:26, Info                  CBS    Starting TiWorker finalization.
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-02-15 17:38:26, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: SrUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-02-15 17:38:27, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-02-15 17:38:27, Info                  CBS    Ending TiWorker finalization.
2017-02-15 17:38:27, Info                  CBS    Ending the TrustedInstaller main loop.
2017-02-15 17:38:27, Info                  CBS    Starting TrustedInstaller finalization.
2017-02-15 17:38:27, Info                  CBS    Winlogon: Stopping notify server
2017-02-15 17:38:27, Info                  CBS    Winlogon: Unloading SysNotify DLL
2017-02-15 17:38:27, Info                  CBS    Ending TrustedInstaller finalization.
2017-02-15 17:38:52, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-15 17:38:52, Info                  CBS    TI: Last boot time: 2017-02-15 17:23:56.499
2017-02-15 17:38:52, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-15 17:38:52, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-15 17:38:52, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-15 17:38:52, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-15 17:38:52, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-15 17:38:52, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:38:52, Info                  CBS    Startup processing thread terminated normally
2017-02-15 17:38:52, Info                  CBS    Starting TiWorker initialization.
2017-02-15 17:38:52, Info                  CBS    Ending TiWorker initialization.
2017-02-15 17:38:52, Info                  CBS    Starting the TiWorker main loop.
2017-02-15 17:38:52, Info                  CBS    TiWorker starts successfully.
2017-02-15 17:38:52, Info                  CBS    Universal Time is: 2017-02-15 22:38:52.517
2017-02-15 17:38:52, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-15 17:38:52, Info                  CSI    00000001@2017/2/15:22:38:52.517 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe4b9346d9 @0x7ffe4bce2150 @0x7ffe4bce1d2b @0x7ff641272ee0 @0x7ff6412738e1 @0x7ffe6231d533)
2017-02-15 17:38:52, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 17:38:52, Info                  CBS    Session: 30574556_1215458986 initialized by client DISM Package Manager Provider, external staging directory: (null)
2017-02-15 17:38:52, Info                  CBS    Client specifies store corruption detect and repair.
2017-02-15 17:38:52, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30574556_1215458986
2017-02-15 17:38:52, Info                  CBS    Reboot mark set
2017-02-15 17:38:52, Info                  CBS    Winlogon: Registering for CreateSession notifications
2017-02-15 17:38:52, Info                  CBS    Winlogon: Loading SysNotify DLL
2017-02-15 17:38:52, Info                  CBS    Winlogon: Starting notify server
2017-02-15 17:40:32, Info                  CBS    Repr: CBS Store check completes
2017-02-15 17:40:33, Info                  CSI    00000002 CSI Store 2191131242192 (0x000001fe29996ed0) initialized
2017-02-15 17:40:33, Info                  CSI    00000003 StoreCorruptionRepair transaction begun. WcpVersion: [l:44]"10.0.10586.570 (th2_release_sec.160801-2011)".
2017-02-15 17:40:33, Info                  CSI    00000004@2017/2/15:22:40:33.715 Starting corruption detection (InnerFlags=5)
2017-02-15 17:40:40, Info                  CSI    00000005 Hashes for file member \SystemRoot\WinSxS\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.10586.310_none_a5154d543e444fc6\clr.dll do not match actual file [l:7]"clr.dll" :
  Found: {l:20 0IbcPXDnRj6jhZMkK/3RNNPZVkE=} Expected: {l:20 03wFDLR3VzVTlcW40IImvcHiqUc=}
  Found: {l:32 Qq7FfotR3Cj8vkF80RjjBUly3V4jJlv62CjkxwlxTK0=} Expected: {l:32 ARTiyJNkFa900nPB6C/ctVbxHiUrBzddCbBCdQ0NNW0=}
2017-02-15 17:41:56, Info                  CSI    00000006 Manifest hash for component [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd" does not match expected value.
 Expected:{l:32 b:74368762a6e348645af5add0dec4137a8145b058a2bd3a54542c826f03ee27e4}
 Found:{l:32 b:2c9fa588b38aff5d65f823fc3a53a5d76cd21cb912941788018f434f1c7e03c6}.
2017-02-15 17:41:56, Info                  CSI    00000007 Looking for manifest in Backup Dir...
2017-02-15 17:41:56, Info                  CSI    00000008 Unable to load manifest for component [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd"
2017-02-15 17:41:56, Info                  CSI    00000009 Manifest hash mismatch. Component: [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd"
2017-02-15 17:41:56, Info                  CSI    0000000a Manifest hash for component [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd" does not match expected value.
 Expected:{l:32 b:74368762a6e348645af5add0dec4137a8145b058a2bd3a54542c826f03ee27e4}
 Found:{l:32 b:2c9fa588b38aff5d65f823fc3a53a5d76cd21cb912941788018f434f1c7e03c6}.
2017-02-15 17:41:56, Info                  CSI    0000000b Looking for manifest in Backup Dir...
2017-02-15 17:41:56, Info                  CSI    0000000c Unable to load manifest for component [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd"
2017-02-15 17:41:56, Info                  CSI    0000000d Manifest hash mismatch. Component: [l:85 ml:140]"amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd"
2017-02-15 17:42:11, Info                  CSI    0000000e Manifest hash for component [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9" does not match expected value.
 Expected:{l:32 b:f57993c0b788ed653aad4ec427b6e2f577175040b639c25792253cd7e2a5360a}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:42:11, Info                  CSI    0000000f Looking for manifest in Backup Dir...
2017-02-15 17:42:11, Info                  CSI    00000010 Unable to load manifest for component [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9"
2017-02-15 17:42:11, Info                  CSI    00000011 Manifest hash mismatch. Component: [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9"
2017-02-15 17:42:11, Info                  CSI    00000012 Manifest hash for component [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9" does not match expected value.
 Expected:{l:32 b:f57993c0b788ed653aad4ec427b6e2f577175040b639c25792253cd7e2a5360a}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:42:11, Info                  CSI    00000013 Looking for manifest in Backup Dir...
2017-02-15 17:42:11, Info                  CSI    00000014 Unable to load manifest for component [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9"
2017-02-15 17:42:11, Info                  CSI    00000015 Manifest hash mismatch. Component: [l:84 ml:140]"amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9"
2017-02-15 17:42:27, Info                  CSI    00000016 Manifest hash for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236" does not match expected value.
 Expected:{l:32 b:ee6ffcf3b8ca47bb0f1ce56525986efc3eb8fdba5b87253e84d4756272188eaa}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:42:27, Info                  CSI    00000017 Looking for manifest in Backup Dir...
2017-02-15 17:42:27, Info                  CSI    00000018 Unable to load manifest for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236"
2017-02-15 17:42:27, Info                  CSI    00000019 Manifest hash mismatch. Component: [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236"
2017-02-15 17:42:27, Info                  CSI    0000001a Manifest hash for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236" does not match expected value.
 Expected:{l:32 b:ee6ffcf3b8ca47bb0f1ce56525986efc3eb8fdba5b87253e84d4756272188eaa}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:42:27, Info                  CSI    0000001b Looking for manifest in Backup Dir...
2017-02-15 17:42:27, Info                  CSI    0000001c Unable to load manifest for component [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236"
2017-02-15 17:42:27, Info                  CSI    0000001d Manifest hash mismatch. Component: [l:95 ml:140]"amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236"
2017-02-15 17:43:40, Info                  CSI    0000001e Manifest hash for component [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe" does not match expected value.
 Expected:{l:32 b:8d5669a53a9c01f26490c296fce6e0479ab380712474cbca768a04a3b9d038cc}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:40, Info                  CSI    0000001f Looking for manifest in Backup Dir...
2017-02-15 17:43:40, Info                  CSI    00000020 Unable to load manifest for component [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe"
2017-02-15 17:43:40, Info                  CSI    00000021 Manifest hash mismatch. Component: [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe"
2017-02-15 17:43:40, Info                  CSI    00000022 Manifest hash for component [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe" does not match expected value.
 Expected:{l:32 b:8d5669a53a9c01f26490c296fce6e0479ab380712474cbca768a04a3b9d038cc}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:40, Info                  CSI    00000023 Looking for manifest in Backup Dir...
2017-02-15 17:43:40, Info                  CSI    00000024 Unable to load manifest for component [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe"
2017-02-15 17:43:40, Info                  CSI    00000025 Manifest hash mismatch. Component: [l:100 ml:140]"amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe"
2017-02-15 17:43:43, Info                  CSI    00000026 Manifest hash for component [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6" does not match expected value.
 Expected:{l:32 b:36c4de717a355910e63648f76ca38c715ee2e32b24413660577ac5b749c74ef8}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:43, Info                  CSI    00000027 Looking for manifest in Backup Dir...
2017-02-15 17:43:43, Info                  CSI    00000028 Unable to load manifest for component [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6"
2017-02-15 17:43:43, Info                  CSI    00000029 Manifest hash mismatch. Component: [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6"
2017-02-15 17:43:43, Info                  CSI    0000002a Manifest hash for component [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6" does not match expected value.
 Expected:{l:32 b:36c4de717a355910e63648f76ca38c715ee2e32b24413660577ac5b749c74ef8}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:43, Info                  CSI    0000002b Looking for manifest in Backup Dir...
2017-02-15 17:43:43, Info                  CSI    0000002c Unable to load manifest for component [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6"
2017-02-15 17:43:43, Info                  CSI    0000002d Manifest hash mismatch. Component: [l:99 ml:140]"amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6"
2017-02-15 17:43:51, Info                  CSI    0000002e Manifest hash for component [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b" does not match expected value.
 Expected:{l:32 b:cae4abf53d2c78169acf57bdfd722c604e91c8409f6a3b006833b1b192cb93fb}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:51, Info                  CSI    0000002f Looking for manifest in Backup Dir...
2017-02-15 17:43:51, Info                  CSI    00000030 Unable to load manifest for component [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b"
2017-02-15 17:43:51, Info                  CSI    00000031 Manifest hash mismatch. Component: [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b"
2017-02-15 17:43:51, Info                  CSI    00000032 Manifest hash for component [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b" does not match expected value.
 Expected:{l:32 b:cae4abf53d2c78169acf57bdfd722c604e91c8409f6a3b006833b1b192cb93fb}
 Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2017-02-15 17:43:51, Info                  CSI    00000033 Looking for manifest in Backup Dir...
2017-02-15 17:43:51, Info                  CSI    00000034 Unable to load manifest for component [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b"
2017-02-15 17:43:51, Info                  CSI    00000035 Manifest hash mismatch. Component: [l:83 ml:140]"amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b"
2017-02-15 17:55:44, Info                  CSI    00000036@2017/2/15:22:55:44.09 Corruption detection complete. numCorruptions = 7, Disp = 1.
2017-02-15 17:55:44, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2017-02-15 17:55:44, Info                  CSI    00000037@2017/2/15:22:55:44.149 CSI Transaction @0x1fe2b3a11f0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id [26]"TI5.30574556_1215458986:1/"

2017-02-15 17:55:44, Info                  CSI    00000038@2017/2/15:22:55:44.165 CSI Transaction @0x1fe2b3a11f0 destroyed
2017-02-15 17:55:44, Info                  CBS    Repr: CSI Store check completes
2017-02-15 17:55:44, Info                  CBS    Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2017-02-15 17:55:44, Info                  CBS    Exec: Clients specified using Windows Update.
2017-02-15 17:55:44, Info                  CBS    Failed to get services collection [HRESULT = 0x8007043c - ERROR_NOT_SAFEBOOT_SERVICE]
2017-02-15 17:55:44, Info                  CBS    Failed to get windows update server configuration. [HRESULT = 0x8007043c - ERROR_NOT_SAFEBOOT_SERVICE]
2017-02-15 17:55:44, Info                  CBS    DWLD: Failed to begin WU search [HRESULT = 0x8007043c - ERROR_NOT_SAFEBOOT_SERVICE]
2017-02-15 17:55:44, Info                  CBS    Failed to search and collect all capabilities [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Failed to repair store. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Ensure CBS corruption flag is clear
2017-02-15 17:55:44, Info                  CBS   
=================================
Checking System Update Readiness.

(p)   CSI Manifest Corrupt         amd64_microsoft-windows-winlogon_31bf3856ad364e35_10.0.10586.63_none_f3dc0aaa859f8abd
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-wimgapi_31bf3856ad364e35_10.0.10586.11_none_0d2a4257c57c6ed9
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.10586.71_none_cb0e7b3963dcd236
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_10.0.10586.162_none_0ce60803660430fe
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_10.0.10586.71_none_f9f25b6b9f62eda6
Repair failed: Missing replacement manifest.
(p)   CSI Manifest Corrupt         amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b
Repair failed: Missing replacement manifest.
(p)   CSI Payload Corrupt         amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.10586.310_none_a5154d543e444fc6\clr.dll
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption:   7
   CBS Manifest Corruption:   0
   CBS Metadata Corruption:   0
   CSI Manifest Corruption:   6
   CSI Metadata Corruption:   0
   CSI Payload Corruption:   1
Total Repaired Corruption:   0
   CBS Manifest Repaired:   0
   CSI Manifest Repaired:   0
   CSI Payload Repaired:   0
   CSI Store Metadata refreshed:   True

Total Operation Time: 1011 seconds.

2017-02-15 17:55:44, Info                  CBS    CheckSur: hrStatus: 0x800f0906 [CBS_E_DOWNLOAD_FAILURE], download Result: 0x8007043c [ERROR_NOT_SAFEBOOT_SERVICE]
2017-02-15 17:55:44, Info                  CBS    Count of times corruption detected: 1
2017-02-15 17:55:44, Info                  CBS    Seconds between initial corruption detections: -1
2017-02-15 17:55:44, Info                  CBS    Seconds between corruption and repair: -1
2017-02-15 17:55:44, Info                  CBS    SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2017-02-15 17:55:44, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Reboot mark cleared
2017-02-15 17:55:44, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2017-02-15 17:55:44, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-02-15 17:55:44, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30574556_1215458986 [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Warning               CBS    Current sub stage percentage lower than last sub stage percentage. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2017-02-15 17:55:44, Error                 CBS    Session: 30574556_1215458986 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Session: 30574556_1215458986 finalized. Download error: 0x8007043c [ERROR_NOT_SAFEBOOT_SERVICE], Reboot required: no [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2017-02-15 17:55:44, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800f0906]
2017-02-15 17:57:44, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2017-02-15 17:57:44, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:57:44, Info                  CBS    Ending the TiWorker main loop.
2017-02-15 17:57:44, Info                  CBS    Starting TiWorker finalization.
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-02-15 17:57:44, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: SrUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-02-15 17:57:45, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-02-15 17:57:45, Info                  CBS    Ending TiWorker finalization.
2017-02-15 17:57:45, Info                  CBS    Ending the TrustedInstaller main loop.
2017-02-15 17:57:45, Info                  CBS    Starting TrustedInstaller finalization.
2017-02-15 17:57:45, Info                  CBS    Winlogon: Stopping notify server
2017-02-15 17:57:45, Info                  CBS    Winlogon: Unloading SysNotify DLL
2017-02-15 17:57:45, Info                  CBS    Ending TrustedInstaller finalization.
2017-02-15 19:46:06, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-15 19:46:06, Info                  CBS    TI: Last boot time: 2017-02-15 17:23:56.499
2017-02-15 19:46:06, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-15 19:46:06, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-15 19:46:06, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-15 19:46:06, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-15 19:46:06, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-15 19:46:06, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 19:46:06, Info                  CBS    Startup processing thread terminated normally
2017-02-15 19:46:06, Info                  CBS    Starting TiWorker initialization.
2017-02-15 19:46:06, Info                  CBS    Ending TiWorker initialization.
2017-02-15 19:46:06, Info                  CBS    Starting the TiWorker main loop.
2017-02-15 19:46:06, Info                  CBS    TiWorker starts successfully.
2017-02-15 19:46:06, Info                  CBS    TiWorker: Client requests SFP repair object.
2017-02-15 19:46:06, Info                  CBS    Universal Time is: 2017-02-16 00:46:06.759
2017-02-15 19:46:06, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-15 19:46:06, Info                  CSI    00000001@2017/2/16:00:46:06.759 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe4f2346d9 @0x7ffe52012150 @0x7ffe52011d2b @0x7ff641272ee0 @0x7ff641273c80 @0x7ffe6231d533)
2017-02-15 19:46:06, Info                  CBS    NonStart: Windows is in Safe Mode.
2017-02-15 19:46:06, Info                  CSI    00000002@2017/2/16:00:46:06.774 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe4f2346d9 @0x7ffe5a284fe5 @0x7ffe5a285132 @0x7ff64127244d @0x7ff641273c97 @0x7ffe6231d533)
2017-02-15 19:46:07, Info                  CSI    00000003 CSI Store 1652151492256 (0x00000180abe71ea0) initialized
2017-02-15 19:46:10, Info                  CSI    00000004 [SR] Verifying 100 (0x0000000000000064) components
2017-02-15 19:46:10, Info                  CSI    00000005 [SR] Beginning Verify and Repair transaction
2017-02-15 19:46:10, Info                  CSI    00000006@2017/2/16:00:46:10.978 Primitive installers committed for repair
2017-02-15 19:46:10, Info                  CSI    00000007@2017/2/16:00:46:10.993 Primitive installers committed for repair
2017-02-15 19:46:10, Info                  CSI    00000008@2017/2/16:00:46:10.993 Primitive installers committed for repair
2017-02-15 19:46:11, Info         

7

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 15, 2017, 08:07:24 am »

Malwarebytes & Superantispyware

8

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 15, 2017, 06:49:19 am »

Boggin & Julian,

The repair/installs I tired before were done with Windows SE off. I have two other antivirus programs installed but they are never running until I do a scan with them.

I ran the repair for the reparse points first in regular mode then in safe mode with networking (below). There are 161 reparse points listed and 4 had errors. The repairs apparently failed. Here's the log for that:
┌────────────────────────────────┐
│[STARTED] [2/14/2017 6:47:52 PM]│
└────────────────────────────────┘
Running Repair on C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files

   

• Command to Run: Create Default Reparse Point (This Is A Default Windows Reparse Point, Lets Put It Back The Way It Should Be)
• Calling Checking If Link Folder Exists
• Link Folder Does Exist, We need to remove it as we can't make Reparse Points for exisiting folders.
• Setting Owner On Folder (So We Have A Better Chance For Permission To Remove It).
• Calling RemoveDirectoryW (Only Removes Empty Folders, Just In Case)
• RemoveDirectoryW Returned An Error, Error: 0 - The directory is not empty.
• Even Though We Got An Error, Lets Keep Going.
• Type is JUNCTION, Calling: mklink /J "C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files" "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache"
• Setting Owner To System And Everyone Read Access To Denied (This Is The Default) To The Link Folder: C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files

Running Repair on C:\Users\Default\Cookies

   

• Command to Run: Create Default Reparse Point (This Is A Default Windows Reparse Point, Lets Put It Back The Way It Should Be)
• Calling Checking If Link Folder Exists
• Link Folder Does Exist, We need to remove it as we can't make Reparse Points for exisiting folders.
• Setting Owner On Folder (So We Have A Better Chance For Permission To Remove It).
• Calling RemoveDirectoryW (Only Removes Empty Folders, Just In Case)
• RemoveDirectoryW Returned An Error, Error: 0 - The directory is not empty.
• Even Though We Got An Error, Lets Keep Going.
• Type is JUNCTION, Calling: mklink /J "C:\Users\Default\Cookies" "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCookies"
• Setting Owner To System And Everyone Read Access To Denied (This Is The Default) To The Link Folder: C:\Users\Default\Cookies

Running Repair on C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\Temporary Internet Files

   

• Command to Run: Create Default Reparse Point (This Is A Default Windows Reparse Point, Lets Put It Back The Way It Should Be)
• Calling Checking If Link Folder Exists
• Link Folder Does Exist, We need to remove it as we can't make Reparse Points for exisiting folders.
• Setting Owner On Folder (So We Have A Better Chance For Permission To Remove It).
• Calling RemoveDirectoryW (Only Removes Empty Folders, Just In Case)
• RemoveDirectoryW Returned An Error, Error: 0 - The directory is not empty.
• Even Though We Got An Error, Lets Keep Going.
• Type is JUNCTION, Calling: mklink /J "C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\Temporary Internet Files" "C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\INetCache"
• Setting Owner To System And Everyone Read Access To Denied (This Is The Default) To The Link Folder: C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\Temporary Internet Files

Running Repair on C:\Users\DefaultAppPool\Cookies

   

• Command to Run: Create Default Reparse Point (This Is A Default Windows Reparse Point, Lets Put It Back The Way It Should Be)
• Calling Checking If Link Folder Exists
• Link Folder Does Exist, We need to remove it as we can't make Reparse Points for exisiting folders.
• Setting Owner On Folder (So We Have A Better Chance For Permission To Remove It).
• Calling RemoveDirectoryW (Only Removes Empty Folders, Just In Case)
• RemoveDirectoryW Returned An Error, Error: 0 - The directory is not empty.
• Even Though We Got An Error, Lets Keep Going.
• Type is JUNCTION, Calling: mklink /J "C:\Users\DefaultAppPool\Cookies" "C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\INetCookies"
• Setting Owner To System And Everyone Read Access To Denied (This Is The Default) To The Link Folder: C:\Users\DefaultAppPool\Cookies

┌─────────────────────────────────┐
│[FINISHED] [2/14/2017 6:48:00 PM]│
└─────────────────────────────────┘

I then ran the Environment Variable fix although I don't know if it made any changes because what it listed to fix and what it listed they would look like after the fix, looked the same to me.

Still in Safe mode with networking, I then ran the two commands you gave as administrator. After the .../ScanHealth one it said "The component store is repairable." Then I ran the ... /RestoreHealth and after 100% it said "Error: 0x800f0906  The source file could not be downloaded..."

Please advise.

9

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 13, 2017, 09:48:50 am »

Ok, ... standing by for Julian then.

10

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 11, 2017, 11:23:54 am »

Has Julian forgotten about me?

11

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 10, 2017, 02:41:47 pm »

Yes, I see it, I'm standing by for Julian then ...

12

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 10, 2017, 01:59:04 pm »

Done. There are the results:

┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.9.18 - Pre-Scan
│ Computer: D-GATEWAYDX4831 (Windows 10 Pro 10.0.10586.589 ) (64-bit)
│ [Started Scan - 2/10/2017 4:28:18 PM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (2/10/2017 4:28:18 PM)
│
│ No problems were found with the Packages Files.
│
│ Files Checked & Verified: 6,712
│
│ Done Scanning Windows Packages Files.(2/10/2017 4:38:32 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (2/10/2017 4:38:32 PM)
│
│ Missing Default Reparse Point: (Original Path: C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files) (Target Path: C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\Default\Cookies) (Target Path: C:\Users\Default\AppData\Local\Microsoft\Windows\INetCookies)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\Temporary Internet Files) (Target Path: C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\INetCache)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\DefaultAppPool\Cookies) (Target Path: C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\INetCookies)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Problems were found with the Reparse Points.
│ You can use the Repair Reparse Points Tool at the bottom of this Window to try and fix these problems.
│
│ Files & Folders Searched: 803,224
│ Reparse Points Found: 16,982
│
│ Done Scanning Reparse Points.(2/10/2017 4:45:25 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (2/10/2017 4:45:25 PM)
│
│ No problems were found with the Environment Variables.
│
│ Done Checking Environment Variables. (2/10/2017 4:45:25 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 2/10/2017 4:45:25 PM]
│
│

• Scan Complete - Problems Found!

│

│

• You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.

│

│

• While problems have been found, you can still run the repairs in the program.

│

• But for the best results it is recommended to fix the problems reported in this scan if possible.

└────────────────────────────────────────────────────────────────────────────────┘

13

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 10, 2017, 08:04:28 am »

"In the Windows Repair program click on Option 2 and run the Pre-Scan. " Which Windows Repair program do you mean?

14

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 10, 2017, 06:48:52 am »

Thanks for the reply Julian. Unfortunately, I don't understand what you just said. Could you try again?

15

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 09, 2017, 01:54:12 pm »

Ok. I've been trying to upload this stuff for over 2 hours. I have the 3rd file with the SFCFix scan attached. Are you sure you don't need it? You read my first post for today?

A clean install isn't feasible for me. As originally posted, I've tried repair installs already and they fail at 33%. Do the scans identify specific files which need repair and if so, can enough of them be repaired to at least allow the Cumulative Upgrade to complete? If so, then it may update to v1607 afterwards. SFCFix seems to ask for a source and if that's the repair/install disk, it hasn't been in the D: drive for it to access. Is that what it needs. If so how do I get it to run and access it?

16

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 09, 2017, 01:31:50 pm »

The prior copy/paste was incomplete. It seems there's some maximum file size. Now I'll try to attach a doc file with the same information for file 2:

17

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 09, 2017, 01:19:16 pm »

... attaching files 2 and 3 to to upload into separate posts both failed. Copy/pasting the file contents also failed. Here is just the contents of file 2 which seems to pertain to the time of the associated scan:

FILE 2:

2017-02-08 12:23:01, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-08 12:23:01, Info                  CBS    TI: Last boot time: 2017-02-08 11:22:58.499
2017-02-08 12:23:01, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-08 12:23:01, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-08 12:23:01, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-08 12:23:01, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-08 12:23:01, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-08 12:23:01, Info                  CBS    Startup processing thread terminated normally
2017-02-08 12:23:01, Info                  CBS    Starting TiWorker initialization.
2017-02-08 12:23:01, Info                  CBS    Ending TiWorker initialization.
2017-02-08 12:23:01, Info                  CBS    Starting the TiWorker main loop.
2017-02-08 12:23:01, Info                  CBS    TiWorker starts successfully.
2017-02-08 12:23:01, Info                  CBS    Universal Time is: 2017-02-08 17:23:01.132
2017-02-08 12:23:01, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-08 12:23:01, Info                  CSI    00000001@2017/2/8:17:23:01.136 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffb2aec46d9 @0x7ffb2b1e2150 @0x7ffb2b1e1d2b @0x7ff753cb2ee0 @0x7ff753cb38e1 @0x7ffb4067d533)
2017-02-08 12:23:01, Info                  CBS    NonStart: Set pending store consistency check.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SOFTWARE' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\SOFTWARE'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SYSTEM' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\SYSTEM'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SECURITY' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\SECURITY'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SAM' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\SAM'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/COMPONENTS' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\COMPONENTS'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/DRIVERS' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\DRIVERS'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/DEFAULT' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\System32\config\DEFAULT'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/Users/Default/ntuser.dat' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Users\Default\ntuser.dat'.
2017-02-08 12:23:01, Info                  CBS    Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/system32/smi/store/Machine/schema.dat' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\WINDOWS\system32\smi\store\Machine\schema.dat'.
2017-02-08 12:23:01, Info                  CBS    Offline image is: read-only
2017-02-08 12:23:01, Info                  CBS    Disabling manifest caching, because the image is not writeable.
2017-02-08 12:23:02, Info                  CSI    00000002 CSI Store 2076124137088 (0x000001e362a44680) initialized
2017-02-08 12:23:02, Info                  CBS    Session: 952_3602828 initialized by client SPP, external staging directory: (null)
2017-02-08 12:23:03, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SOFTWARE
2017-02-08 12:23:04, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SYSTEM
2017-02-08 12:23:04, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SECURITY
2017-02-08 12:23:04, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/SAM
2017-02-08 12:23:04, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/COMPONENTS
2017-02-08 12:23:04, Info                  CBS    Failed to flush offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/DRIVERS. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]
2017-02-08 12:23:04, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/DRIVERS
2017-02-08 12:23:05, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/System32/config/DEFAULT
2017-02-08 12:23:05, Info                  CBS    Failed to flush offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/Users/Default/ntuser.dat. [HRESULT = 0x800703f8 - ERROR_REGISTRY_IO_FAILED]
2017-02-08 12:23:05, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/Users/Default/ntuser.dat
2017-02-08 12:23:05, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy6/WINDOWS/system32/smi/store/Machine/schema.dat
2017-02-08 12:25:05, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2017-02-08 12:25:05, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-08 12:25:05, Info                  CBS    Ending the TiWorker main loop.
2017-02-08 12:25:05, Info                  CBS    Starting TiWorker finalization.
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: SrUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-02-08 12:25:05, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-02-08 12:25:05, Info                  CBS    Ending TiWorker finalization.
2017-02-08 12:25:05, Info                  CBS    Ending the TrustedInstaller main loop.
2017-02-08 12:25:05, Info                  CBS    Starting TrustedInstaller finalization.
2017-02-08 12:25:05, Info                  CBS    Ending TrustedInstaller finalization.
2017-02-08 17:34:30, Info                  CBS    TI: --- Initializing Trusted Installer ---
2017-02-08 17:34:30, Info                  CBS    TI: Last boot time: 2017-02-08 11:22:58.499
2017-02-08 17:34:30, Info                  CBS    Starting TrustedInstaller initialization.
2017-02-08 17:34:30, Info                  CBS    Ending TrustedInstaller initialization.
2017-02-08 17:34:30, Info                  CBS    Starting the TrustedInstaller main loop.
2017-02-08 17:34:30, Info                  CBS    TrustedInstaller service starts successfully.
2017-02-08 17:34:30, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2017-02-08 17:34:30, Info                  CBS    Startup processing thread terminated normally
2017-02-08 17:34:30, Info                  CBS    Starting TiWorker initialization.
2017-02-08 17:34:30, Info                  CBS    Ending TiWorker initialization.
2017-02-08 17:34:30, Info                  CBS    Starting the TiWorker main loop.
2017-02-08 17:34:30, Info                  CBS    TiWorker starts successfully.
2017-02-08 17:34:30, Info                  CBS    TiWorker: Client requests SFP repair object.
2017-02-08 17:34:30, Info                  CBS    Universal Time is: 2017-02-08 22:34:30.606
2017-02-08 17:34:30, Info                  CBS    Loaded Servicing Stack v10.0.10586.570 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.570_none_7645b09c266beb53\cbscore.dll
2017-02-08 17:34:30, Info                  CSI    00000001@2017/2/8:22:34:30.615 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffb20f746d9 @0x7ffb21292150 @0x7ffb21291d2b @0x7ff753cb2ee0 @0x7ff753cb3c80 @0x7ffb4067d533)
2017-02-08 17:34:30, Info                  CBS    NonStart: Set pending store consistency check.
2017-02-08 17:34:30, Info                  CSI    00000002@2017/2/8:22:34:30.619 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffb20f746d9 @0x7ffb2d844fe5 @0x7ffb2d845132 @0x7ff753cb244d @0x7ff753cb3c97 @0x7ffb4067d533)
2017-02-08 17:34:31, Info                  CSI    00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x988dcfdfb0
2017-02-08 17:34:31, Info                  CSI    00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2017-02-08 17:34:31, Info                  CSI    00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x274
2017-02-08 17:34:31, Info                  CSI    00000006 Poqexec successfully registered in [l:12 ml:13]"SetupExecute"
2017-02-08 17:34:31, Info                  CSI    00000007@2017/2/8:22:34:31.843 Beginning NT transaction commit...
2017-02-08 17:34:31, Info                  CSI    00000008@2017/2/8:22:34:31.844 CSI perf trace:
CSIPERF:TXCOMMIT;671
2017-02-08 17:34:31, Info                  CSI    00000009 CSI Store 2730147049680 (0x0000027ba971f0d0) initialized
2017-02-08 17:34:34, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2017-02-08 17:34:34, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2017-02-08 17:34:34, Info                  CSI    0000000c@2017/2/8:22:34:34.910 Primitive installers committed for repair
2017-02-08 17:34:34, Info                  CSI    0000000d@2017/2/8:22:34:34.941 Primitive installers committed for repair
2017-02-08 17:34:34, Info                  CSI    0000000e@2017/2/8:22:34:34.956 Primitive installers committed for repair
2017-02-08 17:34:34, Info                  CSI    0000000f@2017/2/8:22:34:34.973 Primitive installers committed for repair
2017-02-08 17:34:34, Info                  CSI    00000010@2017/2/8:22:34:34.986 Primitive installers committed for repair
2017-02-08 17:34:34, Info                  CSI    00000011@2017/2/8:22:34:34.999 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000012@2017/2/8:22:34:35.012 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000013@2017/2/8:22:34:35.025 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000014@2017/2/8:22:34:35.037 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000015@2017/2/8:22:34:35.050 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000016@2017/2/8:22:34:35.063 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000017@2017/2/8:22:34:35.076 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000018@2017/2/8:22:34:35.088 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000019@2017/2/8:22:34:35.101 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001a@2017/2/8:22:34:35.113 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001b@2017/2/8:22:34:35.126 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001c@2017/2/8:22:34:35.139 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001d@2017/2/8:22:34:35.152 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001e@2017/2/8:22:34:35.164 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000001f@2017/2/8:22:34:35.200 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000020@2017/2/8:22:34:35.214 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000021@2017/2/8:22:34:35.226 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000022@2017/2/8:22:34:35.239 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000023@2017/2/8:22:34:35.252 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000024@2017/2/8:22:34:35.265 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000025@2017/2/8:22:34:35.303 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000026@2017/2/8:22:34:35.316 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000027@2017/2/8:22:34:35.329 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000028@2017/2/8:22:34:35.341 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000029@2017/2/8:22:34:35.354 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002a@2017/2/8:22:34:35.367 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002b@2017/2/8:22:34:35.380 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002c@2017/2/8:22:34:35.392 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002d@2017/2/8:22:34:35.405 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002e@2017/2/8:22:34:35.417 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000002f@2017/2/8:22:34:35.430 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000030@2017/2/8:22:34:35.443 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000031@2017/2/8:22:34:35.456 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000032@2017/2/8:22:34:35.469 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000033@2017/2/8:22:34:35.482 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000034@2017/2/8:22:34:35.495 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000035@2017/2/8:22:34:35.508 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000036@2017/2/8:22:34:35.521 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000037@2017/2/8:22:34:35.533 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000038@2017/2/8:22:34:35.546 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000039@2017/2/8:22:34:35.558 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003a@2017/2/8:22:34:35.571 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003b@2017/2/8:22:34:35.584 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003c@2017/2/8:22:34:35.596 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003d@2017/2/8:22:34:35.609 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003e@2017/2/8:22:34:35.621 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000003f@2017/2/8:22:34:35.634 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000040@2017/2/8:22:34:35.646 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000041@2017/2/8:22:34:35.659 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000042@2017/2/8:22:34:35.672 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000043@2017/2/8:22:34:35.685 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000044@2017/2/8:22:34:35.697 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000045@2017/2/8:22:34:35.709 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000046@2017/2/8:22:34:35.722 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000047@2017/2/8:22:34:35.734 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000048@2017/2/8:22:34:35.750 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000049@2017/2/8:22:34:35.763 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004a@2017/2/8:22:34:35.778 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004b@2017/2/8:22:34:35.792 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004c@2017/2/8:22:34:35.805 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004d@2017/2/8:22:34:35.818 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004e@2017/2/8:22:34:35.831 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000004f@2017/2/8:22:34:35.843 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000050@2017/2/8:22:34:35.857 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000051@2017/2/8:22:34:35.870 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000052@2017/2/8:22:34:35.882 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000053@2017/2/8:22:34:35.895 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000054@2017/2/8:22:34:35.908 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000055@2017/2/8:22:34:35.920 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000056@2017/2/8:22:34:35.933 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000057@2017/2/8:22:34:35.946 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000058@2017/2/8:22:34:35.958 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    00000059@2017/2/8:22:34:35.972 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000005a@2017/2/8:22:34:35.985 Primitive installers committed for repair
2017-02-08 17:34:35, Info                  CSI    0000005b@2017/2/8:22:34:35.998 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000005c@2017/2/8:22:34:36.011 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000005d@2017/2/8:22:34:36.024 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000005e@2017/2/8:22:34:36.036 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000005f@2017/2/8:22:34:36.049 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000060@2017/2/8:22:34:36.061 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000061@2017/2/8:22:34:36.074 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000062@2017/2/8:22:34:36.088 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000063@2017/2/8:22:34:36.101 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000064@2017/2/8:22:34:36.113 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000065@2017/2/8:22:34:36.127 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000066@2017/2/8:22:34:36.140 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000067@2017/2/8:22:34:36.153 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000068@2017/2/8:22:34:36.165 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000069@2017/2/8:22:34:36.178 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006a@2017/2/8:22:34:36.190 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006b@2017/2/8:22:34:36.203 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006c@2017/2/8:22:34:36.216 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006d@2017/2/8:22:34:36.228 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006e@2017/2/8:22:34:36.241 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000006f@2017/2/8:22:34:36.254 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000070 [SR] Verify complete
2017-02-08 17:34:36, Info                  CSI    00000071 [SR] Verifying 100 (0x0000000000000064) components
2017-02-08 17:34:36, Info                  CSI    00000072 [SR] Beginning Verify and Repair transaction
2017-02-08 17:34:36, Info                  CSI    00000073@2017/2/8:22:34:36.519 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000074@2017/2/8:22:34:36.532 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000075@2017/2/8:22:34:36.544 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000076@2017/2/8:22:34:36.556 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000077@2017/2/8:22:34:36.569 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000078@2017/2/8:22:34:36.581 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000079@2017/2/8:22:34:36.594 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007a@2017/2/8:22:34:36.606 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007b@2017/2/8:22:34:36.619 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007c@2017/2/8:22:34:36.632 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007d@2017/2/8:22:34:36.644 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007e@2017/2/8:22:34:36.657 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000007f@2017/2/8:22:34:36.669 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000080@2017/2/8:22:34:36.683 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000081@2017/2/8:22:34:36.695 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000082@2017/2/8:22:34:36.708 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000083@2017/2/8:22:34:36.721 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000084@2017/2/8:22:34:36.734 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000085@2017/2/8:22:34:36.746 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000086@2017/2/8:22:34:36.758 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000087@2017/2/8:22:34:36.771 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000088@2017/2/8:22:34:36.784 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000089@2017/2/8:22:34:36.796 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008a@2017/2/8:22:34:36.809 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008b@2017/2/8:22:34:36.821 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008c@2017/2/8:22:34:36.834 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008d@2017/2/8:22:34:36.847 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008e@2017/2/8:22:34:36.859 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    0000008f@2017/2/8:22:34:36.872 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000090@2017/2/8:22:34:36.885 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000091@2017/2/8:22:34:36.898 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000092@2017/2/8:22:34:36.910 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000093@2017/2/8:22:34:36.923 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000094@2017/2/8:22:34:36.935 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000095@2017/2/8:22:34:36.947 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000096@2017/2/8:22:34:36.960 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000097@2017/2/8:22:34:36.976 Primitive installers committed for repair
2017-02-08 17:34:36, Info                  CSI    00000098@2017/2/8:22:34:36.989 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    00000099@2017/2/8:22:34:37.01 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009a@2017/2/8:22:34:37.014 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009b@2017/2/8:22:34:37.027 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009c@2017/2/8:22:34:37.039 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009d@2017/2/8:22:34:37.052 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009e@2017/2/8:22:34:37.064 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    0000009f@2017/2/8:22:34:37.076 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a0@2017/2/8:22:34:37.089 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a1@2017/2/8:22:34:37.101 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a2@2017/2/8:22:34:37.113 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a3@2017/2/8:22:34:37.126 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a4@2017/2/8:22:34:37.139 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a5@2017/2/8:22:34:37.151 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a6@2017/2/8:22:34:37.166 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a7@2017/2/8:22:34:37.180 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a8@2017/2/8:22:34:37.192 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000a9@2017/2/8:22:34:37.204 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000aa@2017/2/8:22:34:37.217 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ab@2017/2/8:22:34:37.229 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ac@2017/2/8:22:34:37.242 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ad@2017/2/8:22:34:37.254 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ae@2017/2/8:22:34:37.266 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000af@2017/2/8:22:34:37.279 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b0@2017/2/8:22:34:37.292 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b1@2017/2/8:22:34:37.305 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b2@2017/2/8:22:34:37.317 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b3@2017/2/8:22:34:37.329 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b4@2017/2/8:22:34:37.342 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b5@2017/2/8:22:34:37.354 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b6@2017/2/8:22:34:37.366 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b7@2017/2/8:22:34:37.379 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b8@2017/2/8:22:34:37.391 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000b9@2017/2/8:22:34:37.404 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ba@2017/2/8:22:34:37.416 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000bb@2017/2/8:22:34:37.429 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000bc@2017/2/8:22:34:37.441 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000bd@2017/2/8:22:34:37.454 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000be@2017/2/8:22:34:37.466 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000bf@2017/2/8:22:34:37.484 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c0@2017/2/8:22:34:37.496 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c1@2017/2/8:22:34:37.508 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c2@2017/2/8:22:34:37.521 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c3@2017/2/8:22:34:37.534 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c4@2017/2/8:22:34:37.546 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c5@2017/2/8:22:34:37.558 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c6@2017/2/8:22:34:37.571 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c7@2017/2/8:22:34:37.583 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c8@2017/2/8:22:34:37.595 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000c9@2017/2/8:22:34:37.608 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ca@2017/2/8:22:34:37.620 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000cb@2017/2/8:22:34:37.633 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000cc@2017/2/8:22:34:37.644 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000cd@2017/2/8:22:34:37.656 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000ce@2017/2/8:22:34:37.669 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000cf@2017/2/8:22:34:37.681 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d0@2017/2/8:22:34:37.694 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d1@2017/2/8:22:34:37.706 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d2@2017/2/8:22:34:37.718 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d3@2017/2/8:22:34:37.731 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d4@2017/2/8:22:34:37.743 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d5@2017/2/8:22:34:37.755 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d6@2017/2/8:22:34:37.768 Primitive installers committed for repair
2017-02-08 17:34:37, Info                  CSI    000000d7 [SR] Verify complete
2017-02-08 17:34:37, Info                  CSI    000000d8 [SR] Verifying 100 (0x0000000000000064) components
2017-02-08 17:34:37, Info                  CSI    000000d9 [SR] Beginning Verify and Repair transaction
2017-02-08 17:34:37, Info                  CSI    000000da@2017/2/8:22:34:37.989 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000db@2017/2/8:22:34:38.02 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000dc@2017/2/8:22:34:38.014 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000dd@2017/2/8:22:34:38.026 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000de@2017/2/8:22:34:38.039 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000df@2017/2/8:22:34:38.051 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e0@2017/2/8:22:34:38.064 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e1@2017/2/8:22:34:38.076 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e2@2017/2/8:22:34:38.088 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e3@2017/2/8:22:34:38.101 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e4@2017/2/8:22:34:38.113 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e5@2017/2/8:22:34:38.126 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e6@2017/2/8:22:34:38.138 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e7@2017/2/8:22:34:38.150 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e8@2017/2/8:22:34:38.163 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000e9@2017/2/8:22:34:38.175 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ea@2017/2/8:22:34:38.187 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000eb@2017/2/8:22:34:38.199 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ec@2017/2/8:22:34:38.212 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ed@2017/2/8:22:34:38.224 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ee@2017/2/8:22:34:38.236 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ef@2017/2/8:22:34:38.249 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f0@2017/2/8:22:34:38.261 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f1@2017/2/8:22:34:38.274 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f2@2017/2/8:22:34:38.286 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f3@2017/2/8:22:34:38.298 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f4@2017/2/8:22:34:38.311 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f5@2017/2/8:22:34:38.323 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f6@2017/2/8:22:34:38.336 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f7@2017/2/8:22:34:38.348 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f8@2017/2/8:22:34:38.360 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000f9@2017/2/8:22:34:38.372 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000fa@2017/2/8:22:34:38.385 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000fb@2017/2/8:22:34:38.397 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000fc@2017/2/8:22:34:38.409 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000fd@2017/2/8:22:34:38.421 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000fe@2017/2/8:22:34:38.434 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    000000ff@2017/2/8:22:34:38.446 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000100@2017/2/8:22:34:38.459 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000101@2017/2/8:22:34:38.505 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000102@2017/2/8:22:34:38.519 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000103@2017/2/8:22:34:38.532 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000104@2017/2/8:22:34:38.544 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000105@2017/2/8:22:34:38.557 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000106@2017/2/8:22:34:38.571 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000107@2017/2/8:22:34:38.584 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000108@2017/2/8:22:34:38.597 Primitive installers committed for repair
2017-02-08 17:34:38, Info                  CSI    00000109@2017/2/8:22:34:38.609 Primitive installers committed for repair
2017-02-08 17:34:38, I

18

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 09, 2017, 11:56:33 am »

I've tried to post my reply (below) twice, which included three attached files but it isn't working. So here's my reply and just one file, then I'll add the next two files in separate posts:

I don't really know what the CBS log and DISM log files are about or what they specifically relate to. When I run SFCFix, at the end it directs me to where I can find the DISM lof file not a CBS log file. That's why I sent that one to you last time. You seem to prefer and need to CBS log file because it includes what you need to know. So why does SFCFix mention the DISM file?

I hope it's ok that I created a new subfolder in the CBS folder to place copied and renamed files for later reference.

I ran SFC /Scannow yesterday around 5:30p and the attached CBS. log file "1..." seems to show the results of that. I then ran SFCFix but had to leave it running as I went out. When I came back after a couple hours, my system had crashed and rebooted back to the desktop. This morning I saw another CBSPersist file, attached file "2...". What's the difference between the CBS log, Persist and Filter files in the CBS folder? I then ran SFCFix and the results of that seem to be in atttached file "3..."

I don't know what you will suggest I do next but f I need to run SFCFix again and have it access my Windows 10 Repair/Install disk, what command and when and where do I need to enter it in the CMD window? Or if to be done virtually, how do I do that exactly?

19

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 07, 2017, 04:31:14 pm »

I finally found the time to run a couple virus scans, then do a full syst. backup, then run SFCFix. I ran it as administrator and selected Y to allow it to access its server for more extensive fixing capabilities. In the end it said "Source file could not be found." which is expected since this was just to rune the app. The attached DISM log file includes dates going back before today's scan. I hope you wanted all that too.

Please advise.

20

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 03, 2017, 02:15:26 pm »

Ok. I have that CBS Log folder already and checked it and it has several files in it now. In it, there's a CBS.log, a couple CBSPersist ... .cab, a couple CBSPersist ... .log and a Filterlist.log files. When I run the regular SFC /scannow in CMD (Admin) what will be the file it produces which I need to post and also what will be the file after the SFCFix.exe run that I need to post?

21

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: February 03, 2017, 12:11:07 pm »

For some reason I didn't get the notification about your reply. When I went to the site just now I had to go through a process to confirm I'm not a robot and once in, the notifications show  that they are set to be sent to me. (???)

I think the steps are pretty clear now. I'll do a backup tonight then give them a try over the weekend and report afterwards. I really hope they work.

22

General Computer Support / Re: Win. 10 Repair/Replace Corrupted Files

« on: January 31, 2017, 01:27:42 pm »

Thanks Boggin. I want to be sure I do this right so let me ask you for some clarifications. My C: drive is my local drive which has the corrupted system files and my D: drive is my DVD drive, which is where I will be inserting any disks for this repair.

1- The "install disk" you refer to is the "Win 10 RepairInstall with an In-Place Upgrade" disk which I created by burning the file I downloaded from Microsoft, correct?

2- You said to "... change/confirm the Time and currency format...". I don't get this. It sounds like I'm buying something. Please explain about the currency.

3- By the command prompt, you mean the Command Prompt (Admin)?

4- Here are the two lines you said to enter in the command prompt window. I've written them as per my system with an underscore (_) to represent a blank space and I will enter them exactly as shown here. Please let me know if I have them written correctly:

bcdedit_|find_"osdevice"

sfc_/scannow_/offbootdir=D:\_/offwindir=D:\Windows

5- You stated "You can get the latest disk by clicking on the Download tool now button in https://www.microsoft.com/en-gb/software-download/windows10 or hit the Update now button." This is the same disk previously mentioned in 1- above?

23

General Computer Support / Win. 10 Repair/Replace Corrupted Files

« on: January 30, 2017, 03:04:03 pm »

Hell everyone, Just joined.

I tried the All-In-One, twice, and it didn't solve my problem. I've searched the forum and see a couple related posts but being an intermediate user I want to ask first so I don't make things worse.

A brief summary: Several months ago I upgraded from Win. 7 Ultimate (64) to Win. 10 Pro and everything was ok. About two months ago some crashes unltimately indicated that my local HDD was failing which was confirmed by Hard Drive Sentinel afterwards. I then cloned my local drive with AOMEI Backupper to a new HDD of the same WD make and model and total disaster was avoided. However, the failing HDD developed 10 bad sectors of which a couple were non repairable and this apparently corrupted some system code. Since the cloning, every attempt to update my v1511 to cummulative update v1604 fails, error: 0x80073712. SFC /scannow scans result with "... some corrupt files could not be fixed...". I've separated my data files off my local drive to a separate external backup drive to make more free space, now at about 150GB. I've also tried repair-installs from disk and also fro local virtual HDD and at 33% completion they always fail. Fortunately, my system runs ok generally and most software can be installed. Sometimes it crashes to the blue screen but always reboots ok. Although it fails to update the OS, the security updates do seem to be updating ok.

The only fix I can think of at this point, with my limited knowledge, is to provide this forum with the SFC scan log showing the corrupted files. Then you identify which ones need replacing so at least the update or repair-install will complete. I have no idea how to replace system files so I'd need your instructions. Or maybe there's a simpler fix you may know about?

Many thanks.