Hi everyone, and thanks for your answers.

Good news! If FOG works for you, it’ll work for me too (comming soon).

@mashina said in Issue when I tried to make Windows 11 gold image:

I am not aware of any completion message on the server. As far as I know, once the progress bar in the Task tab reaches 100%, the image has been fully cloned to the computer. Can you confirm if that is what you are seeing?

In the PC client, yes it’s exactly this message appears

@mashina said in Issue when I tried to make Windows 11 gold image:

Based on your description, it sounds like your configuration is not capturing the boot partition. As a result, when the image finishes deploying, the system cannot find a valid boot mechanism and falls back to network boot.

I’m looking at the clone I made on a test PC, and I can see using diskpart that the BCD was created correctly.

The files are there.

I tried rebuilding the BCD using the commands.

509 / 5000
Hi everyone, and thanks for your replies.

Good news! If FOG works for you, it’ll work for me too (eventually).

I’m looking at the clone I made on a test PC, and I can see using diskpart that the BCD was created correctly.

The files are there.

I tried rebuilding the BCD using the commands. The output is correct, but Windows won’t boot.

boot C:\Windows /l es-es /s X: /f UEFI

@pilipp_edv said in Issue when I tried to make Windows 11 gold image:

d8eb6692-2fff-4250-9ce8-9bf34f1e1183-image.png

I have the same configuration in my server.
But i tested the others options (im not used DD)

I don’t know what other options I have to check.
Do you know of any logs where I can find more information?

Regards

@mmoore5553 Understood and appreciate the return with new information.

i’m not sure what caused it but glad it has since been addressed/fixed.

Thank you! And yes, I gave an upvote!

@Tom-Elliott Hi Tom,

Thank you, that clarifies a lot. I now understand that hostSecTime represents the expiration time, not the creation time, which fully explains the consistent +30 minute offset I was seeing. That part now makes sense and resolves my question.

The only remaining actual issue I’m trying to understand is the snapin behavior: in several cases, snapins did not execute on some hosts. I don’t see any errors in the logs. Only that the snap-in task doesn’t start, but I will work on this and gather some more data. Thank you!

@romprager The simple answer is depends on the iso image and what OS will boot from the ISO image.

I do have several how tos in the forum that shows how to net boot several different installers.

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

@Tom-Elliott Yep, I caught that workaround in the earlier post. I moved the image folder from /images/dev to /images, but still resulted in the same error.

One thing I noticed this morning, is that the image capture process is hanging at 99% on the task page, as in for at least 45 minutes. Not sure if that is a symptom or the cause.

The previous post was suspect of a very recent init version – but i’m on the most recent dev-branch.

Thank you!

Some Updates (08/12/2025): Fedora has successfully obtained a signed copy of Shim 16.1 which should fix Dell Network boot issue. You can obtain it by downloading the rawhide rpm package and extracting it. I haven’t tested it yet, but will post an update once I do. Around 9 months ago, it looks like a change was pushed to fog which actually updated the general.h header file, enabling the shim command by default. As such performing this modification manually isn’t required anymore.

@rodluz I know you were talking to the other person, but if you like you can send me the kernels for testing.