NTLite 23.11.9515 Windows 10 v1607 could not complete the installation

niros

New Member
Messages
18
Reaction score
1
Since version 23.11.9515 there is a problem to install windows v1607 on a second partition.

Steps for reproduction:
  • Use the original version of MS 14393.0
  • Preset 0
    • Remove 3 components
    • Add packages netfx3 and netfx48
    • Do some tweaks
    • Add the following diskconfig to autounattend.xml:
<ModifyPartition wcm:action="add">​
<Label>PC</Label>​
<Letter>C</Letter>​
<Order>1</Order>​
<PartitionID>1</PartitionID>​
</ModifyPartition>​
<ModifyPartition wcm:action="add">​
<Label>PD</Label>​
<Letter>D</Letter>​
<Order>2</Order>​
<PartitionID>2</PartitionID>​
</ModifyPartition>​

  • Remove the letter definition from autounattend.xml and the install works.
  • partition 2 gets the drive letter C.

Did I miss a setting in NTLite?
 

Attachments

Your disk layout needs to assign the <InstallTo> location, otherwise Setup will decide where to install Windows. Don't use drive lettering to force Setup's actions, it's not a reliable option.

When using a default NTLite disk template, <InstallTo> is automatically written for you. For a manual layout, on a dual-boot or multi-disk system, you should always click the Install to this partition button on the target partition.

View attachment 10959
 
Tested the preset on 1607, no issues.
It prompted to select the disk partition, and at the end prompted the usual OOBE.

Btw if you have "Windows could not complete" error, check online and try various ideas as it can be a Windows issue.
Make sure to do nothing to an unedited ISO when testing if NTLite/preset is the culprit.

It could be related to UEFI or a corrupted image that was started from.
 
Tested the preset on 1607, no issues.
It prompted to select the disk partition, and at the end prompted the usual OOBE.

Btw if you have "Windows could not complete" error, check online and try various ideas as it can be a Windows issue.
Make sure to do nothing to an unedited ISO when testing if NTLite/preset is the culprit.

It could be related to UEFI or a corrupted image that was started from.
Thanks for looking in this issue.

Still i get the same msg.

For the test I use the attached autounattend.xml and as update package Service Stack Update, this is only change we do (see attached preset) and we install in the second partition.


  1. Original 14393.0 Add autounattend - OK

  2. NTLite 9515 Add a Update Package - Error "Windows could not complete"
  3. NTLite 9477 Add a Update Package -Ok
  4. NTLite 9552 - Still problem for v1607
    Install on partition 2 after the second reboot "Windows could not complete"
 

Attachments

Last edited:
Back
Top