Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
USB Bootable stick Drive C mixup
#7
Ok I just think that the problems arise because my system is fully up to date with the 2023 Boot Cerificates, it will NOT boot with 2011 certificates! Had to replace the boot files with powershell with the 2023 certificates as the 2011 ones where added, but that seems to be a problem with most of them like Macrium / Aomei etc.  only 1 system btw. I only use USB backup and restore as most of us older Geeks prefer that way. But we are walking away from what the real problem is, and thats like Win-RE not checked and Boot-drive C: not accesseble.
The Asus(other PC) does not have this problem. System specs:
===============================
B650 AORUS ELITE AX V2

AMD Ryzen 7 8700G

Kingston FURY KF556C36BBEK2-32  (32-GB)

WD_BLACK SN850X 1TB (CSmile / WD Blue SN580 1TB (DSmile / WD_BLACK SN770 1TB (ESmile

be quiet! Pure Power 13 M 550W PSU

Windows 11

========================================
Microsoft Windows [Version 10.0.26100.8037]
© Microsoft Corporation. All rights reserved.

C:\Windows\System32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:        Enabled
    Windows RE location:      \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: fc47a7c1-24da-11f1-b292-ecfacca56fb3
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0
    Windows RE Version:        10.0.26100.8031

REAGENTC.EXE: Operation Successful.

C:\Windows\System32>
===============================
Microsoft Windows [Version 10.0.26100.8037]
© Microsoft Corporation. All rights reserved.

C:\Windows\System32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:        Enabled
    Windows RE location:      \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: fc47a7c1-24da-11f1-b292-ecfacca56fb3
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0
    Windows RE Version:        10.0.26100.8031

REAGENTC.EXE: Operation Successful.

C:\Windows\System32>
==========================
C:\Windows\System32>fsutil volume diskfree \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
Total free bytes                : 199,364,608 (190.1 MB)
Total bytes                    : 892,334,080 (851.0 MB)
Total quota free bytes          : 199,364,608 (190.1 MB)
Unavailable pool bytes          :          0 (  0.0 KB)
Quota unavailable pool bytes    :          0 (  0.0 KB)
Used bytes                      : 688,775,168 (656.9 MB)
Total Reserved bytes            :  4,194,304 (  4.0 MB)
Volume storage reserved bytes  :          0 (  0.0 KB)
Available committed bytes      :          0 (  0.0 KB)
Pool available bytes            :          0 (  0.0 KB)

C:\Windows\System32>
======================
Microsoft Windows [Version 10.0.26100.8037]
© Microsoft Corporation. All rights reserved.

C:\Windows\System32>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Details for image : \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (amd64)
Description : Microsoft Windows Recover Environment (amd64)
Size : 3,037,030,070 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.26100
ServicePack Build : 8031
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 4526
Files : 20842
Created : 4/1/2024 - 8:51:35 AM
Modified : 3/10/2026 - 7:25:40 PM
Languages :
        en-US (Default)
The operation completed successfully.

C:\Windows\System32>
============================
PS C:\WINDOWS\system32> Get-SecureBootSVN


FirmwareSVN      : 7.0
BootManagerSVN  : 7.0
StagedSVN        : 7.0
ComplianceStatus : Compliant (Boot Manager SVN meets staged SVN)
BootManagerPath  : \\.\HarddiskVolume1\EFI\Microsoft\Boot\bootmgfw.efi

PS C:\WINDOWS\system32>
==================================================================================
Windows 11 24H2 (26100.8037)

Secure Boot: ON
Virtualization Based Security: ON
BitLocker on (CSmile OFF

BIOS Firmware
-------------
    Gigabyte Technology Co. B650 AORUS ELITE AX V2
    Version: F40
    Date: 2026-02-06

Factory Default UEFI PK Cert
----------------------------
    GIGABYTE

UEFI PK Cert
------------
    GIGABYTE

Factory Default UEFI KEK Certs
------------------------------
    Microsoft Corporation KEK CA 2011
    Microsoft Corporation KEK 2K CA 2023
    GIGABYTE

UEFI KEK Certs
--------------
    Microsoft Corporation KEK CA 2011
    Microsoft Corporation KEK 2K CA 2023
    GIGABYTE

Factory Default UEFI DB Certs
-----------------------------
    Microsoft Corporation UEFI CA 2011
    Microsoft Windows Production PCA 2011
    Windows UEFI CA 2023
    GIGABYTE
    GIGABYTE

UEFI DB Certs
-------------
    Microsoft Corporation UEFI CA 2011
    Microsoft Windows Production PCA 2011
    Microsoft Option ROM UEFI CA 2023
    Microsoft UEFI CA 2023
    Windows UEFI CA 2023
    GIGABYTE
    GIGABYTE

Factory Default UEFI DBX Certs
------------------------------
    (NONE)
    EFI_CERT_SHA256_GUID Signatures: 77

UEFI DBX Certs
--------------
    Microsoft Windows Production PCA 2011
    Windows BootMgr SVN 7.0
    EFI_CERT_SHA256_GUID Signatures: 487

EFI Files
---------
    Windows Boot Manager [Windows UEFI CA 2023] is ALLOWED.
        \\.\HarddiskVolume1\EFI\Microsoft\Boot\bootmgfw.efi
        File Version: 26100.30227, SVN 7.0

    Registry: WindowsUEFICA2023Capable = 2
        [Windows UEFI CA 2023] in UEFI DB, and Windows starting from CA 2023 Boot Manager.

    SkuSiPolicy.p7b is CURRENT.
        \\.\HarddiskVolume1\EFI\Microsoft\Boot\SkuSiPolicy.p7b
        Version: 33284.17421.33440.335

STATUS REPORT
-------------
    Registry: UEFICA2023Status = Updated

SUCCESS: NO UPDATES ARE REQUIRED.

PS C:\WINDOWS\system32>
=============================
PS C:\WINDOWS\system32> powershell -nop -ep bypass -f C:\Temp\SVN_Order.ps1
BootMgr SVN 2.0
CDMgr SVN 2.0
WDS SVN 2.0
BootMgr SVN 7.0
CDMgr SVN 3.0
WDS SVN 3.0

FirmwareSVN : 7.0

PS C:\WINDOWS\system32>
===============
Tried to cram in here as much as possible as 1 can only make 1 post per day as a "paying" customer"
Windows real mode see picture below, it speaks for itself.
============

Will have to wait 24 hours again, this is ridiculous


Attached Files Thumbnail(s)
   
Reply


Messages In This Thread
USB Bootable stick Drive C mixup - by Klaver7 - 03-21-2026, 12:31 PM
RE: USB Bootable stick Drive C mixup - by CDC9762 - 03-22-2026, 12:09 AM
RE: USB Bootable stick Drive C mixup - by Froggie - 03-22-2026, 01:16 AM
RE: USB Bootable stick Drive C mixup - by Froggie - 03-22-2026, 01:29 AM
RE: USB Bootable stick Drive C mixup - by Froggie - 03-22-2026, 03:39 AM
RE: USB Bootable stick Drive C mixup - by admin - 03-22-2026, 02:42 PM
RE: USB Bootable stick Drive C mixup - by Klaver7 - 03-22-2026, 03:50 PM
RE: USB Bootable stick Drive C mixup - by admin - 03-22-2026, 06:47 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 12:37 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 12:14 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 12:39 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 12:43 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 12:59 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 01:31 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 01:28 PM
RE: USB Bootable stick Drive C mixup - by admin - Yesterday, 04:13 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)