RicaNeaga

Solved the problem and made a thread about the solution for it here. Legolash, you can delete my previous posts, or move them to a separate thread if you want, but I think it's a good idea to mention about this problem in W7T, like a warning, so others won't waste their time, and maybe even yours with false errors for unnatended.

After having some problems with an unattended .xml file, I found out something interesting that I'm sure is really good-to-know. So, some speedy USB sticks have SSD controllers inside. Some of these flash drives (USB 2.0 and especially 3.0) are seen by windows and marketed as external SSDs, some not (ex: USB 3.0 drives that have SSD controllers). And for some reason (I don't know and I don't care why, another Microsoft snafu if you ask me) the Autounattend.xml file isn't working if you boot from one of these drives... maybe Autounattend file isn't the only thing that won't work. Tryed so far two of these drives (one Ridata USB 2.0 / eSATA SSD, one Corsair USB 3.0), and for both the Autounattend.xml didn't work. Fortunately there is a way to detect faulty (from Microsoft perspective) drives: Windows 7 USB/DVD download tool - Microsoft tool for making bootable USB drives. As you can see here, that Microsoft tool can't find the Ridata drive, even after removing any MBR and formatting it both NTFS and FAT32 with a low-format software. After I found an old flash drive that was ok with Microsoft tool, the setup became ~ completely silent with an Autounattend.xml I have, even if I booted and installed windows from a flash drive / USB stick. There are no problems with unattended when booting from a DVD, fyi. LE: Other tools for installing windows from an USB flash drive like RMPrepUSB, UltraISO PE, WinToFlash and W7T integrated USB Boot Prep tool, although are very successful at making those SSD-based drives to be bootable, ANY Autounattend.xml is useless from these kind of drives.

Ok, thanks. I used a second USB stick, and the result is the same for me - unattended options don't matter. I really don't know how this works for you on a LIVE system via USB. BTW, if anyone else has a working unattended xml file, please test it on your LIVE / WORKING system via USB, and not through tools like Virtual BOX, using any USB boot software you'd like (none work for me - I mean they do the job supposed to to - I am able to install windows, but the unattended options aren't preserved - doesn't matter with any of RMPrepUSB,UltraISO, WinToFlash or W7T). I've attached my working unnatended xml files for Windows 7 Home Premium x86 & x64, and also for Ultimate x86 & x64 - maybe it's best you please one of those, since I know it works 100% via DVD installation. You don't have to really install windows on your live system - if unattended works, the first step you see is choosing your partition to install (if you use one of the attached xml files). If not, the first step you see is choosing your locale (language etc.) Legolash, I know this disscusion is a little offtopic, please move some posts to a thread named smth like 100% unattended.xml doesn't work when installing from an USB stick. Thanks. unattended xml files.zip

Yes, same as with other softs. Unattended doesn't work when 7 is installed via usb. Din you installed on a live system? Or just on a virtual PC?

I tried all the softs above with tha same result - the unattended options aren't taken into account through the installation process. So it isn't 95% an usb format&preparing software issue. However, from what I've found so far, my problem was 100% due to installing from USB. If I install from a DVD, everything is ok with ANY unattended file. Can another forum member confirm this?

myselfidem, thank you very much for the help in this thread. I've managed to make a complete unnatended setup for windows 7 by changing one of your .xml examples in this thread, that was perfect for my needs. I attached it. However, I have some trouble. If I install from a dvd - everything is ok. If I install from an USB, the unnatended doesn't work. And it's not the software that helps make the usb bootable, I tried several with the same unwanted result. So, please check in WAIK if there is an option for unattended that needs to be checked if the origin of the installation process is an USB stick. Thanks.

UNBELIEVABLE FIND!!! I found out why NO unattended worked for me - I installed from USB!!! I used the same unnatended file from a cd and NO PROBLEM WHATSOEVER - a COMPLETE unnatended experience Before I did this I played with the various settings, and also thought the reason was that I deleted other OEM images besides Home Premium - WRONG again! Maybe it's just because of the software used - RMPrepUSB. I'll also try other install-7-from-USB softs like UltraISO, WinToFlash and, why not, W7T Sorry for the trouble, even more sorry for the time I managed to waste (not exactly in vain, but very close to), but I can concluse something after all :dancing:

Tryed various settings for unattended, none of them worked, even the one attached (I gave up the x86/x64 stuff, and also the serial) didn't. I will try another file generated by WAIK and see how that goes. Until then I ask you Legolash to check this problem - waiting however to see if other users are experiencing the same issues Autounattend.xml

Legolash, if you wanted my unattended file, it's 2 post back - post 164

Doesn't work aka the setup isn't unattended - i have to check ALL the options that were supposed to be hidden. Did you made a improvement regarding this issue in build 75? Thanks.

Autounnatended still isn't working. Used the attached file for a x86 Windows 7 Home Premium. I integrated it through WIM Manager, since AIO doesn't integrate it. Also I had some issuess integrating some custom tweaks. Maybe it's a problem with the tweaks, so I'll write about those in the tweaks thread. Autounattend.xml

First question: using /ai for the installer, are you sure no ngen optimization is run for the client version? I'm asking because I don't know why your addon is slower (not by much, but slower) to install then pegasus's one (from rvm). Second question: making two installers, one for client, one full, can be a good idea? First reason - less MB for the client version, second (presumption) - hopefully the client will be a little faster

Can confirm that a clean unnatended from build 71 is once again unfunctional. Hope the latest suggestions from other members will be useful Also, a suggestion - maybe it's netter you'd leave the serial blank, and not autocompleted by default with a 7 Ultimate key

Well, it doesn't for me on a live system . Tryed about 7-8 times with different files, all on LIVE systems. I can assure you it doesn't work.

I also have two suggestions: 1. In the ISO Maker, why not naming the iso automatically as the ISO Label + Disk at the end? Also there is a glitch... if I chose the name of the ISO to be the same as the name of the folder, when I press save, instead of keeping that ISO name it goes inside the folder, and the name I gave dissapears. The why not, for example, naming automatically an ISO 7Ultimatex64Disk that has the 7Ultimatex64 ISO Label, and also if the location of that foldet is C:\7Ultimatex64, then the location of the ISO should be C:\7Ultimatex64Disk automatically (and not inside the C:\7Ultimatex64 folder)... 2. As you can see here, if I choose load a previous preset, I can only load all presets. So if my updates preset included an old version of Solor's updates, I have to wait for W7T to load them all, then erase them all, and then load again the ones in the updates folder (including those updated). Wouldn't be a good ideea to give the users the choice to load only some presets (ex: only services and tweaks) instead of all? A box that can be ticked for each category of presets (tweaks, updates, etc) would be great...

Not until I've seen this post. However, used the AIO option to apply unnatended, and it didin't work. Also I remade the unnatended file with what myselfidem said (as attached) and it didn't work either. I'm giving up with tests, to me it's very clear that unnatended is a no-go with W7T Hoping you'll be able to make it functional soon... Autounattend.xml

Ok, I found out what was the trouble. So... If I installed only 7 without any drivers pre-slipstreamed, and then installed the official Intel chipset driver from its .exe, it didn't installed for this old laptop any drivers besides an AHCI one, that was later updated by the official RST. So, Intel preffers windows 7 to use its native Microsoft drivers for this old Intel configuration. However, in the chipset unpacked drivers, there is a windows 7 folder (named WIN7) that doesn't include any updates for the chipset drivers of my laptop, but there is also a universal folder (named All) thet contains drivers for xp and vista mainly, and if I point the driver update option to the All folder, the drivers are updated to these xp/vista versions. Same thing happens if I slipstream the All folder - the Microsoft drivers are updated by vista/xp ones. So there isn't any problem with DISM or W7T. In conclusion, I wasn't the only one to have a bad thinking - the guys at driverpacks are also in the same situation. They shouldn't make combined packs of drivers for vista and 7, because there are some manufacturers like Intel that prefers to have a very different approach regarding vista and 7 (in this case, chipset drivers, the WIN7 folder is 7 only, and All is for vista and older operating systems), I'll soon make a thread with the revised & sorted Windows 7 only specific drivers... to give an alternative is unfortunately is the only solution to the stubbornness of the guys from driverpacks, that continue to consider 7 and vista as the same os.

Tryed it without the skip user creation option checked, and it just won't work, also for a x86 iso. I'll also try the solution above, but that's it - autounnatended is clearly VERY buggy.

This doesn't happen to me. Tryed it (to remove speech support) for a 7 home premium x86 iso.

Still doesn't work. Gets very frustrating... Attached the file used now. These here are the options I checked, and also accept EULA and the Ultimate serial. Used Ultimate SP1 x64. Autounattend.xml

There are at least two BIG things that I'd like in W7T before 1.3.0 comes out - sorry to be a llitle offtopic. 1. A working unnatended with the ability to Auto-Select Language, Locale, Keyboard Locale (as requested by Chares here back in may); 2. that ability to slipstream multilanguage drivers you've made me drool about last week Also, adding some GREAT tweaks from here would be a BIG bonus also

Unfortunately, this doesn't work either. If you've got other suggestions, I'll try them. BTW, is it where it belongs? I mean the root of the dvd... the location... see here.

I'll try it today, in ~ 5 hours, and come back with feedback

With build 63, I used the attached unnatended on a x64 7 ultimate sp1 dvd, and during install, the only preserved and working setting was the time zone. Weird bug... Autounattend.xml Autounattend.xml

I can confirm that using /ai switch only client version is installed and no additional updates are needed through windows updates. So, besides beeing rather slow to install, everything is ok. Thanks again!