Author Topic: Win. 10 Repair/Replace Corrupted Files  (Read 27506 times)

0 Members and 1 Guest are viewing this topic.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #25 on: February 11, 2017, 02:44:09 PM »
No - he will have received the email notification of your reply but weekends tend to be taken up with family life.

We are volunteers on the forum.
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #26 on: February 13, 2017, 09:48:50 AM »
Ok, ... standing by for Julian then.
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #27 on: February 13, 2017, 04:08:06 PM »
I've given Julian a Bump PM, but his work commitments may delay his return.

As you have posted the results of the Pre-Scan, I'd go ahead with the fix button and then do another Pre-Scan to see if it has resolved them, but the Checksur log's report of duplicate ownership and manifest corruption may override those.

When you tried the repair installs, did you disable your antivirus program beforehand ?
Tom.

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1321
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #28 on: February 13, 2017, 10:26:42 PM »
well dang... that was not what i wanted to see okay lets see windows 10 done sfc /scan now already....
let's try this do these 2 commands one at a time let them finish before moving on. (may take awhile to complete.)

DISM /Online /Cleanup-image /Scanhealth

DISM /Online /Cleanup-image /Restorehealth
Julian

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #29 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.
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #30 on: February 15, 2017, 07:55:35 AM »
What antivirus programs do you have installed ?
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #31 on: February 15, 2017, 08:07:24 AM »
Malwarebytes & Superantispyware
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #32 on: February 15, 2017, 08:33:08 AM »
I was wanting to check as running more than one AV program can cause anomalous problems, but they aren't AV programs.

MBAM is okay as a scanner but SAS is a load of crap - all it ever finds are cookies.

As you don't have a 3rd party antivirus program installed then Windows Defender should be running.

To check, right click on the Start button - Control Panel - System and Security/Review your computer's status and expand Security.

Can you run this dism cmd which will tell you if the volume is repairable -

dism /online /cleanup-image /checkhealth

If it says it is then enter this one which can take a while to run then do the /restorehealth one again.

dism /online /cleanup-image /startcomponentcleanup

Follow the /restorehealth one with another sfc /scannow to see if it reports corruption it is unable to repair.

If it does then enter this cmd to put the CBS log into an icon onto your desktop - double click on it then copy & paste into the reply box..

(you can copy & paste this cmd to the cmd prompt to avoid any typos)

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

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #33 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         
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #34 on: February 16, 2017, 12:35:58 AM »
Go back to my first reply to boot up with the install disk and perform an offboot sfc /scannow.

If that doesn't do it then I don't think you will have any other option but to do a clean install.
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #35 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?
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #36 on: February 16, 2017, 08:41:46 AM »
No, you need to go into the BIOS to change the Boot order so that it checks the disk drive first.

If it at first ignores it and boots normally to Windows then you will need to turn off fast start up in the Power Options.

You can get into the BIOS by in Windows, by pressing and holding F2 throughout a Restart until the BIOS appears on the screen.

Use your cursor keys to move along to the Boot tab then use the cursor keys again to select the CD/DVD drive, using F5 or F6 to move it to the top.

Insert the disk then press F10 to Save and Exit - press enter to confirm.

You should be momentarily prompted to press any key to boot from CD/DVD and when you get the Install screen, select Repair your computer.

You may get a window popping up about having booted up with an install disk to perform a custom install and if you intended to just do a repair install, then to insert the disk after booting up Windows - just proceed as for the custom install where you will see the link to Repair your computer down on the left.

You get pretty much the same menu as you would if you had gone in through Settings/Update & Security/Recovery to select the Command Prompt.

It won't produce a CBS log.
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #37 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?
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #38 on: February 16, 2017, 01:36:34 PM »
Yes - what happens is that you are booting up outside of Windows by booting up with the install disk and that cmd will then check your installed volume against the incorrupt source of the disk and repair as necessary.

I think it is the level of manifest corruption that is stopping you from performing a repair install.

While a sfc /scannow doesn't scan all files as I've been told by Shane, hopefully the offboot one will repair your corrupt volume.

When complete, enter exit to close the cmd window, remove the disk then restart.

If it has accomplished anything then a normal sfc /scannow should come up clean - otherwise it's the clean install.
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #39 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.
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #40 on: February 16, 2017, 02:59:32 PM »
When you boot up with the install disk you will be momentarily prompted to press any key to boot from CD/DVD.

Use the dropdown to change/confirm the Time and currency format then click on Repair your computer down on the left.

You may get an alert pop up to say that you have booted up with an install disk to perform a custom install, but if you just want to perform a repair install, then boot up Windows normally and then insert the disk - or words to that effect.

If you do then just proceed as for a custom install and then click on Repair your computer.

After clicking on Repair your computer click on Troubleshoot then on Command Prompt and enter that cmd - without the underscores.

Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #41 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?
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #42 on: February 17, 2017, 02:26:31 PM »
No, the x: prompt is the one you use.

I'm not sure if these cmds will work outside of Windows but give them a go - you would normally get a success message after the first one, but enter them and if they don't return any errors then try the sfc /scannow cmd again.

sc config trustedinstaller start=auto

net start trustedinstaller
Tom.

Offline BretMan

  • Newbie
  • *
  • Join Date: Dec 2016
  • Posts: 21
  • Location: USA
  • Karma: 0
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #43 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?
Bret

OS: Windows 10 Pro (64) v1511. Gateway desktop Intel i5, ITB

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9443
  • Location: UK
  • Karma: 118
    • View Profile
Re: Win. 10 Repair/Replace Corrupted Files
« Reply #44 on: February 18, 2017, 03:18:21 PM »
You could try it but I'd be inclined to register and open a thread in the www.sysnative.com forum, posting your CBS and SFCFix.exe logs where they will probably be able to upload the manifest files for you - which I've seen them do for others.
Tom.