Member Avatar for SDiBen

I have a series of stand alone business computers that are not allowed to be connected to the internet but yet I have to keep up with MS updates. Downloading the Microsoft monthly Security updates on ISO is helpful, but installing them on 7 PC's , one at a time is painful. I have to imagine there is a script that can be wrtten or perhaps a tool that is available pull from a local repository ( That I store the ISO or monthly updates in) . True?

  • 3 Contributors
  • 2 Replies
  • 349 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Bilal_3

Dani AI

Generated

: several practical ways exist to avoid seven manual installs each month. A low-effort route is to build a portable, offline update repository (so one USB installs many machines) or to use a scripted installer that applies the exact standalone packages in the correct order and logs results. As noted, scripting is perfectly reasonable; for less manual work the community tool WSUS Offline Update automates downloads into a USB-ready package. For manual control, the Microsoft Update Catalog is the canonical source for standalone .msu/.cab files, and the Windows Update Standalone Installer (wusa.exe) can install those packages quietly. (wsusoffline.com)

A pragmatic workflow that scales:

  1. Build the repo: either let WSUS Offline collect applicable files, or download the specific .msu/.cab files from the Update Catalog and copy them to a folder on the USB.
  2. Order and apply packages: ensure servicing‑stack updates (SSUs) are applied before rollups/cumulative updates when required; if maintaining the order by filename is easiest, prefix SSU files so they sort first. For installed systems use a short PowerShell wrapper that calls wusa.exe with /quiet /norestart, records exit codes, and queues a controlled reboot at the end. For offline images (WIM) use DISM /Add-Package instead. (learn.microsoft.com)

Small, practical PowerShell example to run from each machine (adjust paths and logging as needed):

$u='E:\Updates'; $log='C:\Temp\offline-updates.log'
Get-ChildItem $u -Filter *.msu -File | Sort-Object Name | ForEach-Object {
  Add-Content $log "$(Get-Date) Installing: $($_.Name)"
  $p = Start-Process -FilePath wusa.exe -ArgumentList "`"$($_.FullName)`" /quiet /norestart" -Wait -PassThru
  Add-Content $log "$(Get-Date) ExitCode: $($p.ExitCode)"
}
# After installs, reboot once during a maintenance window:
Restart-Computer -Force

Troubleshooting notes: test the USB on one machine first; verify bitness/Service Pack level matches each package; if installs fail, check Setup and Windows update event logs and run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow before retrying. Keep a manifest of which KBs were applied and capture logs for each machine. ’s manual-download approach maps directly to the Catalog workflow above; combining that with a small PowerShell wrapper gives a repeatable, auditable process. (learn.microsoft.com)

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

That tool here is a batch file. Almost every update has a commandline quietinstall option. So it should be easy to collect the updates on a stick and write a batch file to run each update.

As to the script it's batch 101 as in very easy so why would a tool be needed for that?

ISO wouldn't be my choice. My choice was a folder on the USB stick and the batch file I wrote for this month.

Member Avatar for Bilal_3

write a batch file which is helping in installing updatesthen download updates from windows. Run the batch file and your system will be updated. for more information about downloding updated click here.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.