![]() ![]() ![]() The tool is aimed at IT professionals and enthusiasts. I don't know what else to do, maybe the tool does not patch the files of the windows 10 images correctly.NTlite is a smart Windows configuration tool provided by an independent developer. I would try to do some more testing tomorrow.ĮDIT 3: I removed all x32 EFI files from the AIO and replaced them with the ones from the 圆4 image but I still get the error. I think most EFI files in the AIO image are taken from the Win 10 x32 bit image. For example, the bootmgr.efi file in the AIO image is 1.232 KB, which is the same size as the one from the WIN 10 x32 image. The difference between the Win 7 AIO and Win 10 AIO images is that the windows 7 AIO image contains files for booting only in 圆4 UEFI whereas the windows 10 AIO image, contains files from both x32+圆4 architectures.ĮDIT 2: I think that problem is that you are using UEFI files from the x32 bit image as your MAIN files for the AIO image. Maybe that's why I can successfully boot the Windows 7 AIO iso (as I told you in my first post). I tried removing the "bootia32.efi" file but I still get the error. If you want to reproduce the error just download the latest images and updates, that's what I did.ĮDIT: I suspect that the issue has to do with the x32 bit architecture of windows 10 since it contains files (bootia32.efi) for booting in x32 UEFI, and most PCs now, cannot boot in x32 UEFI and for some reason they get confused and they don't see the 圆4 bit UEFI files. I have also tried to boot the image in VMware workstation and I get a similar error saying "No compatible bootloader found", which I guess means the same thing. Maybe this system does not support 圆4 UEFI boot". If you would like to provide new boot messages support, you need to edit bootfix.bin with HEX Editor like HxD. Use this tool after your NTLite sessions!Ħ) In 圆4 images Name / DisplayName / Desription / DisplayDescription attributes is added space " " to keep wimlib compress install.esdħ) bootfix.bin patching suppot now these languages: en-US, cs-CZ RES patchesġ) ESD support in Windows 7 is created by grabbing sources folder from Windows 10 boot.wim so boot image is still Windows 7!Ĥ) autounattend.xml - Accept Eula + Skip product keyĥ) Don't integrate updates into boot.wim after using this tool, updates should rewrite patched files. Windows 7 with install.esd looks like original Windows 7 setup! All needed resources are rewriten with original one from. ![]() Autounattend.xml is automaticaly used, if present.Īutorun.dll inside sourc32 / sourc64 is patched to look for setup.cmd instead od setup.exeīootfix.bin modified boot message "Press any key to boot from CD or DVD" to "Press any key to boot from DVD or USB" to get modern look Setup64.exe is patched to run autorun.dll in sourc64Īutorun.dll inside boot.wim\2\sources is patched to look for skiprecover.xml instead of autounattend.xml and run setup.cmd, so we can call original setup.exe with custom install.wim / install.esd and $OEM$ location for both platforms. Setup32.exe is patched to run autorun.dll in sourc32 Simply select edition which you want to install and format HDD
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |