RicaNeaga

How did you uninstall it? It doesn't have a shortcut either in control panel's Programs and Features, either in Start Menu. The ''request'' was to make such an uninstall shortcut somewhere (preferably in programs from control panel) that works. And no, no other errors. The program via the control panel shortcut works just great, both on x86 and x64 versions

I'm verifying now all ''my'' addons for both x86 and x64 builds, and I've noticed one single problem - WhatInStartup is not uninstalable (both for x86 and x64). No biggie / no hurry, please check once version 1.36 is out. Thanks!

new skype is out (6.10.73.104). Thanks

I've noticed for 4.5.1 the installer's name changed a little. dotNetFx451_Full_LDR_x86_x64_Slim - what does LDR stand for? Any update for 4.5.1 will be installed only via LDR branch? This has changed from 4.5? And thank you very much for the update!

4.5.1 is now final. :dancing: Also, Pointzero was linking some new VC++ files from a hotfix, and also VC++ 2013 is available from Microsoft on the official page (scroll down).

Unfortunately I don't have a compatible device. It was for my drivers database. No biggie, hopefully the next installer will be more flexible... And thanks for the update!

Weird. I got a ''The setup command is invalid'' kind of error with /b via run with parameters. I also tried via cmd prompt. Are you sure you've tried the second link? Killer™ e2200, Wireless-N 1102, 1103 and 1202 32Bit (Version # 1.0.35.1273) for example. Probably I'm doing something wrong

Sorry for the little offtopic, but how do I extract files from InstallShield installers? To be more specific, I got stuck on this one (1.0.35.1273). Universal Extractor is useless unfortunately... Thanks in advance!

answered there. you need RSAT aka that update is for RSAT / Active Directory, not for the regular user.

Yep, not a WinToolkit problem, but a ''repository'' issue. See here.

Weird error only for the 2008 version. All other versions from the package install just fine. VBC installer (lite, without f# & j#), /y switch.

Latest version I see it's 1.7.6.85c. Please update when you'll have the time. Thanks.

Thanks, so one says his problems are gone with 9.4 version, one that they aren't. After I'll have the problematic hardware again, and play a little with it, I'll post a reply here.

When Intel made their chipset drivers windows 8 compatible, ~ when the first 9.3.x.xxxx version was released, and also when most of the .cat files grew in size from ~ 10kb to ~ 100kb (10 times the size), problems began when integrating with them in a windows 7 image. For example, on some (''older'') Intel chipsets after windows install video drivers couldn't be installed and stuff like that. I also noticed other people mentioned this. Now however I don't have any problematic Intel system available, so I'm asking - is it still happening with the latest (now windows 8.1 compatible) 9.4.0.1022 version? Again all of them were changed.

Actually it's recommended to install the directx redistributable. And it doesn't include only directx 9 & 10 files, but directx 11 files too. Some apps (especially games) need those to be installed, they don't come with windows, or so was the case with xp / vista / 7 and 8, I don't think 8.1 will be the exception.

Please include in a spoiler those reg tweaks that don't get applied.

I'm pretty sure it's alphabetical order for installers during RunOnce (I always used a number of''z'' letters in front of the ones I needed to be installed in a special order / lastly).

Yep, that is the safe route.

Laughed alot about the step-daughter issues btw, what's the finale? Also, please post here your autounnatended.xml. I have that one with the network skipped just fine, don't know why that's happening to you. LE: Nevermind, I saw it in your second post. Here's how mine looks like: <?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <UserLocale>ro-RO</UserLocale> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 HOMEPREMIUM</Value> </MetaData> </InstallFrom> </OSImage> </ImageInstall> <UserData> <AcceptEula>true</AcceptEula> <ProductKey> <Key>RHPQ2-RMFJH-74XYM-BH4JX-XM76F</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> </UserData> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>Admin-PC</ComputerName> <ProductKey>RHPQ2-RMFJH-74XYM-BH4JX-XM76F</ProductKey> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserLocale>ro-RO</UserLocale> <InputLocale>en-US; ro-RO</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <TimeZone>GTB Standard Time</TimeZone> <OOBE> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <NetworkLocation>Home</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> </OOBE> <AutoLogon> <Password> <Value></Value> </Password> <Enabled>true</Enabled> <LogonCount>2</LogonCount> <Username>Administrator</Username> </AutoLogon> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value></Value> <PlainText>true</PlainText> </Password> <DisplayName>Administrator</DisplayName> <Name>Administrator</Name> <Group>Administrators</Group> </LocalAccount> </LocalAccounts> </UserAccounts> </component> </settings></unattend>So, <NetworkLocation>Home</NetworkLocation> should do the trick and make the install process fully quiet. Also, if you don't want the network location wizard to ever pop up, use this tweak: Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\NetworkLocationWizard]"HideWizard"=dword:00000001[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Network\NetworkLocationWizard]"HideWizard"=dword:00000001

It's related to the fact that WinToolkit uses the DISM from the host machine. So probably windows 8.1 needs DISM from windows 8.1 to be ''manipulated''.

I give this one a bump as it seems like a very important bug, so I hope Lego won't miss it once he's back.

Nope, not through that Wintoolkit feature. If you want a simple solution, there isn't one. Best suggestion - make a silent addon via a .7z installer that includes that folder and a simple .batch files that has admin privileges.

Have you installed the latest directx redist files? Use this for example.

You can use a third-party tool like this one (simple and intuitive) to only mount the .wim and copy the ''WinToolkit_App'' folder to it. Of course, that is after everything is completed in WinToolkit. btw, I wasn't aware that when deploying over the network, only the contents of the .wim file were discoverable by windows installation process / WinToolkit's Runonce process.

Many of them were renamed, other ones (probably very old ones) removed. Check again all of them and most likely you'll find almost ''everything you think you've lost''.