How to check your Windows version (32-bit or 64-bit): Windows + Pause/Break → System type shows "32-bit operating system" or "64-bit operating system." Use the 32-bit fix on 32-bit Windows; use the 64-bit fix (SysWOW64) on 64-bit Windows. On 64-bit, you need to register both MSXML3.dll and MSXML4.dll from the SysWOW64 folder specifically — the regular System32 folder will not work for QB's 32-bit application files.

MSXML3.dll Unregistered or Corrupt

Primary cause — Microsoft Core XML Services DLL files are required for QB to parse XML data in company files and payroll templates. If MSXML3.dll (or MSXML4.dll on 64-bit) is not registered in Windows or is damaged, QB can't use it and reports C=343. Running regsvr32 re-registers the file in the Windows registry.

QB Compatibility Mode Enabled on QBW32.exe

When Windows Compatibility Mode is checked on QBW32.exe (telling Windows to run QB as Windows XP or Vista), QB's DLL loading mechanism behaves differently than on the current Windows version. This mismatch causes C=343 because QB can't load MSXML in the compatibility environment. Unchecking compatibility mode resolves this immediately.

Outdated or Discontinued QB Version

Older QB versions that no longer match the current Windows and DLL environment produce C=343 because QB's internal XML handling code expects older library versions that aren't compatible with updated Windows DLLs. Updating QB to a supported version resolves this variant.

Payroll Template or Company File Trigger

C=343 sometimes appears specifically when accessing payroll in QB or editing payroll templates. The payroll module uses MSXML extensively for form processing. If C=343 only appears in payroll/templates but not on the general QB screen, check and fix the payroll template first (QB → Lists → Templates → find damaged template → delete or restore from backup).

Windows Update Disrupted MSXML

Windows updates can occasionally affect MSXML component registrations — either by updating MSXML files without properly re-registering them, or by changing permissions on the DLL files. QB finds MSXML in an inconsistent state and reports C=343. Running regsvr32 after a Windows update fixes this.

Damaged QB Installation Files

A corrupted QB installation can leave MSXML DLL files missing or in a damaged state. The QB Install Diagnostic Tool scans and repairs MSXML alongside other Windows components needed for QB. This is the right tool when regsvr32 registration succeeds but QB still shows C=343.

METHOD 1 Register MSXML3.dll (and MSXML4.dll on 64-bit) 2 minutes — resolves most C=343 cases

METHOD 2 Uncheck Compatibility Mode on QBW32.exe Compatibility mode forcing QB to run as old Windows

METHOD 3 Reinstall Microsoft Core XML Services (MSXML.msi) MSXML files missing or regsvr32 failed

METHOD 4 Update QB + Run Install Diagnostic Tool + Open in Safe Mode Outdated QB or damaged installation after MSXML fix

What does regsvr32 do and is it safe to run?

regsvr32 is a built-in Windows utility that registers or unregisters Dynamic Link Library (DLL) files in the Windows registry. When you run "regsvr32 MSXML3.dll," Windows writes registry entries that tell programs where to find the MSXML3.dll file and how to call its functions. Running it for QB is safe — it only affects the registry entries for MSXML3.dll and doesn't modify any actual DLL files or your data. It's a standard Windows operation used by Microsoft and software vendors. You'll see a small popup confirming success ("DllRegisterServer in MSXML3.dll succeeded") or failure. Running it requires that the DLL file actually exists in the right location — if you get an error saying the file can't be found, use Method 3 to reinstall MSXML first.

Why does 64-bit Windows need SysWOW64 for this fix?

QuickBooks Desktop is a 32-bit application, even on 64-bit Windows. On 64-bit Windows, there are two sets of system DLL files: 64-bit DLLs in C:\Windows\System32\ and 32-bit DLLs in C:\Windows\SysWOW64\ (WOW64 stands for Windows on Windows 64). When QB (a 32-bit app) calls MSXML3.dll, it must use the 32-bit version in SysWOW64, not the 64-bit version in System32. If you run regsvr32 MSXML3.dll from System32, you'll register the wrong version and QB still can't find what it needs. Always navigate to C:\Windows\SysWOW64 first when running these commands on a 64-bit system.

Is Error C=343 related to company file damage?

Usually not — C=343 is almost always a Windows/DLL issue, not a company file problem. Your accounting data is safe. The C= series errors are QB internal processing errors related to how QB uses Windows components, not errors reading or writing your financial data. However, if C=343 appears only when opening a specific company file and not a sample file, the company file may have a payroll template or XML-based component that is damaged. In that case, run Verify/Rebuild Data after resolving the MSXML issue to check for data problems. The DLL registration fix should resolve C=343 regardless of which company file is open.