SOLVED Can't deploy latest win10x64uefi with 1.5.5
Hi there, everyone! Need your assistance.
Hyper-v vm with generation-2 vm, based on uefi.
Fog version is 1.5.5 (installed on ubuntu 16.04)
Win 10x64 efi, version 1809 build 17763.107
FOG menu config: uefi exit type: refindefi
I’ve manage to customize my win setup(with this article: https://www.theitcave.com/post/561), then used sysprep on it.
If I restart my computer after sysprep is done and then using fog’s ipxe.efi to boot through network, and then in FOG menu using default option boot from hdd, it starts booting with refindefi option(Other option not wirking at all, nothing happens when you press enter on “boot from hdd”), I’m getting error during win installation process:
“The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.”
And this happens even if I didn’t installed FOG client at all.
Also, it’s not happening if, in VM settings, I’m choosing to boot from boot-ffile instead of network boot, EVEN if fog client installed and fog service isn’t disabled. Windows installs normally.
And thank you to all who involved in this incredible project!
Wow, you’re so fast with answers! I really appreciate that!
As I’ve said in the firs post, I’m using Hyper-v second generation VM based on UEFI.
AAAAND! It seems that I’ve got some progress(really hope so).
What i’ve done:
Downloaded latest binary zip of rEFInd: https://sourceforge.net/projects/refind/files/0.11.4/refind-bin-0.11.4.zip/download
extracted /refind/refind_x64.efi ; drivers_x64 from this folder
Renamed refind_x64.efi to refind.efi, renamed drivers_x64/ntfs_x64.efi to drivers/ntfs.efi, renamed /drivers_x64 to /drivers.
Chmod 644 chown fog:www-data to this files|folders, moved them to /var/www/fog/service/ipxe, removed comment symbol from this line:
And I’ve just deployed my image with only one error at the end:
“failed initialization of the interactive login process” or something like this, it’s translated from Russian.
@kAs1m Does this happen on non-VM as well?
What kind of VM software do you use?
Exit types are tricky at best in UEFI, throw in VM as well and it gets even more crazy.
Firstly, thanks for your answer!
But, unfortunately, it seems that I’ve write my first post with mistakes, so you didn’t get it(Eng isn’t my main language, obviously).
This Error occured ONLY if I prefer NETWORK BOOT in VM options and then, chainboot my prepared Windows system via rEFInd option in exit options.
If I’m using efi file-boot(bootmgrfw.efi) in VM’s “bios”-like options everything is alright, Windows continues to install normally with autoanswer file, then loads the desktop.
On a VM where I’ve deployed image, then turned VM off, then change the boot option from network to efi, and waited for WIN setup till launching to desktop - I cat switch boot option back to network, and it’s working. So the problem is that I have to manually switch boot option to EFI after i deployed image and back to network after it first boot.
@kAs1m Interesting, I have seen a vast variety of BSOD but this is a first!
Thankfully there is some info online about this which points to hardware/drivers (as the name of the BSOD would imply) (I’ve mostly seen complaints relating to GPUs)
If an older version of Win 10 works on the same device we can only assume that there’s some new or updated driver in the latest Win 10 builds that are causing this to occur on your clients.
What are the models of your clients? Perhaps this is a known problem for those devices.
So, here’s the crash report:
And the dump: https://drive.google.com/file/d/1dvOXjVpbSLlb3DUa0NzMgHMRHZ9eTiO1/view?usp=sharing
- No, didn’t catch the error code, it only gaves qr code now, if it’s important, i’ll try to make a screenshot with BSOD, and also will try to find the dump.
- Yes, did everything according to that instruction.
- I’m using autoanswer file.
- Starting with a clean install.
- Is there a way to debug the procedure? And post vital info in this thread?
@kAs1m Did you happen to catch the error code in the BSOD?
Did you use the /generalize switch with sysprep? (I’m assuming you did based on the link you gave)
Does the client reach the OOBE screen? (or do you use an unattend file?)
Did you upgrade your image or did you start with a clean install?
If you started with a clean install and used an unattend file, then there’s probably something going on with the latter. (maybe some options are no longer valid or some new mandatory options are missing)
I’m also getting BSOD before this error.
Other(grub-based) exit options getting this error:
Could not boot: Exec format error (https://ipxe.org/2e008081)