@RTOadmin I have to admit that I have not used the printer stuff myself really. Just trying to give you a hand.

Have you checked the user registry for old entries?

I know @Wayne-Workman used it in the past. Maybe he has better ideas.

Beside that I can tell you the fog-client runs as SYSTEM and uses the printui.dll to add the printers.

@george1421 Rebuild to last version didn’t fix the problem.
@Tom-Elliott Exit type to EXIT give a “chainloading failed…”

using snponly.efi fixed the problem.

Thank you for your help.

@george1421
My golden image include these software:
chrome, firefox, egde, acrobat reader, skype, thunder bird, trellix endpoint security, osquery.

I don’t know if i doing something wrong.

Thank for your unattend file, i will try sysprep again with your, hope it work 🙂

@Brad39413 The FOG service should be started from your setupcomplete.cmd batch file. That way it doesn’t start doing its part before oobe is complete. Just update your software or delay the startup of the fog service until you are ready for it to do its thing.

@seppim TBH Your results do not match your subject line, but…
Yes you discovered that bios computers need a different boot loader than uefi computers.

bios == undionly.kpxe
uefi == ipxe.efi or snponly.efi

If you have a windows or linux based dhcp server you can configure it to dynamically send out the right boot loader name based on the pxe booting computer.

And you are also correct to pxe boot into FOG secure boot needs to be disabled.

I can also atest to this. Windows 11 is not having any issue with my Dell Latitude 7440 2-in-1’s. Select “Windows 10” as your OS and you should be just fine…for now 🤛

@george1421 Hi, thank you for your reply.
yes, I agree with you that windows 8 should be stored in the firmware, but then I just don’t understand why when we fog from win 10 back to windows 8 by the image we have 5 years ago, it then grabs the same key to every computer. ( I fog 5 computers and 5 both have the same exact key ). I tried several ways to get the original key from bios by Powershell, cmd, or even registry and nothing worked. All value is empty or no value

again, sorry for the misunderstanding. I am a student worker and try to fog some old computers for sales. What I thought is the fog, will bring the computer back to the time before we going to join domain, and delete everything sensitive inside of it.
I dont think we still keep the cd. But I will try to see if your way work. Thank you again!

I answer myself, the problem was a couple of open files that CHKDSK did not correct, I deleted them and it now generates the image correctly

@Sebastian-Roth

Managed to get this to work by downgrading rEFInd to version 11 as per this:
https://forums.fogproject.org/topic/11993/refind-pxe-booting-issue

Hello,

Here is a link for taskbar in Windows 10 :

https://learn.microsoft.com/en-us/windows/configuration/configure-windows-10-taskbar

Just for my curiosity why not use sysprep + copyprofile solution ?

For me depends what you want personnalize. Often just need GPO, registry, copy files etc to personnalize user environment.

Hello, i found a curious behavior. When I use a account who only serve to join domain : “djoin / djoin”, I can’t join the domain but it work with the GUI. But when I use my administrateur account and password, it work.
Fog 1.5.9
Julien

@LulaHuel While we do have this “Windows Problems” forum, it’s not quite in the same boat.

We, in this community, have an imaging platform called FOG. Often these images might include Windows, and sometimes the imaging process might have issues with Windows, hence this naming mechanism for this topic.

I don’t think anyone would hesitate to help you, but we generally ask people discuss issues as it pertains to them, windows, and how or what FOG may have done that might have cause it. We aren’t a general MS Windows support forum.

Glad you were able to fix the issue and posted a solution, but how this was something FOG did I’m unsure.

@UserBxl May I suggest looking at the BIOS . I see you captured an EFI image. Just check the boot settings on the Lenovo make sure it is booting to EFI and not the Auto setting . Also check if secure boot has been disabled.

Hello everyone,

The problem continues to persist (and even during the creation of the image)

When I have to restart my PC (in OOBE mode) to: change domain, restart after name change, restart after update, etc…

This happens randomly during a reboot. I come across this error. It is therefore impossible for me to create an image.

I find solutions (change on regedit, etc) but my OOBE mode is lost and I have to start over each time.

A solution ?

Thank you for the quick replies. Turns out I did have Fastboot enabled. The Recovery environment was not setup as well. Had to copy winre.wim, and enable the reagentc. Did those things and recaptured the image. Deployed to another laptop and it’s working properly.
Thanks again.