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 ?

@AlexPDX I selected different types of partitions (in FOG image creation) because I got several errors.

I will recreate another image.

Concretely :

• I install a windows10 via USB (in UEFI)
• I enter OOBE mode
• I install Windows ADK & FOG-client$
• I personalize my image: installation of my programs, system settings, drivers, etc.
• I stop the Windows Media Networking service to avoid errors during Sysprep by typing in CMD: net stop wmpnetworksvc (going to o cd c:\windows\system32\sysprep)
• I launch SYSPREP

Do I have an error in my procedure?

I will listen to your advice and incorporate it into my procedure.

@AlexPDX I re-image and change my partition disk before deployment with MiniToolPartitionMagic ?
I imagine that I can no longer modify my capture of my pc master ?

Hello everyone,

Still as part of my deployment tests:

So, I managed to create a capture from a PC master. I linked it to the image.

When deploying the image on a target-pc, here is my error message:

I think this screen will give you more details about my problem :

I am a beginner, forgive my mistakes, what do you advise me to do/change?
Thank you

@JJ-Fullmer Thanks a lot for your answer. I retry a capture, paying attention to the points mentioned.

Hello everyone,

Finally, I reinstalled a windows 10 with a bootable key. I directly clicked on shift f10 to enter cmd

and I fiddled in regedit to modify the ChildCompletion key

Only, this key did not exist in my system. So I created it with this command: reg add “HKLM\SYSTEM\SETUP\STATUS” /v “ChildCompletion” /t REG_DWORD /d 3 /f

I’m posting this hoping it helps future users.

Now that my problem is solved, what do you recommend so that it does not come back again? Should I modify this key in my base image before the sysprep?

Cordially

@Tom-Elliott Yes the fog client has been installed on the base image (HTTP://10.10.10.38/fog/client > Download smart installer)
I enter the IP address of my server and I deselect “fog tray”

As for the second question, I did nothing in this direction. Before my sysprep I simply run:
cd c:\windows\system32\sysprep
net stop wmpnetworksvc

@Tom-Elliott What surprises me is that the pc on which I created my image is the same model as the one receiving the image. There should be no driver incompatibilities

I just created a test image (with just a windows, chrome & 7zip, some quick settings) I launched the sysprep correctly

I’m new to deployment and imaging

Hello everyone,

I just installed a fog server in my company
I am still testing my deployments for my future mission to deploy several images on a large part of my computer park (± 2000 machines to deploy)

So I created my FOG server on a debian11. the installation went very well.

When I launch a deployment on (several) test PCs: I constantly get this error: “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.”

I mainly use ThinkBook 14 G2 ARE

this occurs after the deployment, whereas this one seems well applied.

For you, is this a problem on my fog server or is it a bad configuration in the BIOS? Or an image problem?

Thank you in advance and forgive my English