USB Bootable stick Drive C mixup

[Klaver7]

System = 100 Solid:
=============
Microsoft Windows [Version 10.0.26100.8037]
© Microsoft Corporation. All rights reserved.

C:\Windows\System32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.8037

No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>winmgmt /verifyrepository
WMI repository is consistent

C:\Windows\System32>

[Froggie]

@Klaver7, send them the ZIP file of the entire LOG set produced as requested (they need them all).

[admin]

@Klaver7, please send us the complete log file according to the screenshot below.

Thanks.

[Klaver7]

Ok here you go

[admin]

Macrium = No problem, see below

In the WinPE environment, Macrium Reflect does not provide a separate system backup feature, and it will select all partitions by default.

[admin]

Ok here you go

I'm sorry I may not have described it clearly, what we actually need is the log file saved in WinPE.

[admin]

And please follow the steps below to send us the bcd.txt.
1. Run cmd.exe as a administrator in Windows (not WinPE)
2. Run "bcdedit /enum all /v  >> C:\bcd.txt"

[Klaver7]

As I look at your illustration above .. Now I am lost, where can I get this file besides the "logfiles.zip" ??? I know I am getting old :-)

[Klaver7]

PS C:\WINDOWS\system32> bcdedit /enum all /v

Firmware Boot Manager
---------------------
identifier {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
displayorder {9dea862c-5cdd-4e70-acc1-f32b344d4795}
timeout 1

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {fc47a7c0-24da-11f1-b292-ecfacca56fb3}
resumeobject {fc47a7bf-24da-11f1-b292-ecfacca56fb3}
displayorder {fc47a7c0-24da-11f1-b292-ecfacca56fb3}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {ea3a0ce7-2638-11f1-b45d-a24cf980fa3c}
device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{ea3a0ce8-2638-11f1-b45d-a24cf980fa3c}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-us
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{ea3a0ce8-2638-11f1-b45d-a24cf980fa3c}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
custom:46000010 Yes

Windows Boot Loader
-------------------
identifier {fc47a7c0-24da-11f1-b292-ecfacca56fb3}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-us
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {ea3a0ce7-2638-11f1-b45d-a24cf980fa3c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {fc47a7bf-24da-11f1-b292-ecfacca56fb3}
nx OptIn
bootmenupolicy Standard

Resume from Hibernate
---------------------
identifier {fc47a7bf-24da-11f1-b292-ecfacca56fb3}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence {ea3a0ce7-2638-11f1-b45d-a24cf980fa3c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
custom:21000026 partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-us
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes

EMS Settings
------------
identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems No

Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Local

RAM Defects
-----------
identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Global Settings
---------------
identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}

Boot Loader Settings
--------------------
identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Hypervisor Settings
-------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

Device options
--------------
identifier {ea3a0ce8-2638-11f1-b45d-a24cf980fa3c}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume4
ramdisksdipath \Recovery\WindowsRE\boot.sdi
PS C:\WINDOWS\system32>

[admin]

As I look at your illustration above ..  Now I am lost, where can I get this file besides the "logfiles.zip"  ???  I know I am getting old :-)

Please boot into WinPE first, save the log file to a local drive by following the steps in the screenshot above, then restart into Windows and send us the saved log file.