[SOLVED] Error While Installing Windows 10

[kazasker]

Hello,

I am getting this error when installing Windows 10:

"Could not parse the unattend response file of the Windows [specialize] migration, or
could not work. The settings specified in the response file cannot be applied, Error, [Microsoft-
Detected while processing Windows-Shell-Setup] component's settings."

Unattend file: https://transfer.sh/B2e4Na/autounattend.xml

My saved settings for NtLite: https://transfer.sh/McrQwM/Otomatik-kaydedilen oturum 0a20b25d.xml

View attachment 5435

 

[nuhi]

Probably the computer name.

The * can only be used on its own, not part of a name, as you typed.

If ComputerName set to an asterisk (*) or is included but empty (""), Windows creates a random 15-character name using up to 7 characters from FullName and Organization, then a dash, then more random characters.

ComputerName is a string with a maximum length of 15 bytes of content:

• ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.
• ComputerName cannot use spaces or any of the following characters: { | } ~ [ \ ] ^ ' : ; < = > ? @ ! " # $ % ` ( ) + / . , * &, or contain any spaces.
• ComputerName cannot use some non-standard characters, such as emoji.

If that doesn't help, then try Registered organization or owner without special Turkish (non-ACSII) characters.
But I believe it must be the computer name.
Will add detection if someone misuses * in the future.

Let me know how it goes.
Thanks.

 

[kazasker]

Probably the computer name.

The * can only be used on its own, not part of a name, as you typed.

If ComputerName set to an asterisk (*) or is included but empty (""), Windows creates a random 15-character name using up to 7 characters from FullName and Organization, then a dash, then more random characters.

ComputerName is a string with a maximum length of 15 bytes of content:

• ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.
• ComputerName cannot use spaces or any of the following characters: { | } ~ [ \ ] ^ ' : ; < = > ? @ ! " # $ % ` ( ) + / . , * &, or contain any spaces.
• ComputerName cannot use some non-standard characters, such as emoji.

If that doesn't help, then try Registered organization or owner without special Turkish (non-ACSII) characters.
But I believe it must be the computer name.
Will add detection if someone misuses * in the future.

Let me know how it goes.
Thanks.

You're amazing. The problem solved. Thank you much.

 

[crypticus]

for a reason this problem also happens to me when i do not have setupcomplete.cmd in the setup folder or oem folder.

 

[kazasker]

for a reason this problem also happens to me when i do not have setupcomplete.cmd in the setup folder or oem folder.

I have a solution for this. I will share it with you tonight.

 

[nuhi]

for a reason this problem also happens to me when i do not have setupcomplete.cmd in the setup folder or oem folder.

There is an option in Unattended, OEM SetupComplete, where it explicitly starts setupcomplete, maybe that.
Edit .\autounattend.xml and see if it mentions setupcomplete on one of the rows and remove the entire XML element - or recreate unattended without that option.

 

[crypticus]

There is an option in Unattended, OEM SetupComplete, where it explicitly starts setupcomplete, maybe that.
Edit .\autounattend.xml and see if it mentions setupcomplete on one of the rows and remove the entire XML element - or recreate unattended without that option.

probably that...