Axiom's questions

I have a recurring problem using sysprep on our Windows 10 machines. I use sysprep with an answer file. When I send our windows image on machines with almost the same hardware, everything works perfectly.

However, lets say my source machine is a ASUS and I decide to sysprep my Windows 10 installation and send it to a HP machine, I get this message:

+++ Error message "The Computer Restarted unexpectedly or encountered an unexpected error" after System Startup +++

Normally, I can open regedit using Shift+F10 and change the child completion parameter to 3 instead of 1 nd it works but I want to understand and fix this error. I never found any reason why I get this error and how to fix it permanently...

Anybody have an idea?

I have a very frustrating problem with my sysprep image. Everytime, I choose fr-CA as keyboard layout in my sysprep answerfile, I always end up with canadian french (Multilangual standard), english US and French (France).

I specified in my answer file the inputLocal to: 0c0c:0001109 in winpe, specialize and oobesystem. I also change the value for the copyprofile option to yes.

This problem doesn't happen if I switch to english (canada).

Anyone have an idea what I could do to ONLY have french canada keyboard?

By the way, we don't use SCCM or Audit mode for our Windows system image. We use a vmware VM that is preconfigured with the programs we need and configuration that are persistent through sysprep. Then we send the image to clonezilla for deployment.

We are using the Windows 10 Enterprise LTSB ISO for our company and it does almost all we wanted (no universal apps, no unwanted services, no EDGE, etc).

Unfortunatly, Telemetry is still on and OneDrive activated. I know I could deactivate all of this by GPO but I wonder if it's possible to just include this in a sysprep answer file. Any tried this? That's the two things that are not automated yet.

Thanks a lot!

I have a problem and I haven't been able to get a good answer for this. I want to install drivers on many computers at the same time remotely. The command works but it fails du to timeout.

When I do the command on the computer directly, there is a popup that said if I want to add the driver owners (in this case google) to the trusted publisher. This is what's causing the timeout. I wanted to try to get rid of it but it seems impossible. I had the idea to self-sign the driver certificate but it seems to be impossible for the x64 version of Windows but allowed in 32 bits for some reason.

Anyone have an idea how to proceed? I only want to install that damn drivers remotely and silently.