- Thread Author
- #1
I have Windows 7 Home Premium 32 bit (x86) , trying to install on x64 architecture (dual core atom proc). I am trying to boot from the DVD, with the Autounattend.xml file on a USB drive (Mushkin 8GB, light blinks when accessed, so I know it is being read from). I have also tried using the file name Unattend.xml per other suggestions.
My Autounattend.xml file does not get recognized. No errors are shown, but I explicitly set the locale, language, etc., to US English (en-Us), but I am still prompted by the Windows 7 DVD to select these settings.
Please help! I was unable to get this working for Vista, too, but I didn't have the ambition to sell that to people.
My catalog file that I used when building the answer file is from the DVD, and it is using x86 components for the 32 bit version of Windows.
My Autounattend.xml file does not get recognized. No errors are shown, but I explicitly set the locale, language, etc., to US English (en-Us), but I am still prompted by the Windows 7 DVD to select these settings.
Please help! I was unable to get this working for Vista, too, but I didn't have the ambition to sell that to people.
My catalog file that I used when building the answer file is from the DVD, and it is using x86 components for the 32 bit version of Windows.
AutoUnattend.xml can be placed on the root of any drive/usb/floppy where a dvd install will see it including root of dvd. Unattend.xml is used for other things.
I'd have to see your xml, remove serial or any sensitive data and attach and I'll take a look.
Here is examples Ask your Seven xml ? here - MSFN For
Error can be caught here MSFN
means you're installing on a 64 bit machine? No problemtrying to install on x64 architecture
I'd have to see your xml, remove serial or any sensitive data and attach and I'll take a look.
Here is examples Ask your Seven xml ? here - MSFN For
Error can be caught here MSFN
- Thread Author
- #3
Give me a little bit. I just realized I made a stupid mistake-- I installed the WAIK/OPK on a new install of Server 2008 R2, and I hadn't yet changed it to show all file extensions.
So the first problem was my actual file name was "Autoattend.xml.xml". Microsoft really knows how to screw with developers and system builders.
Now, I am wrestling with auto disk paritioning, and it seems like there are a lot of 'gotchas'. E.g., to extend a primary partition, you set Extend="true" in "CreatePartition," but specifying it in "ModifyPartition" causes an error (because the latter is for logical partitions within an extended partition only).
It looks like I may be good to go, but it didn't help that most of the Microsoft forums for Windows 7 were down last night when I needed an answer.
So the first problem was my actual file name was "Autoattend.xml.xml". Microsoft really knows how to screw with developers and system builders.
Now, I am wrestling with auto disk paritioning, and it seems like there are a lot of 'gotchas'. E.g., to extend a primary partition, you set Extend="true" in "CreatePartition," but specifying it in "ModifyPartition" causes an error (because the latter is for logical partitions within an extended partition only).
It looks like I may be good to go, but it didn't help that most of the Microsoft forums for Windows 7 were down last night when I needed an answer.
- Joined
- Jul 4, 2015
- Messages
- 8,983
I believe you cant do this with a standard windows install dvd. Nor can you do it with a Home license. This is the process for building a unattened install. Step-by-Step: Basic Windows 7 Deployment for IT Professionals
I believe you cant do this with a standard windows install dvd. Nor can you do it with a Home license. This is the process for building a unattened install.
But this doesnt solve my problem. i would like to know the instances in which autounttend file wont get recognized with above explanation
Similar threads
- Replies
- 5
- Views
- 5K