thanks for your unattend.xml
I could not reproduce your problem with :
- win10-x64-1607-ltsb n german
- additional drivers for real hardware and virtual clients
Maybe the problem arises with some special hardwaretyp/and or drivers. So we will keep your unattend.xml for unknown problems...
regards,
Bardo Wolf
staging failled with error 0xe0000100.
Re: staging failled with error 0xe0000100.
OPSICONF 2024
https://opsi.org/en/opsiconf/
Basisworkshop Mainz :
17. - 20. 06. 2024
opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.
http://www.uib.de
Re: staging failled with error 0xe0000100.
The exact Windows 10 version is :
WIN_ENT_10_1607_64BIT_English_MLF_X21-07102
WIN_ENT_10_1607_64BIT_English_MLF_X21-07102
Re: staging failled with error 0xe0000100.
in the meantime ive seen similar strange errors when installing for instance windows 10 enterprise.
Solution:
Set product key to the corresponding
kms-client key
(https://technet.microsoft.com/en-us/lib ... s.11).aspx)
hope that helps ,
regards
bardo wolf
Solution:
Set product key to the corresponding
kms-client key
(https://technet.microsoft.com/en-us/lib ... s.11).aspx)
hope that helps ,
regards
bardo wolf
OPSICONF 2024
https://opsi.org/en/opsiconf/
Basisworkshop Mainz :
17. - 20. 06. 2024
opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.
http://www.uib.de