search

memstechtips / UnattendedWinstall

Personalized Unattended Answer Files that helps automatically debloat and customize Windows 10 & 11 during the installation process.
MIT License
1.76k stars 234 forks source link

Error: Windows cannot read the <ProductKey> setting from the unattend answer file #49

Closed umermasood closed 2 weeks ago

umermasood commented 2 weeks ago

I just followed the instructions from your new video to flash the Windows 11 image For the unattend file I used the default IoT-LTSC-Like image you've provided. When I boot up Windows I get an error which says "Windows cannot read the setting from the unattend answer file" and then the system reboots.

This is what it looks like: Untitled

Apparently some other people have reported this issue in YouTube comments, maybe something is wrong with the unattend file so I am creating an issue here.

memstechtips commented 2 weeks ago

This is interesting, I just downloaded the latest Windows 11 23H2 ISO and downloaded the IoT-LTSC-Like .xml file and used AnyBurn to create the ISO.

I am able to install Windows perfectly fine. I'm not sure what the issue can be.

memstechtips commented 2 weeks ago

@umermasood I have just updated all of the files on the main branch to fix the formatting issues. Please test it again and report back.

Exmon2513 commented 2 weeks ago

I tested the new file, still got the same error as this guy. I tested it with the standard file.

memstechtips commented 2 weeks ago

Someone on my Discord server just reported when using the Media Creation Tool to create the bootable USB, the file doesn't work.

They used AnyBurn+Ventoy and then it worked. I also just tested using Rufus+Copying the .xml file to the usb flash drive and it worked.

raeffer commented 2 weeks ago

I have the same error using rufus and dragging and dropping the .xml file. I will try Ventoy method now and see if I have any joy.

memstechtips commented 2 weeks ago

Really interested to find out what's causing this issue because I haven't encountered it at all.

memstechtips commented 2 weeks ago

I just reproduced this issue and that is because of using the arm64 answer file on a x64/amd64 based system. 1720699169426

Each file has 2 versions: IoT-LTSC-Like x64/amd64 arm64

Standard x64/amd64 arm64

Each file has a comment that states which file it is, ex:

I am aware that @umermasood linked the correct x64/amd64 file when creating this issue, but when he created the issue, there were formatting issues in the XML files. I have updated and fixed that since. From all of my tests with all of the files, they all work perfectly fine, but I think you guys might be using the wrong version for your hardware.

raeffer commented 2 weeks ago

I redownloaded the answer file and remade installation media with ventoy and can report everything went perfectly. My racing sim is eternally grateful!!

memstechtips commented 2 weeks ago

@raeffer Perfect! I'm closing this issue in that chase. Have fun!