Skip to main content

How to Create a Self-Updating Batch Script

Maintaining scripts across multiple machines can be a logistical nightmare. Every time you fix a bug or add a feature, you have to manually copy the new file to every workstation. A better solution is a "Self-Updating" script. When launched, the script checks a central server for a newer version, downloads it if available, and replaces its own code before continuing.

This guide will explain the "Replace-on-the-fly" technique required to bypass Windows file locks and create a self-updating Batch script.

The Challenge: The File Lock​

Windows prevents you from deleting or overwriting a .bat file while it is actively being executed by cmd.exe. To update a script, you must use a three-step dance:

  1. Check: Compare Version A (Local) with Version B (Remote).
  2. Shadow: Download the new file with a temporary name (e.g., update.tmp).
  3. Swap: Launch a separate process that kills the current script, performs the swap, and restarts the new version.

Method: The Remote Version Check​

This implementation uses curl (native in Windows 10/11) to download a version number from a web server.

@echo off
setlocal

set "CurrentVersion=1.0"
set "UpdateURL=https://myserver.com/script/version.txt"
set "ScriptURL=https://myserver.com/script/myscript.bat"
set "TempVer=%temp%\remote_ver_%~n0.txt"
set "TempScript=%~dp0updater_temp.bat"
set "SwapScript=%temp%\swap_%~n0.bat"

echo [UPDATE] Checking for updates (current: v%CurrentVersion%^)...

:: Verify curl is available
where curl >nul 2>&1
if %errorlevel% neq 0 (
    echo [INFO] curl not found. Skipping update check.
    goto :MainLogic
)

:: 1. Download the remote version number
curl -s -f -o "%TempVer%" "%UpdateURL%" 2>nul
if %errorlevel% neq 0 (
    echo [INFO] Could not reach update server. Running current version.
    del "%TempVer%" >nul 2>&1
    goto :MainLogic
)

:: Read the remote version
set "RemoteVersion="
set /p "RemoteVersion=" < "%TempVer%"
del "%TempVer%" >nul 2>&1

if not defined RemoteVersion (
    echo [WARNING] Empty version response. Skipping update.
    goto :MainLogic
)

:: 2. Compare versions
if "%CurrentVersion%"=="%RemoteVersion%" (
    echo [OK] Script is up to date (v%CurrentVersion%^).
    goto :MainLogic
)

echo [UPDATE] New version v%RemoteVersion% available!
echo         Downloading...

:: 3. Download the new script to a temporary file
curl -s -f -o "%TempScript%" "%ScriptURL%" 2>nul
if %errorlevel% neq 0 (
    echo [ERROR] Failed to download update. Running current version.
    del "%TempScript%" >nul 2>&1
    goto :MainLogic
)

:: 4. Verify the downloaded file is not empty
for %%F in ("%TempScript%") do (
    if %%~zF equ 0 (
        echo [ERROR] Downloaded file is empty. Aborting update.
        del "%TempScript%" >nul 2>&1
        goto :MainLogic
    )
)

echo [UPDATE] Download complete. Restarting to apply v%RemoteVersion%...

:: 5. The Self-Replacement Trick
:: Create a tiny temporary script that waits for us to exit, then swaps the files.
(
    echo @echo off
    echo timeout /t 2 /nobreak ^>nul
    echo move /y "%TempScript%" "%~f0"
    echo if errorlevel 1 (
    echo     echo [ERROR] Failed to apply update.
    echo     pause
    echo     exit /b 1
    echo ^)
    echo start "" "%~f0"
    echo del "%%~f0"
) > "%SwapScript%"

start "" "%SwapScript%"
exit

:MainLogic
echo.
echo --- Running v%CurrentVersion% ---
:: === Your actual script code goes here ===
echo Script is operational.
:: === End of main logic ===

pause
endlocal

Why this works:​

  • %~f0: This refers to the Full path of the current script.
  • start "" "%SwapScript%" & exit: We launch the "swapper" and then immediately terminate the main script. This releases the file lock, allowing the swapper to successfully move the new file into the old location.
  • move /y: The /y flag overwrites the existing file without asking for permission.
  • -f flag on curl: Makes curl return a non-zero exit code on HTTP errors (like 404), so the script can detect download failures.

Alternative: Using BITSADMIN (Legacy Support)​

If you are on an older version of Windows (like Windows 7) that doesn't have curl, you can use the Background Intelligent Transfer Service.

:: Download with BITSADMIN (available on Windows 7+)
bitsadmin /transfer "ScriptUpdate" /download /priority normal "%ScriptURL%" "%~dp0new_version.bat"

if %errorlevel% neq 0 (
    echo [ERROR] BITSADMIN download failed.
)

How to Avoid Common Errors​

Wrong Way: Downloading directly into the live filename​

If you run curl -o "myscript.bat" ... while myscript.bat is running, the command will fail with "Access Denied." You must download to a temporary filename first.

Problem: Infinite Update Loops​

If you forget to update the CurrentVersion number inside your new script before uploading it to the server, the script will see the "New" version is still higher than its local version and update itself in a loop forever.

Best Practice: Always verify that your remote version.txt and the version number inside the new script match before publishing the update.

Problem: Corrupted downloads​

If the network connection drops mid-download, the temporary file will be incomplete. Running a corrupted script could produce unpredictable errors.

Best Practice: Verify that the downloaded file is not empty before attempting the swap (as shown in step 4 of the main method).

Best Practices and Rules​

1. Security First​

Allowing a script to download and execute code from the internet is a security vector. Ensure your UpdateURL uses HTTPS to prevent Man-in-the-Middle attacks. Consider verifying a checksum of the downloaded file before applying it.

2. Error Handling (Offline Mode)​

If the user has no internet connection, the curl command will fail. Your script should detect this and proceed with the current version rather than crashing (as shown in the main method).

3. Cleanup​

Ensure the temporary version file is deleted after reading. The swap script deletes itself (del "%%~f0") as its final action.

Conclusions​

Creating a self-updating Batch script transforms a simple tool into a managed application. By utilizing the "swapper script" technique, you can overcome the limitations of Windows file locks and ensure your entire user base is always running the latest, most secure version of your automation. This approach is essential for any long-lived Batch project deployed across a network or to multiple remote clients.

Table of Contents