Best way to fully update a new installed Windows?

Question

I am wondering, what is the best way to automatically update a new installation of Windows (Windows 7)?

When I manually update a new install of Windows 7 SP1, I get about 45 updates. Installing those is not the problem, but after installing those, up come new updates. One installs them and then again: new updates and so on. All together it takes a long time - and you have to come back every few minutes to check for new updates and install them.

So, how is that done in business / how to automate this? Is WSUS a good way for this or does it only cache updates locally?

Using WSUS, is it possible to force immediate install of updates, reboot and install more updates automatically?

WSUS wouldn't help me, if updates are only installed when the system is shutdown, because then it again would require user interaction (shutting down the system, wait for reboot, shutdown again...).

Thanks for any hint!

Solution 1

Perform instructions below at your own risk: To automate windows update these instructions may or may not work for your system however it appears to work to an extent for Windows 7 as these instructions were tested on Windows 7.

MUST READ: 1. If the step below does not work verify then you are most likely part of a domain and your security policy may not allow you to perform steps below! 2. UAC prompts were also disabled for the duration of the windows updates so the batch files can run without interruption; be careful to restore this to default when done

Caution this step will make your computer less secure, immediately remove this after your computer is completely up to date. Set a reminder for 24 hours later if need be:

1. First you will have to make sure your computer automatically logs into a user. You can do this by clicking start menu, type "netplwiz", press enter or open the wizard, under the users tab, select your username, and un-check "require password", type your password, close this window.

2. Create 3 batch files to start the automated process. (Open notepad paste each code into a separate notepad and perform a save as corresponding_file_name.bat)

One. Save as: any_name.bat then copy this batch file to your startup folder for the user you made auto login. (Click start > All Programs > Startup)

start "" c:\autoupdate1.bat
exit    

Two. Save as: autoupdate1.bat then copy this to C:\ drive

wuauclt /detectnow
wuauclt /updatenow
reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" > nul && shutdown -r -t 0
start "" c:\autoupdate2.bat
exit

Three. Save as: autoupdate2.bat then copy this to C:\ drive

ping 127.0.0.1 -n 61 > nul
start "" c:\autoupdate1.bat
exit

Restart or open the batch file in the startup folder and watch the magic begin!

3. When it is completely done updating just delete the batch files from the startup folder & c:\ drive

Once again follow these instructions at your own risk as it can create an endless loop if you do not know how to stop this process by removing it from the startup folder or going into windows under safe-mode to remove the batch files

Final notes: If you run into issues running the batch files chances are you may have to look up how to disable UAC prompts for your Windows version

Solution 2

If you are starting from a bare metal install, you can slipstream updates into your installer disc so it already has updates in it (this depends on how many installs you're doing to make it worth it).

WSUS will not reboot your computer for you. It only keeps track of your updates and will act as a repo for updates so that rather than updating 300+ meg of updates from your Internet connection, they'll come from the local network. It can also control which systems get updates (I want to update IE for all the computers in HR, but restrict it from Marketing...) and give you reports on what updates your systems in the network have. The update mechanism sucks in terms of giving feedback of what is happening, but that's a shortcoming of Windows Updates. It also won't prevent the constant "You're updated! No, wait, you're not..." reboot cycles. Through group policy, you can have the system update with Windows Updates automatically on a scheduled basis just like regular Windows can be set to do individually if you don't mind becoming fully updated over a few days and leaving it on overnight to regularly check for updates and reboot.

Another method is to use the Windows Deployment Services (if you have, say, a lab of systems to update.) You take one of the systems, fully update and configure it, then sysprep it and upload that to the WDS server. Then netboot the subsequent systems and install the full image, fully updated. You have a lot of time invested in the first system but save time when you have 30 systems to install straight from the WDS server. Even if you don't create and auto-deployment script to finish the post-sysprep state you'll save a lot of time not having to do service packs, MS Office, custom installed software, etc. plus you can re-deploy the image when a system gets screwed up.

Otherwise you will have to do the updates repeatedly by hand, which as you've found, takes quite a bit of time. But at least you know that it was done without issues or errors.

Solution 3

I can highly recommend WSUS Offline Update. You can use it to create an USB stick or DVD which you can use afterwards to automatically install all critical updates for every currently supported Windows or Office version.

It will automatically restart and continue the update process, so you just need time but can let it work unattended.

Solution 4

Businesses do two things:

• First, have internal WSUS which makes updates faster.
• Second, they DO NOT INSTALL A FRESH WINDOWS.

They have an image with core drivers etc. that they maintain and regularly update. For example, we have a machine with Windows and the drivers that just updates and is not used, and every 3-6 months we use it as the base for a new image. Plus after every service pack.

A new machine gets the image and all updates since then. Not that many.

Solution 5

One of the problems you face is that it is not possible to install all the updates in one go because some are dependant on others and they may not be applied until the machine has rebooted. This is why you have to go through the update, reboot, update, reboot, etc. Using WSUS makes no difference as it's merely a distribution point for the updates and doesn't directly affect how those updates are applied, other then whether or not they are approved.

There are settings for Windows Update to install and reboot if necessary, although in my opinion it's ill advised as it's known to be troublesome. Have a look at either GPO or local policies for the relevant settings.

View more solutions

Comments

[John Gardeniers]

Not all businesses do things the same way, for all kinds of reasons.

[stefan.at.wpf]

thanks for your reply! if one uses the slipstreaming way, where to get all required updates? I know tools like WSUS Offline update [it's not from Microsoft], but I am wondering, if there is an official way?

[jscott]

With Group Policy, you can configure Automatic Updates to trigger a restart (if required) without user interaction after a timeout period. See this TechNet blog for some relevant information.

[user1364702]

This is probably as official as you'll get for Win7 support.microsoft.com/kb/913086

[MDMarra]

@stefan.at.wpf When I package updates with my thin image using DISM I just install a reference computer, check for windows updates and write down the KB number. You can find that on the Microsoft support site easily and download the MSU files for the update. Lather, rinse, repeat.

[ZJR]

Businesses of a certain size that own their employees' computers should really go trough a system image.

[Tommy Whitmore]

excellent, thanks for that. I'll have a look in to it

[Richard de Wit]

This is amazing!

[stefan.at.wpf]

This sounds awesome, thanks! I currently don't have this problem, but this shounds promising -> marked as answer. Thanks!

[Michael Kropat]

This is brilliant. Why not simplify it to one file like so? git.io/vzcYu