@Sebastian-Roth said in Windows 10 Deployment stuck:

Yeah, i kn this is’nt really a fog problem… its the same laptop as the reboot problem, legacy boot, spinning HD…
i could try not? but nvm thx for the help with the reboot problem…

@Sebastian-Roth

Yes I did, well maybe I wasnt 100% clear, the reboot isn’t the only problem, windows doesn’t boot. When I forced reboot windows installation error… I presume this is a driver issue? So I think the reboot problem is solved now… thx Sebastian!!! the kernel argument fixed the reboot problem… now i just have to get Windows to boot, how can I insert drivers in deployment process… Like is said I’m used to MDT, I’m new to FOG…

Grtz

@Quazz

I Did generalize imao? no 3the party antivirus installed, we push AV after deployment…

I do think its a driver issue now just looking for solution to insert the drivers, I’m justed to MDT…

@Quazz

Yes, we use an unnattend.xml file, fog client is installed in VM before sysprep… strange thing is it works on like 200 computers (Desktops/laptops). I just fails on this type of laptop…

And no service isn’t disabled before sysprep…

More information…

So the deployment Task is completed, GUI = task complete, computer “jammes” see photo…

Forced reboot --> Windows installation can’t be completed… tried several times, changed boot settings, i have no clue what to do!

Hi,

I’m new to this forum.

I deployed a Windows 10 image + snapins to several workstations without problems, now we have a certain type of laptop where the deployment “fails”. The image is installed (task complete) but jammes @ reboot. Snapins are not installed…

Anny tips/Suggestions

grtz

Hi,

I have Windows 10 image that we deployed at several laptops/desktops without problems, now we have some older laptops (HP notebook 250 G3) were the deployment process gets stuck at reboot, the image is installed 100% and fog servers says that deployment was ok… Snap-ins are not executed and not joined at domain…

Is there somewhere to get some more info (Logs)…

grtz