How did you do that?
1. What partitions on the disk 100FAT32 + rest NTFS ?
2. Which EFI loader you used - from Beta2 6.0.5384.4 ?
3. What version VMware?
4. VMware Workstation or Player?
5. Which Host's operating system
1.- MBR Partition scheme, done with Partition Magic v8. 1024MB active fat32 partition + rest NTFS (20GB VDisk).
I don't think sizes have to do, as long as you have a small FAT32 partition to place the files and the rest as NTFS. This also allows you to do BIOS booting normally if the EFI boot procedure fails.
Note: Both primary partitions have to be unhidden
. There are partition tools which set the hide partition flag on one of them when you set active flag in the other, as DOS doesn't know how to manage multiple primary partitions. THIS CONFIGURATION WILL NOT WORK IN EFI MODE
. If your partition tool hides all the primary partitions except the active one, you will have to unhide the rest manually. For better results, just use the diskpart tool which comes with XP, Vista or Win7. PtMagic allows you to unhide manually individual partitions too, without altering the Active flag of the bootable one.
2.- All the loader and certain extra files for the loader taken from Beta2 6.0.5384.4. My structure of the files taken from beta media is the following one:
Code: Select all
bootx64.efi (renamed bootmgfw.efi, taken from ..\Microsoft\Boot folder)
Boot (Folder taken as it is from boot.wim:\Windows\Boot\EFI)
Fonts (Folder taken as it is from boot.wim:\Windows\Boot)
bcd (dummy BCD file taken from ISO:\Boot)
Boot.ini (original created by XP64 setup, modified with nobcd parameter and "/noguiboot /usenewloader" in Os option entries)
nt6.cat (taken from boot.wim in the same relative location and renamed nt5.cat to avoid collisions with the XP64 nt5.cat signature catalog. Bootmgfw and Winload don't care in the catalog name as long as the files have MS or an MS approved signature, and the file ends with the .cat extension)
winload.efi.mui (taken from boot.wim in the same relative location)
The en-US folder, with the bootmgfw, bootmgr and winload mui files, along with the Fonts folder and its files are required for this version of the UEFI loader. Bootmgfw and Winload will give you errors if them don't find these files in their proper locations. The beta nt5.cat file is necessary to make Kernel Module Signature Verification happy, and makes "/disable_integrity_check" unnecessary, as Bootmgfw and Winload will load and use both NT5.cat from XP64 and NT6.cat copied from the beta files to verify all the boot file chain (NT6.cat verifies Bootmgfw, Bootmgr and Winload files, NT5.cat verifies all the rest).
3. VMware 12, with Hardware v8 profile. With its original builtin firmware (without ntfs support).
4. Workstation. But works fine with the player included in Workstation too.
5. Windows 10 10.0.16299.547
Beta12 wrote:I am using VMware Workstation 8 and bootmgfw.efi from Beta2 6.0.5384.4 but have error: BlInitializeLibrary failed 0xc00000bb
Because you didn't supply the MUI and the Font files in the locations expected by the loader modules. Check my file structure.