Boot failure after chkdsk /r No bootable image found

zbook · 14 Sep 2018

continued:

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-part-3.png

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-part-4.png

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-part-5.png

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-part-6.png

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-part-7.png

Sfc /scanow and Dism commands:

Code:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning system scan.  This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\Windows\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The component store is repairable.The operation completed successfully.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================80.0%==============            ]Error: 0x800f0906The source files could not be downloaded.Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32>

Bcdedit, diskpart disk, volume, partition, and drive letter directories:

Code:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.


C:\Windows\system32>bcdedit /enum


Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume4
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {7fb98aec-258d-11e7-b8db-8021c2dade89}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30


Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {7fb98aee-258d-11e7-b8db-8021c2dade89}
displaymessageoverride  CommandPrompt
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {7fb98aec-258d-11e7-b8db-8021c2dade89}
nx                      OptIn
bootmenupolicy          Standard


C:\Windows\system32>bcdedit | find "osdevice"
osdevice                partition=C:


C:\Windows\system32>diskpart


Microsoft DiskPart version 10.0.15063.0


Copyright (C) Microsoft Corporation.
On computer: DESKTOP-BH9NBPV


DISKPART> list disk


  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          931 GB  1024 KB
  Disk 1    Online          698 GB  2048 KB        *
  Disk 2    Online         3726 GB      0 B        *
  Disk 3    Online           29 GB      0 B


DISKPART> list volume


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   System Rese  NTFS   Partition    500 MB  Healthy
  Volume 1     F   New Volume   NTFS   Partition    931 GB  Healthy
  Volume 2     C                NTFS   Partition    698 GB  Healthy    Boot
  Volume 3         Recovery     NTFS   Partition    450 MB  Healthy    Hidden
  Volume 4                      FAT32  Partition     99 MB  Healthy    System
  Volume 5     E   Seagate Bac  NTFS   Partition   3725 GB  Healthy
  Volume 6     G                FAT32  Removable     29 GB  Healthy


DISKPART> select disk 0


Disk 0 is now the selected disk.


DISKPART> detail disk


HGST HTS721010A9E630
Disk ID: F53DF534
Type   : SATA
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   System Rese  NTFS   Partition    500 MB  Healthy
  Volume 1     F   New Volume   NTFS   Partition    931 GB  Healthy


DISKPART> list partition


  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary            500 MB  1024 KB
  Partition 2    Primary            931 GB   501 MB


DISKPART> select partition 1


Partition 1 is now the selected partition.


DISKPART> detail partition


Partition 1
Type  : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     D   System Rese  NTFS   Partition    500 MB  Healthy


DISKPART> select partition 2


Partition 2 is now the selected partition.


DISKPART> detail partition


Partition 2
Type  : 07
Hidden: No
Active: No
Offset in Bytes: 525336576


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1     F   New Volume   NTFS   Partition    931 GB  Healthy


DISKPART> select partition 3


The specified partition is not valid.
Please select a valid partition.


There is no partition selected.


DISKPART> select disk 1


Disk 1 is now the selected disk.


DISKPART> detail disk


Hitachi HTS727575A9E364
Disk ID: {8B059D16-7067-4974-88C8-26FE2E15D000}
Type   : SATA
Status : Online
Path   : 4
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C04T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     C                NTFS   Partition    698 GB  Healthy    Boot
  Volume 3         Recovery     NTFS   Partition    450 MB  Healthy    Hidden
  Volume 4                      FAT32  Partition     99 MB  Healthy    System


DISKPART> list partition


  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           450 MB  1024 KB
  Partition 2    System              99 MB   451 MB
  Partition 3    Reserved            16 MB   550 MB
  Partition 4    Primary            698 GB   566 MB


DISKPART> select partition 1


Partition 1 is now the selected partition.


DISKPART> detail partition


Partition 1
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 1048576


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3         Recovery     NTFS   Partition    450 MB  Healthy    Hidden


DISKPART> select partition 2


Partition 2 is now the selected partition.


DISKPART> detail partition


Partition 2
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 472907776


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 4                      FAT32  Partition     99 MB  Healthy    System


DISKPART> select partition 3


Partition 3 is now the selected partition.


DISKPART> detail partition


Partition 3
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 576716800


There is no volume associated with this partition.


DISKPART> select partition 4


Partition 4 is now the selected partition.


DISKPART> detail partition


Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 593494016


  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2     C                NTFS   Partition    698 GB  Healthy    Boot


DISKPART> exit


Leaving DiskPart...


C:\Windows\system32>d:


D:\>dir
 Volume in drive D is System Reserved
 Volume Serial Number is EEC5-2DC6


 Directory of D:\


09/08/2018  11:39 PM               301 rescuepe.log
09/11/2018  11:03 AM    <DIR>          swsetup
               1 File(s)            301 bytes
               1 Dir(s)     368,013,312 bytes free


D:\>e:


E:\>dir
 Volume in drive E is Seagate Backup Plus Drive
 Volume Serial Number is 2C3D-0277


 Directory of E:\


09/14/2018  01:33 PM    <DIR>          extra backup folders from 750 GB HD
09/14/2018  11:38 AM    <DIR>          Local Disk
07/15/2017  07:09 AM    <DIR>          Start_Here_Mac.app
05/09/2016  07:29 PM        18,010,688 Start_Here_Win.exe
09/05/2018  09:16 AM    <DIR>          Users
01/08/2015  05:13 PM         1,146,400 Warranty.pdf
               2 File(s)     19,157,088 bytes
               4 Dir(s)  3,595,741,278,208 bytes free


E:\>f:


F:\>dir
 Volume in drive F is New Volume
 Volume Serial Number is 6EA5-537F


 Directory of F:\


07/18/2018  03:22 AM   225,784,262,406 9F42B29DBE553E79-00-00.mrimg
11/30/2017  02:41 AM    <DIR>          backup 11 30 2017 G0
11/30/2017  02:01 AM    <DIR>          backup 11 30 2017 SSD
03/15/2018  01:50 AM             4,018 macrium EFI chkdsk r 3 15 2018.txt
12/02/2006  01:37 AM           904,704 msdia80.dll
04/18/2017  10:04 PM    <DIR>          Owner
03/14/2018  04:55 PM    <DIR>          user 3 14 2018
               3 File(s) 225,785,171,128 bytes
               4 Dir(s)  79,714,226,176 bytes free


F:\>g:


G:\>dir
 Volume in drive G has no label.
 Volume Serial Number is C48D-6BEF


 Directory of G:\


12/13/2016  07:27 AM    <DIR>          Boot
11/08/2016  12:32 PM    <DIR>          EFI
01/15/2017  10:35 PM                 0 Win10PE.cd
05/18/2016  10:30 AM           393,720 bootmgr
05/18/2016  10:30 AM         1,131,496 bootmgr.efi
11/08/2016  12:32 PM    <DIR>          en-us
01/15/2017  10:28 PM             1,095 pecmdExt.ini
01/16/2017  11:23 PM    <DIR>          sources
               4 File(s)      1,526,311 bytes
               4 Dir(s)  30,071,095,296 bytes free


G:\>c:


C:\Windows\System32>

DESKTOP-BH9NBPV-(2018-09-14_18-57-30).zip

zbook · 14 Sep 2018

These were from the beta log collector logs:

Code:

Event[554]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2018-09-14T17:45:36.208
  Event ID: 1213
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-BH9NBPV
  Description: 
Repaired the corrupted files from backup.

Code:

Event[551]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2018-09-14T17:45:36.208
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-BH9NBPV
  Description: 
Startup Repair successfully completed repairs.

Code:

Event[386]:
  Log Name: Application
  Source: ESENT
  Date: 2018-09-14T18:57:25.875
  Event ID: 544
  Task: Database Page Cache
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
Catalog Database (3424) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 24940544 (0x00000000017c9000) (database page 6088 (0x17C8)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1). 
The flush state on database page 6088 (0x17C8) was 1 while the flush state on flush map page 0 (0x0) was 3. 
If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Code:

Event[383]:
  Log Name: Application
  Source: ESENT
  Date: 2018-09-14T18:57:00.543
  Event ID: 467
  Task: Database Corruption
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
svchost (3160) SRUJet: Database C:\Windows\system32\SRU\SRUDB.dat: Index UserIdTimeStamp of table {973F5D5C-1D90-4944-BE8E-24B94231A174} is corrupted (0).
Event[384]:
  Log Name: Application
  Source: ESENT
  Date: 2018-09-14T18:57:00.872
  Event ID: 474
  Task: Database Page Cache
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
svchost (3160) SRUJet: The database page read from the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 6578176 (0x0000000000646000) (database page 1605 (0x645)) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch.  The stored checksum was [44bf19b1bb40e64e] and the computed checksum was [00000645c440ae80].  The read operation will fail with error -1018 (0xfffffc06).  If this condition persists then please restore the database from a previous backup.  This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Code:

Event[381]:
  Log Name: Application
  Source: ESENT
  Date: 2018-09-14T18:57:00.165
  Event ID: 447
  Task: Database Corruption
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
svchost (3160) SRUJet: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 26, PgnoRoot: 160) of database C:\Windows\system32\SRU\SRUDB.dat (1522 => 288, 909).
Event[382]:
  Log Name: Application
  Source: ESENT
  Date: 2018-09-14T18:57:00.395
  Event ID: 447
  Task: Database Corruption
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
svchost (3160) SRUJet: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 24, PgnoRoot: 176) of database C:\Windows\system32\SRU\SRUDB.dat (5550 => 2900, 4070).

Somehow the 6th automatic startup repair worked:
This was the Srttrail.txt

Code:

Startup Repair diagnosis and repair log---------------------------
Last successful boot time: ‎7/‎26/‎2018 9:55:23 AM (GMT)
Number of repair attempts: 6


Session details
---------------------------
System Disk = \Device\Harddisk1
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 1


Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms


Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 359 ms


Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms


Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms


Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms


Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 93 ms


Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 2000 ms


Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 188 ms


Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 1906 ms


Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 375 ms


Test Performed: 
---------------------------
Name: Access control test
Result: Completed successfully. Error code =  0x0
Time taken = 6063 ms


Test Performed: 
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code =  0x0
Time taken = 130218 ms


Test Performed: 
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Fallback diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Root cause found: 
---------------------------
Unspecified changes to system configuration might have caused the problem.


Repair action: 
Result: Failed. Error code =  0x32
Time taken = 453 ms


Repair action: System files integrity check and repair
Result: Completed successfully. Error code =  0x0
Time taken = 1345484 ms


---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk1
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 0


Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms


Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 359 ms


Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 828 ms


Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 359 ms


Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 32 ms


Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 11203 ms


Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms


Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 172 ms


Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 1953 ms


Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 516 ms


---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 0


Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms


Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 360 ms


Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 890 ms


Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms


Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 344 ms


Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms


Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 5781 ms


Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =

The advanced recovery command: reset with save files had failed
This was from the Panther setuperr log: C:\$sysreset\log

Code:

2018-09-14 16:14:12, Error                        0x80070003 in PushButtonReset::RegKey::HasValue (base\reset\util\src\registry.cpp:187): Failed to load subkey at [Microsoft\Windows\Signature][gle=0x00000002]2018-09-14 16:14:48, Error                        [sysreset.exe]  (WinRE)WinReIsInstalledOnSystemPartitionInternal() Invalid parameters
2018-09-14 16:16:15, Error                        GetEnrollmentsOfTypes 0x80070002[gle=0x00000002]
2018-09-14 16:25:27, Error                 CSI    00000a75 (F) Baseline file missing missing on generating delta for: [l:16]'AppVShNotify.exe'[gle=0x80004005]
2018-09-14 16:25:27, Error                 CSI    00000a76@2018/9/15:00:25:27.737 (F) onecore\base\wcp\componentstore\deltastore.cpp(3238): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::RecursivelyRegenerateComponentPayload expression: (null)
[gle=0x80004005]
2018-09-14 16:25:28, Error                 CSI    00000a77 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #10106842# from CFileInstaller::DoComponentOperation(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a78 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #10106841# from CFileInstaller::ProcessComponentChange(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a79 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #10106840# from PrimitiveInstaller::CCoordinator::ProcessChange(Change (null) -> 10.0.15063.0 for Microsoft-Windows-AppManagement-AppVClient, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35})[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a7b (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #7437281# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a7c (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #7437280# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a7d (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #7437279# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a7e (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #7437278# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd015001a]
2018-09-14 16:25:28, Error                 CSI    00000a7f (F) HRESULT_FROM_WIN32(14098) #7386614# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80073712]
2018-09-14 16:25:28, Error                 CSI    00000a80 (F) HRESULT_FROM_WIN32(14098) #7297317# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_Analyze(Flags = 0, riid = {7a8b78de-d107-46ca-812b-8e3f1c163270}, ppUnk = NULL, disp = 0)[gle=0x80073712]
2018-09-14 16:25:28, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-14 16:25:28, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-14 16:25:29, Error                 SP     CReconstructOS::ReconstructWindows: ::ReconstructWindows failed: 0x80073712
2018-09-14 16:25:29, Error                 SP     CReconstructOS::DoExecute: Servicing stack failed to reconstruct OS: 0x80073712
2018-09-14 16:25:29, Error                 SP     Operation failed: Reconstruct OS from Packages. Error: 0x80073712[gle=0x000000b7]
2018-09-14 16:25:29, Error                        0x80004005 in PushButtonReset::OpExecSetup::InternalExecute (base\reset\engine\operations\src\execsetup.cpp:1411): Operation execution failed: System State: [4][gle=0x000000b7]
2018-09-14 16:25:29, Error                        0x80004005 in PushButtonReset::Operation::Execute (base\reset\engine\exec\src\operation.cpp:480): Internal failure in subtype execution routine[gle=0x000000b7]
2018-09-14 16:25:29, Error                        0x80004005 in PushButtonReset::Executer::Execute (base\reset\engine\exec\src\executer.cpp:366): Internal error while executing operation[gle=0x00000002]
2018-09-14 16:25:29, Error                        0x80004005 in ResetExecute (base\reset\engine\dll\clientapi.cpp:1193): Failed to execute offline operation queue[gle=0x00000002]
2018-09-14 16:38:18, Error                        0x80004005 in srRefreshMain (base\reliability\recovery\sysreset\sysreset.cpp:1983): [gle=0x00000057]
2018-09-14 16:38:18, Error                        wWinMain: srRefreshMain failed: 0x80004005

dism log:

Code:

2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 DismApi.dll:                                            - DismInitializeInternal2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 DismApi.dll:                                            - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 DismApi.dll: Version 10.0.15063.0 - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 DismApi.dll: Parent process command line: C:\Windows\system32\CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun -cv:9ngtO5kvakmY31Nb.1 - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Enter DismInitializeInternal - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Initialized GlobalConfig - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Initialized SessionTable - DismInitializeInternal
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=1924 Waiting for m_pInternalThread to start - CCommandThread::Start
2018-09-14 17:55:05, Info                  DISM   API: PID=5632 TID=7836 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 17:55:06, Info                  DISM   API: PID=5632 TID=7836 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 17:55:06, Info                  DISM   API: PID=5632 TID=1924 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2018-09-14 17:55:06, Info                  DISM   API: PID=5632 TID=1924 m_pInternalThread started - CCommandThread::Start
2018-09-14 17:55:06, Info                  DISM   API: PID=5632 TID=1924 Created g_internalDismSession - DismInitializeInternal
2018-09-14 17:55:06, Info                  DISM   API: PID=5632 TID=1924 Leave DismInitializeInternal - DismInitializeInternal
2018-09-14 17:55:07, Info                  DISM   API: PID=5632 TID=1924 Enter DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 17:55:07, Info                  DISM   API: PID=5632 TID=1924 Input parameters: ImagePath: DISM_{53BFAE52-B167-4E2F-A258-0A37B57FF845}, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2018-09-14 17:55:09, Info                  DISM   API: PID=5632 TID=1924 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath
2018-09-14 17:55:13, Info                  DISM   API: PID=5632 TID=1924 Waiting for m_pInternalThread to start - CCommandThread::Start
2018-09-14 17:55:13, Info                  DISM   API: PID=5632 TID=4052 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 17:55:13, Info                  DISM   API: PID=5632 TID=4052 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 17:55:13, Info                  DISM   API: PID=5632 TID=1924 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2018-09-14 17:55:14, Info                  DISM   API: PID=5632 TID=1924 m_pInternalThread started - CCommandThread::Start
2018-09-14 17:55:14, Info                  DISM   API: PID=5632 TID=1924 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 17:55:14, Info                  DISM   API: PID=5632 TID=4052 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 17:55:14, Info                  DISM   API: PID=5632 TID=4052 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 17:55:16, Info                  DISM   PID=5632 TID=4052 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2018-09-14 17:55:16, Info                  DISM   PID=5632 TID=4052 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2018-09-14 17:55:16, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:55:17, Info                  DISM   PID=5632 TID=4052 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2018-09-14 17:55:18, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:55:18, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 17:55:18, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:55:18, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:55:19, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:55:19, Info                  DISM   DISM Manager: PID=5632 TID=4052 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-09-14 17:55:19, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-14 17:55:19, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:20, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:21, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:22, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:23, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:23, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Connecting to the provider located at C:\Windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:55:23, Warning               DISM   DISM Provider Store: PID=5632 TID=4052 Failed to Load the provider: C:\Windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 17:55:23, Warning               DISM   DISM Provider Store: PID=5632 TID=4052 Failed to Load the provider: C:\Windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
[5632] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[5632] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[5632] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 17:55:24, Info                  DISM   DISM WIM Provider: PID=5632 TID=4052 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 17:55:25, Info                  DISM   DISM VHD Provider: PID=5632 TID=4052 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 17:55:25, Info                  DISM   DISM VHD Provider: PID=5632 TID=4052 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 17:55:25, Info                  DISM   DISM Imaging Provider: PID=5632 TID=4052 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[5632] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[5632] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[5632] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 17:55:26, Info                  DISM   DISM WIM Provider: PID=5632 TID=4052 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 17:55:26, Info                  DISM   DISM Imaging Provider: PID=5632 TID=4052 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2018-09-14 17:55:26, Info                  DISM   DISM Imaging Provider: PID=5632 TID=4052 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2018-09-14 17:55:26, Info                  DISM   DISM Manager: PID=5632 TID=4052 physical location path: C:\ - CDISMManager::CreateImageSession
2018-09-14 17:55:26, Info                  DISM   DISM Manager: PID=5632 TID=4052 Event name for current DISM session is Global\{50D9CCC3-74C9-468E-8BF6-F1C0061D0EF2} - CDISMManager::CheckSessionAndLock
2018-09-14 17:55:26, Info                  DISM   DISM Manager: PID=5632 TID=4052 Create session event 0x89c for current DISM session and event name is Global\{50D9CCC3-74C9-468E-8BF6-F1C0061D0EF2}  - CDISMManager::CheckSessionAndLock
2018-09-14 17:55:27, Info                  DISM   DISM Manager: PID=5632 TID=4052 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2018-09-14 17:56:08, Info                  DISM   DISM Manager: PID=5632 TID=4052 Successfully loaded the ImageSession at "C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57" - CDISMManager::LoadRemoteImageSession
2018-09-14 17:56:08, Info                  DISM   DISM Image Session: PID=7164 TID=6108 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-09-14 17:56:08, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:56:08, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Connecting to the provider located at C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:56:08, Info                  DISM   DISM OS Provider: PID=7164 TID=6108 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-09-14 17:56:08, Info                  DISM   DISM OS Provider: PID=7164 TID=6108 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-09-14 17:56:08, Info                  DISM   DISM OS Provider: PID=7164 TID=6108 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2018-09-14 17:56:08, Warning               DISM   DISM OS Provider: PID=7164 TID=6108 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2018-09-14 17:56:08, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:56:09, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Connecting to the provider located at C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:56:09, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:56:09, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 17:56:09, Warning               DISM   DISM Provider Store: PID=7164 TID=6108 Failed to Load the provider: C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 17:56:09, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:56:09, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 17:56:09, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:56:09, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:56:09, Info                  DISM   DISM Manager: PID=5632 TID=4052 Image session successfully loaded from the temporary location: C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57 - CDISMManager::CreateImageSession
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=4052 Target image information: OS Version=10.0.15063.724, Image architecture=amd64 - CDismCore::LogImageSessionDetails
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=1924 Leave DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=1924 Session id is: 2 - DismOpenSessionInternal
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=1924 Enter DismGetDriverInfoInternal - DismGetDriverInfoInternal
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=1924 Input parameters: Session: 2, DriverPath: oem7.inf - DismGetDriverInfoInternal
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=1924 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 17:56:09, Info                  DISM   API: PID=5632 TID=4052 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:10, Info                  DISM   API: PID=5632 TID=4052 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 17:56:10, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Connecting to the provider located at C:\Windows\TEMP\3CC15BFE-3347-4280-91CF-C9E1974D1E57\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:56:10, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 17:56:10, Info                  DISM   DISM OS Provider: PID=7164 TID=6108 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-09-14 17:56:10, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-09-14 17:56:10, Error                 DISM   DISM Driver Manager: PID=7164 TID=6108 Error, file not found 'oem7.inf'. - CDriverManager::OpenPackageByFile(hr:0x80070002)
2018-09-14 17:56:11, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2018-09-14 17:56:11, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Leave DismGetDriverInfoInternal - DismGetDriverInfoInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Enter DismGetDriverInfoInternal - DismGetDriverInfoInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Input parameters: Session: 2, DriverPath: C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf - DismGetDriverInfoInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=4052 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=4052 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 17:56:12, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2018-09-14 17:56:12, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2018-09-14 17:56:12, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2018-09-14 17:56:12, Info                  DISM   DISM Driver Manager: PID=7164 TID=6108 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\iaahcic.inf_amd64_b4ae13c6e6218d1b\iaahcic.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Leave DismGetDriverInfoInternal - DismGetDriverInfoInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Enter DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Leave DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Enter DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:12, Info                  DISM   API: PID=5632 TID=1924 Leave DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:13, Info                  DISM   API: PID=5632 TID=1924 Enter DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:13, Info                  DISM   API: PID=5632 TID=1924 Leave DismDeleteInternal - DismDeleteInternal
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=5676 Enter DismCloseSessionInternal - DismCloseSessionInternal
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=5676 Input parameters: Session: 2 - DismCloseSessionInternal
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=5676 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=5676 Refcount for DismSession= 2s 0 - CSessionTable::RemoveSession
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=5676 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=4052 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:23, Info                  DISM   API: PID=5632 TID=4052 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 17:56:24, Info                  DISM   API: PID=5632 TID=4052 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:24, Info                  DISM   API: PID=5632 TID=4052 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=7164 TID=6108 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Manager: PID=5632 TID=4052 Closing session event handle 0x89c - CDISMManager::CloseImageSession
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   DISM Provider Store: PID=5632 TID=4052 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 17:56:24, Info                  DISM   API: PID=5632 TID=4052 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 17:56:24, Info                  DISM   API: PID=5632 TID=5676 Leave DismCloseSessionInternal - DismCloseSessionInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Enter DismShutdownInternal - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=7836 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=7836 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=7836 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=7836 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 17:56:25, Info                  DISM   PID=5632 TID=7836 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2018-09-14 17:56:25, Info                  DISM   PID=5632 TID=7836 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2018-09-14 17:56:25, Info                  DISM   PID=5632 TID=7836 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2018-09-14 17:56:25, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=7836 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Deleted g_internalDismSession - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Shutdown SessionTable - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 Leave DismShutdownInternal - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 DismApi.dll:                                          - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2018-09-14 17:56:25, Info                  DISM   API: PID=5632 TID=5676 DismApi.dll:                                          - DismShutdownInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 DismApi.dll:                                            - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 DismApi.dll:                                            - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 DismApi.dll: Version 10.0.15063.0 - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 DismApi.dll: Parent process command line: C:\Windows\system32\cleanmgr.exe /autoclean /d C: - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Enter DismInitializeInternal - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Initialized GlobalConfig - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Initialized SessionTable - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Waiting for m_pInternalThread to start - CCommandThread::Start
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=9384 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=9384 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 m_pInternalThread started - CCommandThread::Start
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Created g_internalDismSession - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Leave DismInitializeInternal - DismInitializeInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Enter DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Input parameters: ImagePath: DISM_{53BFAE52-B167-4E2F-A258-0A37B57FF845}, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Waiting for m_pInternalThread to start - CCommandThread::Start
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=8372 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=8372 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 m_pInternalThread started - CCommandThread::Start
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=10140 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=8372 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 18:30:12, Info                  DISM   API: PID=8048 TID=8372 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 18:30:12, Info                  DISM   PID=8048 TID=8372 Scratch directory set to 'C:\Users\aaaaaaa\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-09-14 18:30:12, Info                  DISM   PID=8048 TID=8372 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2018-09-14 18:30:12, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:30:12, Info                  DISM   PID=8048 TID=8372 Successfully loaded the ImageSession at "C:\Windows\system32\Dism" - CDISMManager::LoadLocalImageSession
2018-09-14 18:30:12, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:30:12, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:30:12, Info                  DISM   DISM Manager: PID=8048 TID=8372 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Connecting to the provider located at C:\Windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:12, Warning               DISM   DISM Provider Store: PID=8048 TID=8372 Failed to Load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:30:12, Warning               DISM   DISM Provider Store: PID=8048 TID=8372 Failed to Load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
[8048] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[8048] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[8048] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 18:30:12, Info                  DISM   DISM WIM Provider: PID=8048 TID=8372 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 18:30:12, Info                  DISM   DISM VHD Provider: PID=8048 TID=8372 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 18:30:12, Info                  DISM   DISM VHD Provider: PID=8048 TID=8372 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 18:30:12, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[8048] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[8048] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[8048] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 18:30:12, Info                  DISM   DISM WIM Provider: PID=8048 TID=8372 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 18:30:12, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2018-09-14 18:30:12, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2018-09-14 18:30:12, Info                  DISM   DISM Manager: PID=8048 TID=8372 physical location path: C:\ - CDISMManager::CreateImageSession
2018-09-14 18:30:12, Info                  DISM   DISM Manager: PID=8048 TID=8372 Event name for current DISM session is Global\{5139FBD2-D606-4CB9-A9D3-4A7CAD28C658} - CDISMManager::CheckSessionAndLock
2018-09-14 18:30:12, Info                  DISM   DISM Manager: PID=8048 TID=8372 Create session event 0x620 for current DISM session and event name is Global\{5139FBD2-D606-4CB9-A9D3-4A7CAD28C658}  - CDISMManager::CheckSessionAndLock
2018-09-14 18:30:12, Info                  DISM   DISM Manager: PID=8048 TID=8372 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2018-09-14 18:30:47, Info                  DISM   DISM Manager: PID=8048 TID=8372 Successfully loaded the ImageSession at "C:\Users\aaaaaaa\AppData\Local\Temp\98C36D3C-2917-48B7-B79C-EB705841C344" - CDISMManager::LoadRemoteImageSession
2018-09-14 18:30:47, Info                  DISM   DISM Image Session: PID=9256 TID=5360 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-09-14 18:30:47, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:30:57, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\98C36D3C-2917-48B7-B79C-EB705841C344\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:30:57, Info                  DISM   DISM OS Provider: PID=9256 TID=5360 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:30:57, Info                  DISM   DISM OS Provider: PID=9256 TID=5360 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:30:57, Info                  DISM   DISM OS Provider: PID=9256 TID=5360 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2018-09-14 18:30:57, Warning               DISM   DISM OS Provider: PID=9256 TID=5360 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:30:57, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:30:58, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\98C36D3C-2917-48B7-B79C-EB705841C344\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:31:00, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:31:00, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:31:00, Warning               DISM   DISM Provider Store: PID=9256 TID=5360 Failed to Load the provider: C:\Users\aaaaaaa\AppData\Local\Temp\98C36D3C-2917-48B7-B79C-EB705841C344\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:31:00, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:31:00, Info                  DISM   DISM Provider Store: PID=9256 TID=5360 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:31:00, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:31:00, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:31:00, Info                  DISM   DISM Manager: PID=8048 TID=8372 Image session successfully loaded from the temporary location: C:\Users\aaaaaaa\AppData\Local\Temp\98C36D3C-2917-48B7-B79C-EB705841C344 - CDISMManager::CreateImageSession
2018-09-14 18:31:00, Info                  DISM   API: PID=8048 TID=8372 Target image information: OS Version=10.0.15063.724, Image architecture=amd64 - CDismCore::LogImageSessionDetails
2018-09-14 18:31:00, Info                  DISM   API: PID=8048 TID=10140 Leave DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 18:31:00, Info                  DISM   API: PID=8048 TID=10140 Session id is: 2 - DismOpenSessionInternal
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=10140 DismInitialize: 2 - DismInitializeInternal
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=10140 Enter DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=10140 Input parameters: ImagePath: DISM_{53BFAE52-B167-4E2F-A258-0A37B57FF845}, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=10140 Returning existing DismSession=2 for path DRIVE_C. RefCount=2 - CSessionTable::CreateSession
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=10140 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=8372 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-09-14 18:31:05, Info                  DISM   API: PID=8048 TID=8372 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-09-14 18:31:05, Info                  DISM   DISM Provider Store: PID=8048 TID=8372 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[8048] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[8048] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[8048] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 18:31:05, Info                  DISM   DISM WIM Provider: PID=8048 TID=8372 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 18:31:05, Info                  DISM   DISM VHD Provider: PID=8048 TID=8372 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 18:31:05, Info                  DISM   DISM VHD Provider: PID=8048 TID=8372 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2018-09-14 18:31:05, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[8048] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[8048] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[8048] [0xc142011c] WIMGetMountedImageHandle:(2893)
2018-09-14 18:31:05, Info                  DISM   DISM WIM Provider: PID=8048 TID=8372 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2018-09-14 18:31:05, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2018-09-14 18:31:05, Info                  DISM   DISM Imaging Provider: PID=8048 TID=8372 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2018-09-14 18:31:06, Info                  DISM   API: PID=8048 TID=8372 Target image information: OS Version=10.0.15063.724, Image architecture=amd64 - CDismCore::LogImageSessionDetails
2018-09-14 18:31:06, Info                  DISM   API: PID=8048 TID=10140 Leave DismOpenSessionInternal - DismOpenSessionInternal
2018-09-14 18:31:06, Info                  DISM   API: PID=8048 TID=10140 Session id is: 2 - DismOpenSessionInternal
2018-09-14 18:34:26, Info                  DISM   PID=7244 TID=6072 Scratch directory set to 'C:\Users\aaaaaaa\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-09-14 18:34:26, Info                  DISM   PID=7244 TID=6072 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   PID=7244 TID=6072 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: 
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: 
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.15063, Running architecture=amd64, Number of processors=8
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.15063.0
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: Executing command line: dism  /online /cleanup-image /scanhealth
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 physical location path: C:\ - CDISMManager::CreateImageSession
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Event name for current DISM session is Global\{E159E664-387C-4168-B75D-113BB187D751} - CDISMManager::CheckSessionAndLock
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Create session event 0x180 for current DISM session and event name is Global\{E159E664-387C-4168-B75D-113BB187D751}  - CDISMManager::CheckSessionAndLock
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Successfully loaded the ImageSession at "C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC" - CDISMManager::LoadRemoteImageSession
2018-09-14 18:34:26, Info                  DISM   DISM Image Session: PID=888 TID=2720 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:26, Info                  DISM   DISM OS Provider: PID=888 TID=2720 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM OS Provider: PID=888 TID=2720 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM OS Provider: PID=888 TID=2720 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2018-09-14 18:34:26, Warning               DISM   DISM OS Provider: PID=888 TID=2720 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:34:26, Warning               DISM   DISM Provider Store: PID=888 TID=2720 Failed to Load the provider: C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:34:26, Info                  DISM   DISM Manager: PID=7244 TID=6072 Image session successfully loaded from the temporary location: C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC - CDISMManager::CreateImageSession
2018-09-14 18:34:26, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.15063.724, Image architecture=amd64
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:26, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM OS Provider: PID=888 TID=2720 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-09-14 18:34:27, Info                  DISM   DISM Driver Manager: PID=888 TID=2720 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Warning               DISM   DISM Provider Store: PID=888 TID=2720 Failed to Load the provider: C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\FED4B30D-4F83-4E1E-98CE-0EE0653475CC\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:34:27, Info                  DISM   DISM Transmog Provider: PID=888 TID=2720 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-09-14 18:34:27, Info                  DISM   DISM Transmog Provider: PID=888 TID=2720 Audit Mode: [No] - CTransmogManager::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM Transmog Provider: PID=888 TID=2720 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2018-09-14 18:34:27, Info                  DISM   DISM Transmog Provider: PID=888 TID=2720 Product Type: [WinNT] - CTransmogManager::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM Transmog Provider: PID=888 TID=2720 Product Type ServerNT : [No] - CTransmogManager::Initialize
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-09-14 18:34:27, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-09-14 18:34:27, Info                  DISM   DISM Package Manager: PID=888 TID=2720 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
2018-09-14 18:46:54, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Package Manager: PID=888 TID=2720 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=888 TID=2720 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Manager: PID=7244 TID=6072 Closing session event handle 0x180 - CDISMManager::CloseImageSession
2018-09-14 18:46:54, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-09-14 18:46:54, Info                  DISM   DISM.EXE: 
2018-09-14 18:46:54, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2018-09-14 18:46:54, Info                  DISM   DISM.EXE: 
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:46:54, Info                  DISM   DISM Provider Store: PID=7244 TID=6072 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:50:35, Info                  DISM   PID=2584 TID=9704 Scratch directory set to 'C:\Users\aaaaaaa\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-09-14 18:50:35, Info                  DISM   PID=2584 TID=9704 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2018-09-14 18:50:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:35, Info                  DISM   PID=2584 TID=9704 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2018-09-14 18:50:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:35, Info                  DISM   DISM Provider Store: PID=2584 TID=9704 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:50:35, Info                  DISM   DISM Provider Store: PID=2584 TID=9704 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:35, Info                  DISM   DISM Provider Store: PID=2584 TID=9704 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:35, Info                  DISM   DISM Manager: PID=2584 TID=9704 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: 
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: 
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.15063, Running architecture=amd64, Number of processors=8
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.15063.0
2018-09-14 18:50:35, Info                  DISM   DISM.EXE: Executing command line: dism  /online /cleanup-image /restorehealth
2018-09-14 18:50:35, Info                  DISM   DISM Provider Store: PID=2584 TID=9704 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:35, Info                  DISM   DISM Manager: PID=2584 TID=9704 physical location path: C:\ - CDISMManager::CreateImageSession
2018-09-14 18:50:35, Info                  DISM   DISM Manager: PID=2584 TID=9704 Event name for current DISM session is Global\{B8609216-8F6F-4AEF-89E6-6903F296FFB9} - CDISMManager::CheckSessionAndLock
2018-09-14 18:50:35, Info                  DISM   DISM Manager: PID=2584 TID=9704 Create session event 0x188 for current DISM session and event name is Global\{B8609216-8F6F-4AEF-89E6-6903F296FFB9}  - CDISMManager::CheckSessionAndLock
2018-09-14 18:50:35, Info                  DISM   DISM Manager: PID=2584 TID=9704 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2018-09-14 18:50:36, Info                  DISM   DISM Manager: PID=2584 TID=9704 Successfully loaded the ImageSession at "C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06" - CDISMManager::LoadRemoteImageSession
2018-09-14 18:50:36, Info                  DISM   DISM Image Session: PID=9068 TID=8420 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:36, Info                  DISM   DISM OS Provider: PID=9068 TID=8420 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM OS Provider: PID=9068 TID=8420 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM OS Provider: PID=9068 TID=8420 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2018-09-14 18:50:36, Warning               DISM   DISM OS Provider: PID=9068 TID=8420 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:36, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-14 18:50:36, Warning               DISM   DISM Provider Store: PID=9068 TID=8420 Failed to Load the provider: C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-14 18:50:36, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:36, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2018-09-14 18:50:36, Info                  DISM   DISM Manager: PID=2584 TID=9704 Image session successfully loaded from the temporary location: C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06 - CDISMManager::CreateImageSession
2018-09-14 18:50:36, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.15063.724, Image architecture=amd64
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:36, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM OS Provider: PID=9068 TID=8420 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-09-14 18:50:37, Info                  DISM   DISM Driver Manager: PID=9068 TID=8420 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Warning               DISM   DISM Provider Store: PID=9068 TID=8420 Failed to Load the provider: C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Connecting to the provider located at C:\Users\aaaaaaa\AppData\Local\Temp\C0B13125-00AD-4D03-B292-55653946CD06\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-14 18:50:37, Info                  DISM   DISM Transmog Provider: PID=9068 TID=8420 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-09-14 18:50:37, Info                  DISM   DISM Transmog Provider: PID=9068 TID=8420 Audit Mode: [No] - CTransmogManager::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM Transmog Provider: PID=9068 TID=8420 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2018-09-14 18:50:37, Info                  DISM   DISM Transmog Provider: PID=9068 TID=8420 Product Type: [WinNT] - CTransmogManager::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM Transmog Provider: PID=9068 TID=8420 Product Type ServerNT : [No] - CTransmogManager::Initialize
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-09-14 18:50:37, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-09-14 18:50:37, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2018-09-14 18:50:48, Info                  DISM   DISM Package Manager: PID=9068 TID=3572  Error in operation: (null) (CBS HRESULT=0x800f0906) - CCbsConUIHandler::Error
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0906)
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0906)
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0906)
2018-09-14 18:50:48, Error                 DISM   DISM Package Manager: PID=9068 TID=8420 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)
2018-09-14 18:50:48, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:50:48, Info                  DISM   DISM Package Manager: PID=9068 TID=8420 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-14 18:50:48, Info                  DISM   DISM Provider Store: PID=9068 TID=8420 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider

There is an additional dism log file: DISMRepairLogFile.txt if needed

zbook · 15 Sep 2018

C: and D: drives are now on different disks.
C: is now on disk 1 and D: is now on disk 0.

The storage drive became disk 0.
The problematic drive is now disk 1.

The operating system and possibly the registry is corrupt.

At sometime Windows 1703 needs to be upgraded to 1803.

How do you fix the corrupt operating system and the separation of the partitions onto different disks?

EdTittel · 15 Sep 2018

Shoot, @zbook: given the situation and the presence of usable backups, I'd be inclined to wipe the drives and start over with a clean install. You can always use viboot to run the backups as VMs on a pristine new install. Is that an option for you?
Best of luck in getting this figured out. Sounds vexatious!
--Ed--

Caledon Ken · 15 Sep 2018

Good news that you are back. Likely in your BIOS is a function to enable the Intel Option Rom which allows you to control Raid as part of boot. thie is where CRTL+I comes in. I would not turn on now as you do not need the 32GB, you need your data.

Looks like the G: drive (32GB) is not in game yet. While you have access to drive I don't think the game plan should have changed. That is a clean install on the 750GB to provide you with a fresh base to build from, 1803 and soon 1809.

The issue remains, how do we get data from 750GB to a new disk to ensure it is protected and can be saved.

So you could run Macrium (Free) as you have it installed to reimage c: out to a new device, think you need at least 500GB of space. This would give you another backup of C: possibly more complete than the original (July18th) but when you copied using commands you had some errors so I'm not sure. Still I would undertake this task. Hopefully you have a 500GB drive around or you could steer it to your 4TB seagate.

At all costs DO NOT DELETE the original Macrium backup. <<<<-----------

While the new Macrium Backup could be more complete the issue remains how do you get data off. Your names are to long, you don't have a good feel for where the data is with all the re-installs and transitions so messy at best.

So what is next.

I can't remember what drive F: is. I think you copied data out to it as a "backup" weren't you. Not sure how as file copy keeps coughing up files names issues and duplicates. If you were copying out to F: I would perform that function as if nothing has happen. Please confirm that is what you were using F: for. Very long thread.

Hopefully now data will be in three places, original Macrium image, new Macrium image from above and as files on F:.

Since your file names and structure is a real issue on C: I think I would then purchase a copy of Macrium and install it. This will likely require a reboot. Make new boot media preserving old, clearly labelled. The bridge of reboot would have to be crossed at some point. Again I would not be turning on raid, data restoration is the job.

With the purchased copied of Macrium you can now deploy file folder backups. My target would then be the "Users\aaaaaa" and "users\administration" folder on C:. If you take such a backup then you are supposed to be able to restore file and folders without restoring all the questionable stuff on C: (Windows etc).

Once this folder backup is verified then with it in hand and the other three copies of your data I would vapourize C: and reinstall windows with only the 32GB and 750GB installed. (Actually I would get a large SSD and say good bye to that 32GB).

Thoughts. I have to good out this morning but will check back in. Would like to see what Ed has to say as well.

zbook · 15 Sep 2018

This is a current image of file explorer:

Boot failure after chkdsk /r No bootable image found-file-explorer-9-15-2018.png

C: drive is 750 GB HD and is the problematic drive. It is now on disk 1.
It has an old Users folder that was saved to drive F: (1 TB ) storage drive.
A Macrium image had been made of this drive with the default incremental backups that has a corrupt operating system saved to drive F: (1 TB)

D: drive is system reserved 500 MB and is on disk 0.

Code:

D:\>dir
 Volume in drive D is System Reserved
 Volume Serial Number is EEC5-2DC6

 Directory of D:\

09/08/2018  11:39 PM               301 rescuepe.log
09/11/2018  11:03 AM    <DIR>          swsetup
               1 File(s)            301 bytes
               1 Dir(s)     368,013,312 bytes free

E: drive is the external HD (4 TB)
It has a backup Users folder using Kyhi boot rescue.
It has the additional backup folders that were interrupted from post # 80.

Code:

E:\>dir
 Volume in drive E is Seagate Backup Plus Drive
 Volume Serial Number is 2C3D-0277

 Directory of E:\

09/14/2018  01:33 PM    <DIR>          extra backup folders from 750 GB HD
09/14/2018  11:38 AM    <DIR>          Local Disk
07/15/2017  07:09 AM    <DIR>          Start_Here_Mac.app
05/09/2016  07:29 PM        18,010,688 Start_Here_Win.exe
09/05/2018  09:16 AM    <DIR>          Users
01/08/2015  05:13 PM         1,146,400 Warranty.pdf
               2 File(s)     19,157,088 bytes
               4 Dir(s)  3,595,741,278,208 bytes free

F: drive is the internal storage drive (1 TB)
It has the old Users backup from the problematic C: drive
(03/14/2018 04:55 PM <DIR> user 3 14 2018)
It has the Macrium backup from the problematic C: drive

(11/30/2017 02:41 AM <DIR> backup 11 30 2017 G0)

This Macrium backup was set to use the incremental backups and likely has a corrupt operating system and registry.
This drive also has a Macrium backup image of a drive on another computer
(11/30/2017 02:01 AM <DIR> backup 11 30 2017 SSD)

Code:

F:\>dir
 Volume in drive F is New Volume
 Volume Serial Number is 6EA5-537F

 Directory of F:\

07/18/2018  03:22 AM   225,784,262,406 9F42B29DBE553E79-00-00.mrimg
11/30/2017  02:41 AM    <DIR>          backup 11 30 2017 G0
11/30/2017  02:01 AM    <DIR>          backup 11 30 2017 SSD
03/15/2018  01:50 AM             4,018 macrium EFI chkdsk r 3 15 2018.txt
12/02/2006  01:37 AM           904,704 msdia80.dll
04/18/2017  10:04 PM    <DIR>          Owner
03/14/2018  04:55 PM    <DIR>          user 3 14 2018
               3 File(s) 225,785,171,128 bytes
               4 Dir(s)  79,714,226,176 bytes free

G: drive is the Kyhi boot rescue flash drive

Code:

G:\>dir
 Volume in drive G has no label.
 Volume Serial Number is C48D-6BEF

 Directory of G:\

12/13/2016  07:27 AM    <DIR>          Boot
11/08/2016  12:32 PM    <DIR>          EFI
01/15/2017  10:35 PM                 0 Win10PE.cd
05/18/2016  10:30 AM           393,720 bootmgr
05/18/2016  10:30 AM         1,131,496 bootmgr.efi
11/08/2016  12:32 PM    <DIR>          en-us
01/15/2017  10:28 PM             1,095 pecmdExt.ini
01/16/2017  11:23 PM    <DIR>          sources
               4 File(s)      1,526,311 bytes
               4 Dir(s)  30,071,095,296 bytes free

The HP website > support and drivers was opened and the computer's product / serial number was entered.
The storage driver, Intel RST was downloaded and installed.
It requires a reboot to complete the installation and this was not done.
If the Intel RST is installed it has a performance tab with the ability to turn off acceleration and the default RAID 0 for the internal 750 GB C: and the 32 GB flash cache would then be converted to a HD that is no longer in RAID 0.
Then the drive could be moved to the secondary bay of another computer or to an external HD enclosure.
This would allow one additional method to backup data.
With all of the drives (internal storage and external storage) connected to the problematic computer the Intel RST disable acceleration may not be needed.

The plan seems to be the same to use the BIOS tool disk sanitizer to clean the C: drive.
The change was that the repair steps made the drive bootable.
Kyhi boot rescue is not needed at this time.
How stable or fragile the boot files are is unclear.
The partitions somehow (possibly with the reversal or reset save files, startup repair, chkdsk, etc) got moved to different disks.

EdTittel
As you commented the clean install is planned after the disk sanitization.
The virtual methods I'v not yet learned. And if it is not complex could be used.

Caledon Ken
The continued backups in step #80 will take substantial time.
The Users folder is likely to take 15 to 20 hours.
Should they be restarted now?
Should the new Macrium image be performed first?
If the operating system were not corrupt would you only perform a Macrium backup image then stanitize, clean install, restore an image?
Would it place the files at an unnecessary risk to attempt a Windows update at any time?
It could be the third Macrium backup image?

After the clean install Microsoft Office (old edition) needs to be reinstalled.
For the prior boot loop with windows defender offline and windows driver verifier it was easy for the Microsoft store to reinstall from the downloads folder.
Two weeks later after the backup for the failed Windows upgrade, in the same Microsoft store, they were unable to reinstall Office.
Somehow after time and many steps that I no longer remember I was able to install office.
This old edition of Microsoft can be uninstalled before the drive is sanitized.
Typically an uninstall make the next uninstall easy as the server does not get confused that it is just on one computer.
If the drive becomes unbootable again can Microsoft office be uninstalled using Kyhi boot rescue or should this be done while the boot is not problematic?

For the zbook G0 there is a problem with form factor for where the 32 GB flash cache is attached to the computer.
This can only be attached or detached and a SSD cannot fit in the same spot.

The zbook G0 has two HD bays.
The 750 GB problematic C: drive is in the primary bay and the 1000 GB storage drive is in the secondary bay.
Extra chasis I do not have but this may be the method to get a SSD drive attached to the computer.
If the internal 750 GB HD does not have chkdsk problems after the disk sanitization then it can be used as the default drive.
If this drive has recurrent chkdsk problems then I'll check into the HP drive chasis options for SSD drives.

For Macrium is there a side by side comparison link for free versus pay edition?
This is what was seen for the $70 edition:

Code:

Backup your entire PC to a single compressed image file.
Backup files and folders to a single compressed archive file.
Recover partitions and entire disk images with just a few clicks of your mouse.
MBR and GPT disk support.
12 months Essentials Support.

They have a 30 day trial.
Can the free edition be used and there if there are problems use the 30 day trial or the paid edition?
Or do you need to start with the paid edition?
Which steps would be needed in the pay edition?

What are the steps to be performed now that the drive is bootable and that there is more information from the various software?

a) Make a brand new Macrium backup to the external HD 4 TB (E: drive) ?
b) Make the additional backup folders as in the list on post # 80? (this may take 2 days as the users folder may take 15 to 20 hours)
c) Use the BIOS to perform disk sanitization?
d) Clean the flash drive that has Windows 10 1703 iso and install 1803 iso or just install the iso that will automatically overwrite the files that are already on the flash drive?
e) Macrium restore I've not yet done and need to learn the technique and any pitfalls.

Are these settings correct for the next Macrium backup image?
Once this backup image is made should there be any setting modifications for the default incremental backup images?
If so which modifications?

For the Macrium backup image that is on the 1 TB internal storage drive there should be default incremental backup images. This does not matter at this time? Or should this be modified?

Boot failure after chkdsk /r No bootable image found-macrium-settings-next-backup-image-9-15-2018.png

Caledon Ken · 15 Sep 2018

I would not perform the steps in post 80. You said you are getting names to long.

Yes I outlined exactly how I would perform the recovery.

First I would use the installed Macrium to take another complete fresh backup of C:

I would verify this backup to be sure it is usable.

Do not delete original Macrium of C:

This would give you, hopefully two copies of data, the original macrium up to July 18 and the second Macrium which should be all inclusive, should be.

You said F; has the old users backup from the problematic c: . Great

Is it complete, does F: have all your data?

As I understood it, no, you hadn't added to it in a while. So in my previous post I suggested you perform your normal activity and do what you do to get F: complete. (not sure how you are doing this with super long names but do what you normally do)

Glad you caught the Macrium Trail offer. I had over looked. Yes by all means use the trial if it will allow file / folder back ups.
Download it and install it, create boot media and then create a full backup of the users\aaaaaaa and users\administrator folders.

I assume there is no other folder on the root / hidden that contains data.

If you wish to activate the raid it is your device. Moving the drive is not really the issue. The file names being as long as the one I saw are and then there are the duplicates. I would spend some serious time getting my data in order. There are batch renaming programs that might help. That is for another day.

If the 32GB is part of device, then not much you can do to remove. You may still be able to buy a standard 2 1/2 SSD and ignore the 32GB

So complete the data copy to F: that you have been using as a backup.

Reimage the 750GB c: drive with the installed Macrium, full backup and verify.

Use the Macrium trial to preform full backups of just the Users folders and verify it.

(I might even suggest you do a test restore of a file name with an excessive length back to this "troubled drive" in a folder you create)

My thinking is once you have Windows reinstalled you will be able to restore your folders in your new account.
I'm making an assumption, if Macrium's file folder backup can back these excessively long files names then it will allow you to restore. That is why I suggested the test just above.

Ken

zbook · 15 Sep 2018

The Users backup from C: to F: was dated 3/14/2018 so it was old.
Each time that I backed up the users folder it had problems with names too long or duplicate files that had different sizes and or different dates. So at sometime a decision was made on one of the options available to complete the backup. I don't remember what choice was made at that time.

The Microsoft store had made a backup in Windows PE or RE and I don't know how they were able to do it without the same problem.

The Macrium backup of C: is on the 1 TB storage drive F:
So in the last image there were settings to make a new backup image to the 4 TB external HD.
This then is cancelled.

With the installed Macrium then use the settings to perform an incremental backup?
So there will only be one Macrium backup on drive F: and it will be an incremental backup?
What are the steps to perform an on demand incremental backup image?

The last incremental backup image on 9/14/2018 had failed with error code 0x01.

Boot failure after chkdsk /r No bootable image found-macrium-9-14-2018-last-result-0x01-error.png

In a google search it indicated that the end of the log file should be viewed.

The end of the log file displayed:
macrium backup aborted unable to read from disk error code 2 the system cannot find the file specified

Boot failure after chkdsk /r No bootable image found-macrium-log-displaying-backup-aborted-unable-read-disk.png

In a google search for this message it indicated that this may be a problem with a shadow copy?

The beta log collector collected the event viewer data and these were the entries related to shadow:

Code:

Event[697]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2018-09-14T17:53:40.366
  Event ID: 98
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-BH9NBPV
  Description: 
Volume ?? (\Device\HarddiskVolumeShadowCopy2) is healthy.  No action is needed.

Code:

Event[693]:
  Log Name: System
  Source: Volsnap
  Date: 2018-09-14T17:53:23.641
  Event ID: 33
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-BH9NBPV
  Description: 
The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

The prior Macrium log files were then viewed.
Macrium had a failed backup on 7/25/2018 displaying corruption of the MFT.
The last successful backup was 7/18/2018

Boot failure after chkdsk /r No bootable image found-macrium-mft-corrupt-7-25-2018-last-successful-backup-7-18-2018.png

How would you troubleshoot this Macrium error message from 9/14/2018?
Is it something else besides a shadow copy?
How can an incremental backup be performed on demand to see whether this was a problem that was or was not related to the environment during the most recent repair period?

zbook · 15 Sep 2018

In the Macrium other tasks menu it displayed:

Boot failure after chkdsk /r No bootable image found-macrium-tools-fix-vss-problems-9-15-2018.png

It did not display whether it does or not require a reboot.

I'll try that and see what happens.
It did not display information on how to perform an on demand incremental backup.
How is that done?

zbook · 15 Sep 2018

When the computer had failed to upgrade the system reserved partition Microsoft had created the User named Administrator so that they could perform remote access steps. At the time it was unknown what had caused the problem. Both Microsoft and HP had been contacted. Later it was determined that it was HP firmware that blocked the Windows upgrades. The user Administrator folders and files do not appear to be needed. I'm guessing that it was not just the name Administrator but a user that elevated privileges. At some time I want to learn how to create such User accounts so that if necessary troubleshooting can be performed.

Using file explorer > this PC > C: > Users > Administrator > it displayed:

Boot failure after chkdsk /r No bootable image found-user-administrator-you-dont-currently-have-permission-access-folder-click-continue-p.png

When I had used Kyhi boot rescue I don't remember seeing this prompt for permission.
I had forgotten what was seen.

Looked more into the VSS.
Macrium had a red circle with white exclamation mark near the left upper corner.
Looked backed 30 days for VSS problems and there were a very large number of ESENT problems.

Boot failure after chkdsk /r No bootable image found-macrium-vss-events-9-15-2018-30-day-range.png

Boot failure after chkdsk /r No bootable image found-macrium-vss-events-9-15-2018-30-day-range-part-2.png

Boot failure after chkdsk /r No bootable image found-macrium-vss-events-9-15-2018-30-day-range-part-3.png

Boot failure after chkdsk /r No bootable image found-macrium-vss-events-9-15-2018-30-day-range-part-4.png

Boot failure after chkdsk /r No bootable image found-macrium-vss-events-9-15-2018-30-day-range-part-5.png

In the DM log collector it only collects the system-events.
In the BETA log collector it collects:
application-events
pnp-events
system-events
The ESENT problems were in the application-events.
These were not troubleshooted when using the DM log collector as they were not seen.
Troubleshooting them is something that I have not yet done.

It looks like Macrium other tasks > fix VSS needs to be ran even with the boot failure risk.

I'll uninstall Microsoft Office and wait for your troubleshooting ideas >

(Microsoft Office Standard Edition 2003 version 11.0.5614.0 was installed 10/3/2017 and was just uninstalled using control panel.
Compatibility pack for the 2007 Office System version 12.0.6514.5001 was also installed on 10/3/17 and was uninstalled.)

The Intel RST was displayed as one of the ESENT problems.
This may be able to be fixed once the computer is rebooted as the software/HP driver was installed.