Single Practical Fix

Fix Multisim Windows 11 "Cannot Read Database" Errors with a Jet 3.x Registry Batch Script

This tutorial covers a working field fix for 64-bit Windows systems where Multisim fails with database errors even after the official NI registry files do not fully resolve the problem.

Download the batch file Jump to run steps

Intro

If Multisim opens with database-related errors on Windows 11, the failure is often tied to the Jet engine mapping used by legacy database components. NI documents Jet registry corruption and corrupted user configuration files as two possible causes on 64-bit Windows, but this article is focused on a more direct batch-script method that worked in practice when the official .reg file approach was not enough.

This is not an official NI fix. It is a practical repair that forces the Jet 3.x win32 value to point to the NI-bundled msrd3x40.dll inside the Multisim installation folder, then verifies both the registry value and the DLL file.

Reference: NI KnowledgeBase, Problem Accessing the Database When Launching Multisim, updated Oct 28 2025.

Symptoms

  • Problem accessing the database
  • The Master Database cannot be accessed
  • Cannot open database created with previous version of your application
  • Empty component databases after launch
  • Database-backed features that stop loading or return read errors

Why this happens

This tutorial is for 64-bit Windows systems. NI documents the relevant 64-bit registry area as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0. The specific value repaired here is under:

HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x

The practical explanation is straightforward. Multisim still depends on older Jet-related behavior in the 32-bit registry space. If the Jet 3.x engine mapping is redirected, left behind by another installer, or otherwise corrupted, Multisim can end up looking at the wrong DLL. When that happens, database access can fail even though the main application is installed.

NI officially confirms Jet registry corruption as one possible cause and also notes corrupted user configuration files as another possible cause. This article does not cover the configuration-file repair. It focuses only on the batch-script approach that points Jet 3.x back to NI's bundled DLL.

Warning and backup note

Before you start

  • Close Multisim.
  • Make sure you are on 64-bit Windows.
  • Make sure you can run commands as an administrator.
  • Confirm the Multisim installation path on your machine.
  • Understand that corrupted user config files are an alternate cause, but they are outside the scope of this tutorial.

Install path note: the script below assumes C:\Program Files (x86)\National Instruments\Circuit Design Suite 14.3. If your Multisim version or install location differs, edit the NIDIR variable before running the batch file.

Batch script fix

This script changes only the win32 value under HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x. It points that value to:

C:\Program Files (x86)\National Instruments\Circuit Design Suite 14.3\msrd3x40.dll

It then reads the value back and checks whether the target DLL exists. If the DLL is missing, repairing or reinstalling Multisim may be necessary.

Download multisim-jet-fix.bat

@echo off
echo ============================================================
echo   Multisim Jet 3.x ISAM Fix
echo   Restores NI-bundled DLLs and redirects Jet 3.x engine
echo ============================================================
echo.

:: Check admin
net session >nul 2>&1
if %errorLevel% neq 0 (
    echo ERROR: Please run this as Administrator!
    echo Right-click the file and select "Run as administrator"
    pause
    exit /b 1
)

set "NIDIR=C:\Program Files (x86)\National Instruments\Circuit Design Suite 14.3"
set "REGKEY=HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x"

echo.
echo Step 1: Redirecting Jet 3.x ISAM to NI-bundled msrd3x40.dll...
echo.

reg add "%REGKEY%" /v "win32" /t REG_SZ /d "%NIDIR%\msrd3x40.dll" /f
if %errorLevel% equ 0 (
    echo   Registry updated successfully!
) else (
    echo   ERROR: Failed to update registry
)

echo.
echo Step 2: Verifying...
echo.

for /f "tokens=2*" %%a in ('reg query "%REGKEY%" /v "win32" 2^>nul ^| findstr "win32"') do (
    echo   Current value: %%b
)

echo.
if exist "%NIDIR%\msrd3x40.dll" (
    echo   NI msrd3x40.dll: PRESENT
) else (
    echo   NI msrd3x40.dll: MISSING - this needs to exist!
)

echo.
echo ============================================================
echo   Done! Try launching Multisim now.
echo   If it still doesn't work, you can revert with:
echo   reg add "%REGKEY%" /v "win32" /t REG_SZ /d "C:\Windows\SysWOW64\msrd3x40.dll" /f
echo ============================================================
echo.
pause

How the script works

  • net session blocks execution if the batch file is not running as administrator.
  • NIDIR is the National Instruments installation directory. Change it if your version is installed in a different folder.
  • REGKEY targets only the Jet 3.x engine key under the 64-bit Windows 32-bit registry branch.
  • reg add updates only the win32 value.
  • reg query reads the value back so you can confirm the exact path now stored in the registry.
  • if exist confirms the target msrd3x40.dll is physically present where the registry now points.

How to run it

  1. Download multisim-jet-fix.bat.
  2. If needed, edit the NIDIR line so it matches your installed Multisim path.
  3. Right-click the file and choose Run as administrator.
  4. Let the script finish.
  5. Launch Multisim again and test database access.

How to verify

The script verifies the registry value immediately after writing it and checks whether the target DLL exists. You can also confirm the registry value manually with this command:

reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x" /v "win32"

The returned path should match the NI-bundled DLL inside your Multisim install directory.

How to revert

If you need to point Jet 3.x back to the Windows copy, run this from an elevated Command Prompt:

reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x" /v "win32" /t REG_SZ /d "C:\Windows\SysWOW64\msrd3x40.dll" /f

The fallback path above points to the Windows SysWOW64 copy.

Troubleshooting

  • The script says to run as Administrator: right-click the file and run it with elevated permissions.
  • The value changed, but Multisim still fails: double-check the install path in NIDIR. A version mismatch is enough to break the fix.
  • The script reports the DLL is missing: repair or reinstall Multisim so the NI-bundled msrd3x40.dll is restored.
  • The registry looks correct and the DLL exists, but the error remains: the alternate corrupted user configuration-file cause documented by NI is the next thing to check.

FAQ

Does this change the whole Jet branch?

No. It changes only the win32 value under HKLM\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x.

Is this for 32-bit Windows?

No. This tutorial is specifically for 64-bit Windows systems.

What if the official NI article did not fully fix my system?

That is exactly the gap this page is meant to address. NI documents the registry issue, but the batch script here is the practical method that succeeded when the provided registry files were not enough.

Summary

If Multisim on Windows 11 cannot read its database, one practical fix is to force the Jet 3.x win32 mapping back to NI's bundled msrd3x40.dll, then verify the registry value and the DLL file. Back up the registry first, run the script as administrator, and repair or reinstall Multisim if the target DLL is missing.