forum.opsi.org

Hi,

I'm trying to make an automatic installation of windows 10.
I used the package opsi-winpe to make my winpe, added the startnet.cmd and used the template win10-x64 filled with my install.wim and unattend.xml file.

The winpe boot properly and startnet.cmd launch work.cmd but after the setup start, it fail with the error 0xe0000100.
"Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation"

BUT if i run the last command of work.cmd the setup works and the staging continue normally.

Could you please help me?

Thanks.

mmh,

may be the winpe has some kind of timing problem.

Does a manual rerun of the
also works?

regards,

Bardo Wolf

I must edit work.cmd first because after the first attempt the drive letter are changed.

X: is still BOOT
C: is WINDOWS and not WINPE anymore
E: is WINPE

So if I replace C: by E: in it, it works.


Setuperr file give this error :

Error 0x3 - could not build list of driver packages

A possible solution should be to omit the DriverPaths section of the unattend.xml.
I'm trying it now.

removing the DriverPaths in the unattend.xml solve the issue. But Windows will not load my drivers now...

Antarion hat geschrieben:I must edit work.cmd first because after the first attempt the drive letter are changed.

X: is still BOOT
C: is WINDOWS and not WINPE anymore
E: is WINPE

So if I replace C: by E: in it, it works.

very strange. Did you edit the custom/unattend.xml ?

Can you post the bootimage.log?

regards,

Bardo Wolf

here is the bootimage.log

driverpath is the problem. i'm trying with Microsoft-Windows-PnPCustomizationsWinPE and Microsoft-Windows-PnPCustomizationsNonWinPE
to check which one is at fault.

So i moved "Microsoft-Windows-PnPCustomizationsWinPE" to the offlineServicing part of the xml and it solved the problem.

I used the official unattend.xml delivered wth the win10-x64 package. Did anyone else got this problem ?

Antarion hat geschrieben:So i moved "Microsoft-Windows-PnPCustomizationsWinPE" to the offlineServicing part of the xml and it solved the problem.

I used the official unattend.xml delivered wth the win10-x64 package. Did anyone else got this problem ?

No, very strange.

Which kind of installationmedia do you use?

Can you provide us your unattend.xml?

Regards,

Bardo Wolf

I use the Windows 10 Enterprise edition release 1607.

here is our unattend.xml

Thanks for your time.