BatchPatch is free to try. The evaluation version is fully functional, but it allows a max of only 4 simultaneous target hosts in the grid. Additionally, the ‘Run BatchPatch as a service’ functionality is not available in the free evaluation.
The download below is delivered as a single batchpatch.zip file containing a single batchpatch.exe file. There is NO bundled crap-ware! Simply extract the .exe from the .zip, and then double-click on the .exe to launch BatchPatch.
Download: BatchPatch
Verify: How to Verify the Authenticity and Integrity of BatchPatch.exe
View: License Agreement
System Requirements:
- The BatchPatch console is supported to run on Windows 10, 11, 2012/2012R2, 2016, 2019, 2022. (NOTE: The BatchPatch console should generally be able to still run on older versions of Windows as long as they have .NET 4.6.2 installed, but we no longer officially support these older OS versions)
- The following operating systems are supported as target systems: Windows 10, 11, 2012/2012R2, 2016, 2019, 2022. (NOTE: BatchPatch can generally still even patch Windows versions going all the way back to Windows 2000 SP3/SP4 and Windows XP targets too, but we no longer officially support these operating systems)
- In order to use BatchPatch you must have the .NET Framework 4.6.2 installed on the computer you’re running it from. Target hosts do NOT need to have .NET installed.
- If you are using BatchPatch for the first time, please visit the Getting Started page to learn how to configure your environment to work smoothly with BatchPatch.
- For most actions, you’ll need to use an account that has local administrator access on the target remote hosts.
- Microsoft’s Sysinternals PsExec must either be saved to your Windows system PATH or in the directory that you launch BatchPatch from OR you may simply tell BatchPatch the exact location of psexec.exe on your computer by using ‘Tools > Settings > Remote Execution > Use psexec.exe custom filepath‘ (Note: psexec.exe only goes on the BatchPatch computer, not on the target computers). Another option is to simply drop psexec.exe into C:\Windows and that should do the trick. Launch psexec.exe one time to accept the license agreement. If during your first test run BatchPatch appears to be stuck on ‘Attempting to initiate Windows Update‘ or ‘Deployment: Initiating execution…‘ see this page for assistance.
- Target computers’ firewalls need to allow “Remote Administration” and “File and Printer Sharing” as explained here: Using BatchPatch with Windows Firewall