How to fix Error 2739 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: MSI Installer Error 2739 on SQL Server 2025

Why This Error Happens

Error 2739 occurs when the Windows Installer (MSI) attempts to invoke a VBScript or JScript custom action but fails because the scripting engine is not properly registered on the system. This is most commonly caused by vbscript.dll or jscript.dll being unregistered, corrupted, or blocked by Group Policy. On Windows Server 2025 and Windows 11, this can also happen if the installer is running under a 32-bit context while the required scripting components are only registered for 64-bit, or vice versa.

Step-by-Step Resolution Guide

Step 1: Re-register the VBScript and JScript Engines

  • Open an elevated Command Prompt (Run as Administrator).
  • Run the following command to re-register the 64-bit VBScript engine:
  • regsvr32 vbscript.dll
  • Run the equivalent command for JScript:
  • regsvr32 jscript.dll
  • If running a 32-bit installer on a 64-bit OS, repeat the commands using the SysWOW64 path:
  • C:\Windows\SysWOW64\regsvr32.exe vbscript.dll

Step 2: Check Group Policy and Script Host Restrictions

  • Navigate to Local Group Policy Editor (gpedit.msc).
  • Go to User Configuration > Administrative Templates > Windows Components > Windows Script Host.
  • Ensure “Disable Windows Scripting Host” is set to Not Configured or Disabled.
  • Restart the Windows Installer service via services.msc to apply changes.

Step 3: Clear the Windows Installer Cache

  • Open Command Prompt as Administrator and stop the Installer service:
  • net stop msiserver
  • Navigate to C:\Windows\Installer and rename the folder temporarily to Installer_old to clear corrupted cache files.
  • Restart the service:
  • net start msiserver
  • Re-launch the SQL Server 2025 setup executable.

Step 4: Run the SQL Server Installer in Compatibility Mode

  • Right-click the SQL Server 2025 setup file (setup.exe).
  • Select Properties > Compatibility.
  • Check “Run this program in compatibility mode for” and select Windows Server 2022 (or the closest previous version) if the Windows Server 2025 drivers haven’t fully stabilized for the specific build.
  • Apply changes and retry the installation as Administrator.

Alternative or Verification Steps

  • Verify the Fix: Check the SQL Server setup log file located at %ProgramFiles%\Microsoft SQL Server\160\Setup Bootstrap\Log\Summary.txt to confirm the installation completed without triggering Error 2739 again.
  • Alternative Solution: If the error persists, download the System Update Readiness Tool (DISM) and run DISM /Online /Cleanup-Image /RestoreHealth to repair underlying OS component corruption before re-attempting the SQL Server installation.