Can anyone please re-upload version 11 of burfadel's Visual C++ Redist Installer? I've mistakenly deleted it and now mediafire decided to delete the link (again). I wanted to test it to see if the auto switch makes it completely silent...
Can anyone tell me why the following won't work-it cannot find any updates, yet, is located right in the folder containing all of the cabs in SoLoR's updates: the cmd works fine after Windows has logged in. This part of the answer file is run in OOBE at first log on. <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\Cabs\Installer_V23c.cmd"</CommandLine> <Description>Install Windows Core Updates</Description> <RequiresUserInput>true</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>2</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\Subsystem-for-UNIX-based-applications\Cabs\Installer_V23c.cmd"</CommandLine> <Description>Subsystem-for-UNIX-based-applications addin</Description> <RequiresUserInput>true</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>3</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\IIS\Cabs\Installer_V23c.cmd"</CommandLine> <Description>IIS updates</Description> <RequiresUserInput>true</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>4</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\KB982861.Internet.Explorer.9.0\Updates\Cabs\Installer_V23c.cmd"</CommandLine> <RequiresUserInput>true</RequiresUserInput> <Description>Internet.Explorer.9.0 updates</Description> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>5</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\MSMQ\Cabs\Installer_V23c.cmd"</CommandLine> <RequiresUserInput>true</RequiresUserInput> <Description>MSMQ updates</Description> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>6</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\NFS\Cabs\Installer_V23c.cmd"</CommandLine> <RequiresUserInput>true</RequiresUserInput> <Description>NFS updates</Description> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>7</Order> <CommandLine>"D:\Windows6.1_Updates_x64_SP1\SNMP\Cabs\Installer_V23c.cmd"</CommandLine> <RequiresUserInput>true</RequiresUserInput> <Description>SNMP updates</Description> </SynchronousCommand> </FirstLogonCommands>
try: Code: cmd /c "<path>\Installer_V23c.cmd" If that does not work try adding 'start /wait' Try something like this also, it should work no matter what letter drive your dvd/usb ends up as Code: cmd /c for %i in (D E F G H I J K L M N O P Q R S T U V W X Y Z) if exist "%i\Windows6.1_Updates_x64_SP1\S NMP\Cabs\Installer_V23c.cmd" do start /wait "%i\Windows6.1_Updates_x64_SP1\S NMP\Cabs\Installer_V23c.cmd" Edit: now that I read your question again I think it may be cmd related, you do not have a problem launching it
Thanks Ricktendo64; it's wierd because I have no problem with the line below in another variation of my answer files (a cmd file I built myself). I use this one when all updates are integrated into the image. Therefore, it must be something in Burf's cmd file that is throwing a fly in the ointment because I run it unmodified except the rename to make it shorter: <SynchronousCommand wcm:action="add"> <Order>1</Order> <CommandLine>D:\CustomFiles\CommandFiles\PostSetup\Runtimes_NET4_AIO</CommandLine> <Description>Create Directories, Install Runtimes</Description> <RequiresUserInput>true</RequiresUserInput> </SynchronousCommand> D: is a separate HDD that I use to store all my setup files and backups, so, it is always D Also, [Slim] .NET Framework 4 Full x86/x64 (12-29-2011) runs without error and does satisfy M$ update-first time I have used it-with the y switch. Thanks
You seem to have Windows6.1-KB2603229-x64.msu twice, in the main x64 directory and in a 'Not integratable to Offline image' directory. It's fine for x86 though. Keep up the excellent work!
For those that have tried the V24 Test installer, how has it worked for you? Have people tried the autoreboot feature etc? if any errors occurred, what were they etc? Thanks! Also I updated the Visual C++ link in my signature and added an alternative download for the main stuff. The rest of the stuff can be browsed through by the folder link. I also added a folder called 'Third Party' (not by me, and not modded, but maybe just recompressed for much smaller size). Contains the latest Intel Chipset and RST (AHCI driver, and RAID if installed), and one or two other potentially useful things.
question, why did u add autoreboot? does mean, after all updates are installed, it will reboot with or without warning? i thank you for great work..keep up
I mainly use your script for integration (then after to install any new hotfixes released that week) so the auto reboot feature is not something I am interested in. When you integrate the updates there is no slow down like I imagine there is when you do a batch online install
Autoreboot is an additional feature, added as option 3 in install updates menu. If you have a large number of updates that haven't been installed (such as a fresh install of Windows), the update process can get very slow due to the checking that is done by DISM (for what's installed and applied to the system already, and the pending updates previously installed). What autoreboot does is install 50 updates, reboot, load automatically upon windows login and continue installing in up to 50 update steps until all updates are installed. Even with the booting, it should be quicker than doing all 300+ updates at once. Its an extension of 'Only process updates that haven't already been installed' (option2). For installing a few updates (or even the bulk updates that have come out), you should use option 2, for installing on a fresh system, or a system that hasn't been updated using the repository, option 3 would be quicker. It does warn you that it will automatically boot once you choose it. Also, it requires UAC to be turned off so it can run properly after boot. When setting up a new system, UAC should be turned off anyway (since you should know what you are doing ), it can always be turned back on if required, such as for non-administrator logins etc. Note that I did rewrite the checking command for the processing of updates that haven't already been installed in this test 2, along with a few other changes that were minor. It should also reboot properly now.
Yes that true, integration is different because the updates are committed straight away and not added to the pending list. Integration is still something on my 'to do' list (he says sheepishly). On the plus side, the autoreboot feature is great for those that don't integrate . Actually, if post Windows install setup isn't explicitly time sensitive, the autoreboot feature is probably more realistic to use than integration, especially for single machine installs, since it saves making a new image. BTW the test installers are testing the principals etc. The description is yet to be changed, and the warning message will probably get some tweaking before the final V24.
sorry for this late answer. I checkt 2446710 on my x86 system. If I uninstall it, windows still offers the update for installation. How do I test? I uninstall the GDR to keep or LDR to keep updates und run Windows update to see what it offers.