Etz

Quick question, is this appearing by intention or can it be hidden some way?

Then I dont quite understand why did you post it here, into my Bug report topic... :g:

Install.ini is not tied to Autounattended.xml in any way, at least to my knowledge...

Well modularity needs probably somekind of API (for possibility to create 3rd party modules) aswell so I doubt it will really happen due to time constrains... :g:

Well I have a MSDN subscription and definately it doesnt work on Images that are available from there. Tested Mostly on Windows 8(.1) Images, will try Windows 7 Image aswell, but so far it has always been working when XML is put into ther root if install media, so there is absolutely no need whatsoever to put it into sources folder. And it has it has been working this way from the launch for Windows Vista, so why try to fix and reimplement something that is not broken? Also, places where Setup will actually look (and in what Stage) for XML is described here: http://technet.microsoft.com/en-us/library/cc749415%28v=ws.10%29.aspx Apparently there is something wrong with your image then, from where did you acquire it? EDIT: Did a quick test on Windows 7 Ultimate SP1 x64 Image aswell, same result, works when XML is in root, does not work if its in sources folder. Image which I tested is this: http://msdn.microsoft.com/en-us/subscriptions/downloads/#FileId=46948

If it is in Sources folder, it wont work! At least on standard and unmodified images from MSDN or Retail DVD`s.

Tested, if XML is in Sources folder, Unattended Setup doesnt work at all...neither from DVD or USB.

In WinToolkit 1.4.38.5 AIO tool, apply Unattended (Quick option), XML is not copied into DVD root its copied into Sources folder instead. Also broken in latest Stable 1.4.37.20, worked fine on older versions. For sucessful USB install it must be in Installer root for UEFI install to suceed unattended, currently Setup will still prompt all the options. EDIT: Tested DVD install also, doesnt work. Copying Autounattended.xml "manually" back from sources folder to root (where it actually should be) helps.

Not quite...he could install it as Retail with default key...and activate with his OEM key afterwards as OEM...

This behaviour isn`t dependant on WinToolkit at all, its a Windows Setup feature. http://technet.microsoft.com/en-us/library/cc749415%28v=ws.10%29.aspx

Main problem with this approach is, that you have to Mount OS Image to even Get Into AIO tool Tweaks Tab... :g:

Well, you cant, but instead you could use pwoershell or VBS script to detect adapter and inject that reg key after that for corresponding adapter. There are plenty examples in the internet, how to Detect Adapter and change different parameters on it...

Same here... :g:

Re-tested with latest stable: 1.4.36.2, still works like a charm. I really owe you Lego, as this has been a real PITA for you to get this work properly. But as there are lots of other installers also, which use similar method for tweaking and customizing the Setup process, I think lot of users will actually benefit from this

Yes, I know that extracting them helps (I also have read this thread in his forum) but extracting/repackaging breaks the way, how I automatically keep all my installers up to date eq Automation. Also doesnt change the fact, that by default they cannot be installed silently and without Malware or Junk. Ofc, I could extract those, repackage all installers...but why should I, if there are better suitable alternatives? Anyway...wont generate anymore offtopic into this thread... PS: Just my 2 cents, if creating Unattended windows Installer with software (repackaging, etc, etc) takes more time, then actually installing those manual way, it pretty much defeats the purpose, at least for me...

I use K-Lite pack myself in conjunction with WMP (As K-lite pack is fully unattended and configurable via external install file) and I cannot remember my RyanVM forum logon details, but this is totally OT, I guess... Also Lego made major improvements to WinToolkit Installer lately, making possible to Install stuff, with external config files possible in WinToolkit too.

Sucess! :dancing: But now I already know that I have to remaster my image and try again: http://www.wincert.net/forum/topic/12077-some-problems-with-the-new-wintoolkit-installer/?p=106043 And I have to test Visual Studio 2013 XML anyway...

Sharks Codecs cannot be installed unattended AFAIK...and even I fthey would install, I wouldnt dare. He is pretty famous with Bundling varius Junk in hes Codecs. Well I understand that he needs to buy food too, but this is my choice.

Damn...I cannot test as fast as you can release

Built image from scratch, and still no joy... No CMD window, but install failed. Now it wrapped syntax between " marks. 03/21/2014 22:31:15.965 SETUP (0xb98) 0xb6c Click-To-Run aqkhc Medium CmdLine:"D:\WinToolkit_Apps\Office_2013_Professional\Setup.exe" "/configure D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml"As a result install failed: 03/21/2014 22:31:15.965 SETUP (0xb98) 0xb6c Click-To-Run aoh8e Monitorable HandleCommandLineAction::HandleStateAction: Invalid Admin command. Command: "/configure D:\WinToolkit_Apps\Office_2013_Professional\Setup.xml"Used latest stable 1.4.35

Your name is up there too, look above the "Lurker"..

No worries, as I always try to use youre "cutting edge" releases as I build Images solely only for my own personal purpose. If no one would use those, and report any possible hiccups, there would be no evolution and stable versions aswell...

I am pretty sure I havent integrated it multiple times as I always start testing with untouched copy And I dont use install.ini (well at least so far). Anyway will build new one from scratch tomorrow (khmm...technically today) evening, but now...off to bed I may have mixed something and used old sourcedir, but its easy to figure out, there should be 2 entries in the registry then? Will mount registry and check whats in there, will let you know (takes couple of minutes), as it indeed runs twice. EDIT: Registry at least has only one entry present... :g: Anyway as I really may have mixed things up and used already processed source, I will try again at the evening. To be sure I just deleted that directory, so no more mixups are possible

Hmm...now this looks odd... It looks like it ran Setup.exe twice, according to logs, install itself succeeded though. Anyway, will try to figure out what exactly went wrong, it shouldnt display any dialogs (and usually dont, no cmd window, no nothing that is why this XML is primarily used)

Most installers dont have a so detailed log, fortunately Office Click-to-run installer has, check the first line, it even logs syntax that you actually used to execute Setup.exe Makes script debugging pretty easy, heh..