Create media for automated unattended install of Windows 10

avismile10 · 23 Jan 2019

@Kari

Quick question, is there a difference from where i get the original wim file (for example VLSC, MSDN or Media creation tool)?
i'm asking because i was having two issues with two separate files.
1. I used Media creation tool to download the latest ISO, but dism kept on throwing error 11 when i tried mounting it (powershell's error was very not descriptive so i tried with dism itself)
2. i used the generic key you supplied for Windows 10 Pro with an image that only contained a windows 10 pro index, and i kept on getting an error that i supplied a wrong key.

Thanks in advance.

ludwin79 · 23 Jan 2019

Well I found this way:

Integracion de Drivers a instalador de windows - YouTube -add driver (Spanish).
CÃ³mo integrar programas desatendidos a Windows 7, 8, 10 - YouTube -add programs unattended (Spanish).
Add Drivers to Windows Installation ISO - YouTube -Add Drivers to Windows Installation ISO

those are very good documentation.

avismile10 said:

@ludwin79 You can add drivers for multiple computer models, windows knows itself what drivers to use for what model.

Kari · 23 Jan 2019

avismile10 said:

1. I used Media creation tool to download the latest ISO, but dism kept on throwing error 11 when i tried mounting it (powershell's error was very not descriptive so i tried with dism itself)

MCT ISO is ESD based, it has install.esd file instead of install.wim in Sources folder. All references to install.wim must be changed to install.esd.

The MCT ISO, its install.esd cannot be used to create catalog file in Windows System Image Manager. You need to either download a WIM based ISO, or convert install.esd to install.wim (tutorial).

avismile10 said:

2. i used the generic key you supplied for Windows 10 Pro with an image that only contained a windows 10 pro index, and i kept on getting an error that i supplied a wrong key.

I used the generic key for W10 PRO provided by Microsoft (VK7JG-NPHTM-C97JM-9MPGT-3V66T) only yesterday to create Insider build 18317 deployment image. Worked / works perfectly.

If it does not work, it is either because the image is damaged, it does not contain PRO edition, or there's a typo in your answer file. There simply are no other possibilities.

Kari

Kari · 23 Jan 2019

ludwin79 said:

Well I found this way:.

In addition, see this tutorial: DISM - Add or Remove Drivers on an Offline Image | Tutorials

Kari

avismile10 · 23 Jan 2019

Kari said:

MCT ISO is ESD based, it has install.esd file instead of install.wim in Sources folder. All references to install.wim must be changed to install.esd.
The MCT ISO, its install.esd cannot be used to create catalog file in Windows System Image Manager. You need to either download a WIM based ISO, or convert install.esd to install.wim (tutorial).

Yeah, i'm sorry i didn't mention that i converted first the esd to a wim file. I was having issues with the WIM file, not the ESD.

Kari said:

I used the generic key for W10 PRO provided by Microsoft (VK7JG-NPHTM-C97JM-9MPGT-3V66T) only yesterday to create Insider build 18317 deployment image. Worked / works perfectly.

If i may ask, what was the source of your wim file?

Thanks in advance.

Kari · 23 Jan 2019

avismile10 said:

Yeah, i'm sorry i didn't mention that i converted first the esd to a wim file. I was having issues with the WIM file, not the ESD.

Can't explain your issue without a screenshot of the error, and the log file.

avismile10 said:

If i may ask, what was the source of your wim file?

Self made build 18317 ISO (tutorial) after upgrading build 18312 to 18317 last week.

Kari

avismile10 · 23 Jan 2019

Kari said:

Can't explain your issue without a screenshot of the error, and the log file.

Never mind, seems like something went wring with that conversion, just converted again it it worked as it should have.

i just have to figure out now what the issue with the key was. Will be doing some testing and report back.

ludwin79 · 29 Jan 2019

Hi Kari,

this is out scenery:
1-UEFI/GPT configuration.
2-we follow all your steps to create a image an then copy to a boot USB to install windows using autounattended, and unattended files.
3.- Windows 10 v1803 64bit.
BUT we get the follow error: please help me I don't know what to do. I spent a lot of hours looking the error or doing different test. We see the error on the VM (Hyper-v) and on a physical machine as well.
"windows could not create a partition on disk ). The error occurred while applying the auntted answer file's <diskconfiguration> setting. Error code: 0x80042565"

Attachment 221666

Kari · 29 Jan 2019

ludwin79 said:

Error code: 0x80042565

Usually, error code 0x80042565 means booting in wrong mode (BIOS / UEFI). For instance, if your Hyper-V VM is Generation 1, it is a BIOS machine with MBR partitioning and can't create GPT partitions as in your answer file. For that, you need Generation 2 VM which is UEFI / GPT.

Here's a good post to read: Deployment error: Windows could not create a partition s technical blog

Kari

ludwin79 · 06 Feb 2019

Hey mister,

I already have the power setting and you gave me how add drivers thanks for that.

do you have any blog to setup "default apps setting" on the image? Win10.

Kari said:

Usually, error code 0x80042565 means booting in wrong mode (BIOS / UEFI). For instance, if your Hyper-V VM is Generation 1, it is a BIOS machine with MBR partitioning and can't create GPT partitions as in your answer file. For that, you need Generation 2 VM which is UEFI / GPT.

Here's a good post to read: Deployment error: Windows could not create a partition s technical blog

Kari