Solved VenToy boot partion + win10 install

[longpanda]

Rename directory name from EFI to VTEFI  and try this CI release
https://github.com/ventoy/Ventoy/actions...3781722980
https://www.ventoy.net/en/doc_github_ci.html

[LordMessi]

Rename directory name from EFI to VTEFI  and try this CI release
https://github.com/ventoy/Ventoy/actions...3781722980
https://www.ventoy.net/en/doc_github_ci.html

OK, I'll try - could you perhaps also fix the "bug" in Ventoy2Disk.exe - "Please run under the correct directory"

I mean what actually is the correct directory - and why should it run from that...

---

Rename directory name from EFI to VTEFI  and try this CI release
https://github.com/ventoy/Ventoy/actions...3781722980
https://www.ventoy.net/en/doc_github_ci.html

OK, I'll try - could you perhaps also fix the "bug" in Ventoy2Disk.exe - "Please run under the correct directory"

I mean what actually is the correct directory - and why should it run from that...

So I updated to the release, and now the Windows installation complains about \EFI\Microsoft\Boot\BCD - status 0xc000000f  - The boot configuration data for your pc is missing or contains errors.

[longpanda]

"Please run under the correct directory"
--------- 
Download Ventoy install package from github release (https://github.com/ventoy/Ventoy/releases), then you will not get this message. 
Remember to download the install package (not the source code).
For every release, I will tell the install package file name and file sha256 checksum.
for example:
ventoy-1.0.86-windows.zip:    fb414f4546a62fd7688b30d7f483521bd9b740f716fae176911d9e966e4b99f5

So if you download this ventoy-1.0.86-windows.zip file then you will never get this error message.

If you download Ventoy source code or download Ventoy from other unofficial website (e.g.  sourceforge ...) then you may get this error message.

[longpanda]

Try this:
Don't rename EFI directory name, just rename the sub-directory EFI/BOOT  to  EFI/VTBOOT.
This time check whether you can boot into Ventoy.

[LordMessi]

Try this:
Don't rename EFI directory name, just rename the sub-directory EFI/BOOT  to  EFI/VTBOOT.
This time check whether you can boot into Ventoy.

Nope - Windows 10 starts without Ventoy.

[longpanda]

Now still boot to Ventoy (rename EFI directory name to VTEFI), then boot a linux ISO from Ventoy (e.g. Ubuntu)
After boot, run the following command in the terminal and give the result here:
sudo  efibootmgr -v

[LordMessi]

Now still boot to Ventoy (rename EFI directory name to VTEFI), then boot a linux ISO from Ventoy (e.g. Ubuntu)
After boot, run the following command in the terminal and give the result here:
sudo  efibootmgr -v

ubuntu@ubuntu:~$ sudo efibootmgr -v
BootCurrent: 001E
Timeout: 0 seconds
BootOrder: 0000,001F,001C,001D,0020,001E,0021,0022,0023,0024
Boot0000* Windows Boot Manager HD(3,GPT,1873e546-6581-4d2c-b54b-99ca6cbc265f,0xdc609000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Asset Information FvFile(da465b87-a26f-4c12-b78a-0361428fa026)
Boot0015  Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0016  ThinkShield secure wipe FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0017  ThinkShield Passwordless Power-On Device Manager FvFile(08448b41-7f83-49be-82a7-0e84790ab133)
Boot0018  Wi-Fi Configuration FvFile(d3aaff0f-cb22-4792-896c-802c2e9383ba)-.A.p.p...
Boot0019  Intel® MEBx FvFile(29a70110-7762-4211-ae88-fab19b7665be)
Boot001A  Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot001B  Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001C* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001D* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001E* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001F* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022* ON-PREMISE VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri()
Boot0023  Other CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35400)
Boot0024  Other HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ca88c2349e7ae947beeb43038a5aeae700)
Boot0025* IDER BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0026* IDER BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0027* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0028* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

[longpanda]

Is this the partition 3 ?
Boot0000* Windows Boot Manager HD(3,GPT,1873e546-6581-4d2c-b54b-99ca6cbc265f,0xdc609000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................

[LordMessi]

Is this the partition 3 ?
Boot0000* Windows Boot Manager HD(3,GPT,1873e546-6581-4d2c-b54b-99ca6cbc265f,0xdc609000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................

I would believe so.

[longpanda]

Try this:
1. Run sudo efibootmgr -B 0000
2. Don't rename EFI directory name, just rename the sub-directory EFI/BOOT  to  EFI/VTBOOT.
This time check whether you can boot into Ventoy.