Odd issue with Win 10 UEFI images after updating from 1.5.9-RC2.15 to 1.5.9-RC2.17
I updated my home server and a server at work. Today at work, I noticed a once working Win10 UEFI image would not longer boot to the desktop properly… even deploying it to the same workstation it was captured from.
The image was captured a couple of days prior on 1.5.9-RC2.15 and had been deployed a few times without any problems. The problem only happened after going to 1.5.9-RC2.17.
This was easy to resolve since we have the same exact image in legacy, I deployed the legacy image then converted it to UEFI and re-captured it as the broken UEFI image. … tested working.
I just figured oh… the image got corrupted due to… something else. I was too burnt to look into it any further.
I got home and tried to deploy a completely different Win10 UEFI image that also was captured and deployed on 1.5.9-RC2.15 and since updating to 1.5.9-RC2.17 the same exact weird behavior. The desktop never completely loads. Task manager never opens… etc etc.
The image is close to stock so it is easy to recreate. I’m wondering if anyone else experienced this.
Nobody else has access to either FOG server and the only change made was the update from RC2.15 to 1.5.9-RC2.17
And automated Updates…
RC2.19 is not much of a difference. Just preparing for the actual release to come very soon!
Cool an even newer version is out now. Gonna try 2.19
I don’t know. The Win 10 UEFI image on the FOG server at work and a completely different Win 10 UEFI image on my home FOG server both deployed and worked fine the day before. Nobody else has access to either FOG server and the only change made was the update from RC2.15 to 1.5.9-RC2.17
The original UEFI based image that got corrupted is not working.
Do we know how it got corrupted?!
Sorry I am not explaining this well.
I was able to resolve the situation by creating a new UEFI image from a legacy image and capturing it. The original UEFI based image that got corrupted is not working.
@Fog_Newb And this is now working fine? Even with FOG 1.5.9-RC2.17?
The Windows 10 EFI image is just the legacy image converted to EFI
Since the Legacy image was still working fine I deployed the legacy image, converted it to EFI then re-captured it replacing the broken Win 10 EFI image
It was easy to sort it just seemed related to the upgrade at the time.
How did you get this sorted?
Yes that update was installed on both images.
The odd thing is it only affected the EFI image(s) not Legacy one and the same behavior on 2 different fog servers and 2 different images that deployed fine prior to the FOG upgrade.
But yeah who knows. It was easy to sort it just seemed related to the upgrade at the time.
@Fog_Newb The changes between 1.5.9-RC2.15 and 1.5.9-RC2.17 are minimal. See the last two commits here: https://github.com/FOGProject/fogproject/commits/dev-branch
I can’t imagine FOG to be causing the described issue. I have read about the latest MS Windows 10 2004 update KB4571756 causing a fair amount of strange issues. Can you please check if you use Win 10 2004 and if KB4571756 is installed?