Anyone else having trouble with the unattended install not working? [resolved]

[Alex Corretor Do Brasil]

Anyone else having trouble with the unattended install not working?

 

[garlin]

You removed the OOBE component, and didn't specify in Unattended mode to skip OOBE.

                <c>microsoftwindows.client.oobe 'Pacote de Experiência de Recursos do Windows - OOBE'</c>

 

[Alex Corretor Do Brasil]

ObrigadoThanks my friend. But how do we specify to skip to OOBE?

 

[garlin]

It's right there in Unattended mode. But then you're responsible for providing all the other settings that OOBE normally asks from the user.

 

[Alex Corretor Do Brasil]

Even after all these procedures It is still not doing the standalone installation.

It's right there in Unattended mode. But then you're responsible for providing all the other settings that OOBE normally asks from the user.

 

[garlin]

Can you explain what isn't working for you?

 

[Alex Corretor Do Brasil]

Can you explain what isn't working for you?

The autonomous installation

 

[garlin]

I don't mind helping users, but you can't reply "it doesn't work" and expect an useful solution.

 

[Alex Corretor Do Brasil]

But the problem is just that, the unattended installation simply doesn't work, as if it didn't recognize the "autounattend.xml" file.

 

[garlin]

There were several problems with this preset.

1. Using "[KEY]" as the value for Product Key (Setup) doesn't actually work, because it's not a proper value for the unattended file.

If you're not using a specific activation key or a generic install key, then leave this field empty. The descriptive text for this setting implies "[KEY]" works, but NTLite is creating the unattended file with that string left in place (which is not legal).

2. You're making the mistake of reapplying all changes to boot.wim index #2 (and index #1, which isn't needed at all for installs).

The only real changes that need to be applied to boot.wim (index 2), are adding any missing drivers, copying a handful of Settings, or possibly importing a reg file if you can't use normal Settings to apply bypasses to boot.wim.

Other changes don't need to be re-applied to boot.wim, and can probably break something.

After removing boot.wim from most of the Reapply tasks across editions, the install is mostly unattended. It's not entirely unattended because you omitted any disk layout, so Setup stops to ask how to configure the system disk.

3. Running the Post-Setup command "rundll32.exe advapi32.dll,ProcessIdleTasks" serves no useful purpose. While it forces some existing tasks to run to completion, other post-install tasks are not triggered by this action. It only serves to make Post-Setup run slower than needed.

 

[Alex Corretor Do Brasil]

You say there's a disk layout omission, so Setup stops and asks how to configure the system disk. I had already configured this in another automation file, but it still didn't work, but I'll review it.

Regarding the key, I entered it this way because Ntlite itself tells me to, but I also entered the key manually in the file, and it didn't work. This time, I'll remove it.

Regarding the replications mentioned in item 2, they previously worked without issues. I'll review everything and report back to you.

Thank you for your patience and for taking the time to help me.

 

[Alex Corretor Do Brasil]

Here I am again, I was here reviewing my old automation file with these that I put here for you. I noticed that the problem is not NTLite but my automation file. And it wasn't any of the problems mentioned in our conversation, the problem was a specific setting that I had configured incorrectly.

 

[Alex Corretor Do Brasil]

I discovered that the problem is with Ventoy.
The standalone installation doesn't work with Ventoy, but it works outside of Ventoy.
However, I haven't tested it with the automation file generated by NTLite. I use the file generated by NTLite, but I mix it with "Schneegans."