Fresh Clover release (5163) won't boot on legacy BIOS LGA1156 system created via BDUtility. For me release 4449 worked.

[mndtr]

I have legacy-based system and installed NVMe SSD via PCIe adapter and wanted to boot Windows from NVMe. Used BDUtility like it was in most user-friendly guides. My Clover won't boot after 6_ and goes to black screen with constant _ at left corner. Using boot7 file helps to get booted Clover with GUI but even with different NvmExpressDxe.efi drivers on both \BIOS and \UEFI folders I can't see NVMe as available file system. Trying using v4449's boot6 file helped to boot on new v5163. The strange part is that I tried default new v5163 created via BDUtility on another LGA1156 machine (mobo GA-P55-UD3 and another Lynnfield CPU) and it worked perfectly. Also yet another machine (but UEFI-based, LGA 1155) which load EFI only from USB drives too needs old v4449 release to boot Clover from HDD.

Shortly: same old legacy platforms, same NVMe SSD, same newest Clover on one USB drive, different motherboards — one motherboard boots and another not.

My current working Clover:
4449.zip

System information:

Asus P7H57D-V EVO
Intel Core i7 870
16GB RAM
GTX 1660 Super
NVMe SSD
2 HDD

Steam's system information:

Computer Information:
Manufacturer: System manufacturer
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
CPU Family: 0x6
CPU Model: 0x1e
CPU Stepping: 0x5
CPU Type: 0x0
Speed: 2942 MHz
8 logical processors
4 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Unsupported
AVX: Unsupported
AVX2: Unsupported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Unsupported
BMI2: Unsupported
F16C: Unsupported
FMA: Unsupported
Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0
Client Information:
Version: 1751405894
Browser GPU Acceleration Status: Enabled
Browser Canvas: Enabled
Browser Canvas out-of-process rasterization: Enabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Enabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Enabled
Browser Rasterization: Enabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Enabled
Browser Video Encode: Enabled
Browser Vulkan: Disabled
Browser WebGL: Enabled
Browser WebGL2: Enabled
Browser WebGPU: Enabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA GeForce GTX 1660 SUPER
DirectX Driver Name: nvldumd.dll
Driver Version: 32.0.15.6094
DirectX Driver Version: 32.0.15.6094
Driver Date: 8 14 2024
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 1660 SUPER
VendorID: 0x10de
DeviceID: 0x21c4
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.91" x 11.77" (23.98" diag), 53.1cm x 29.9cm (60.9cm diag)
Primary Bus: PCI Express 8x
Primary VRAM: 6143 MB
Supported MSAA Modes: 2x 4x 8x
Sound card:
Audio device: Динамики (High Definition Audio
Memory:
RAM: 16344 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 634640 MB
Largest Free Hard Disk Block: 237787 MB
OS Install Date: ��� 05 2025
Game Controller: None detected
MAC Address hash: 9596979984114a729de83292274319f22a73039e
Storage:
Disk serial number hash: 5588efff
Number of SSDs: 1
SSD sizes: 256G
Number of HDDs: 2
HDD sizes: 250G,160G
Number of removable drives: 0

If you want I can speak russian because it's my native language.

[chris1111]

I know that clover duet is broken for long time maybe @jief666 or @SergeySlice can see were is the issue

Ive create a repos here Clover-ESP-Legacy to use the Clover Package with old boot file

[mndtr]

Ok. However I prefered method of inserting OpROM into the legacy BIOS of my motherboard since it's reduces latency and time to boot system. But I hope project will be more universal because it will be needed when Microsoft will deprecate legacy MBR boot...

[SergeySlice]

I tested newest boot6 and it works so I don't know what to fix.

[mndtr]

I tested newest boot6 and it works so I don't know what to fix.

Do you tested it on old platform? I tested newest boot6 on my machine and it boots into a black screen with just underscore _. However I think that fixing it may be not so worthy because of small amount of people need it. And I already described how to fix it manually via changing boot-file with older one from releases on SourceForge or inserting OpROM into legacy BIOS.

[SergeySlice]

Take the boo6 file with NVME support

boot6.zip

[mndtr]

Take the boo6 file with NVME support

boot6.zip

@SergeySlice I've tried it but it didn't work. How I tested: used BDUtility to prepare USB drive, tried to boot it and got black screen, then tried to use boot-file from your archive (pasted into USB drive and renamed from boot6 to boot), and it didn't booted too. Tested on LGA1156 PC.

With old 4449's release boot-file everything works on two old machines I tested: mine (legacy BIOS) and another person's PC (motherboard: asrock h67de3, it have UEFI but kinda hybrid because it can boot EFI only from USB drives, so to boot Clover from HDD I needed to use 4449's boot-file)