QuickBooks Web Connector Keeps Crashing: Every Fix, and the Permanent One

If the QuickBooks Web Connector keeps crashing — freezing mid-sync, showing "has stopped working," or taking QuickBooks Desktop down with it — this guide covers every fix that actually works, in the order worth trying. Then it explains why the crashes always come back, because that part matters more than any single fix.

No phone numbers, no "call our certified experts." Just the steps.

Fix it right now

Work through these in order. Most crash loops are resolved by one of the first four.

1. Update the Web Connector

Old QBWC builds crash against newer QuickBooks releases and newer Windows updates. Check your version (Help → About in the Web Connector) against the current release on Intuit's developer site, and install the latest. If the Web Connector broke suddenly across all your integrations on the same day, check whether Intuit shipped a bad update or had a certificate incident — it has happened before, and no local fix helps until they patch it.

This is the most common "crash" that isn't technically a crash. The Web Connector talks to QuickBooks through the same channel a human uses — and if QuickBooks is showing any modal dialog (an update prompt, a payroll notice, a "QuickBooks needs to close" box, even a stray message behind the main window), the connector's requests hang until they time out, and QBWC frequently falls over waiting. Open QuickBooks on the machine that runs the sync, dismiss every dialog, and try again.

3. Clear a corrupted log file (QBWC1085)

The Web Connector writes a verbose log (QWCLOG.TXT) constantly, and corrupts it regularly — especially after a crash or unclean shutdown, which makes this a self-perpetuating loop: crash corrupts log, corrupt log crashes startup.

Exit the Web Connector completely (right-click the tray icon → Exit).
Open C:\ProgramData\Intuit\QBWebConnector\log (ProgramData is hidden — paste the path into Explorer's address bar).
Rename QWCLOG.TXT to QWCLOG.OLD.
Restart the Web Connector. It recreates a fresh log.

If you're seeing the QBWC1085 error specifically, we have a dedicated QBWC1085 page with the full details.

4. Run both programs "as administrator" — consistently

QuickBooks and the Web Connector must run at the same elevation level. If one runs elevated and the other doesn't, Windows blocks the COM connection between them and QBWC errors out or hangs. Either run both as administrator or both as a normal user — mixed is what crashes.

5. Slow down the auto-run interval

Aggressive sync schedules crash the Web Connector. Intervals under roughly 5–15 minutes cause runs to overlap: the next sync starts while the previous one is still processing, and the two sessions deadlock or crash. Set every app's auto-run interval to 15 minutes or more, and stagger multiple apps so they don't fire together.

6. Check .NET Framework health

QBWC is a .NET application. If it crashes on launch or crashes Windows-side (check Event Viewer → Application log for .NET Runtime errors naming QBWebConnector.exe), repair the .NET Framework: Windows Settings → Apps → Installed apps → repair, or Intuit's Component Repair Tool. Then reinstall the Web Connector itself: uninstall from Apps, download the current version, reinstall, and re-add your .qwc files.

7. If QuickBooks itself crashes during the sync

When the QuickBooks process dies while the Web Connector is running requests, the problem is usually on the QuickBooks side:

Verify and rebuild the company file (File → Utilities → Verify Data, then Rebuild Data if it reports problems). Syncs hammer the file harder than normal use and surface latent corruption.
Switch to single-user mode for the sync if you can — large writes in multi-user mode are a known stress point.
Check the file size and network path. A company file opened over a network share is dramatically more fragile under sync load than one opened locally. Run the sync on the machine that hosts the file.

Why it keeps crashing

Here's the part the support threads never say plainly: the Web Connector's crashes are architectural, not configurational. It's a SOAP polling agent designed in 2002, and every one of the failure modes above traces back to that design:

It polls on a timer instead of responding to requests, so overlapping runs, timeouts, and hangs are built into the model.
It requires an interactive, logged-in Windows session and a running QuickBooks window, so any dialog, screen lock, reboot, or logoff kills it. (This is also why it can't run as a Windows service.)
It maintains its own fragile state — the QWCLOG file it corrupts, the .qwc registrations that break, the passwords it forgets — and it has no recovery logic for any of it.
Nobody is fixing it. Intuit's development effort is on QuickBooks Online; the Web Connector has been in maintenance mode for years. The version you're running today is as good as it will ever be.

That's why the fixes above are real but temporary. You will do them again — after the next reboot, the next QuickBooks update, the next Windows patch. If you've found this page more than once, you already know that.

The permanent fix

LedgerCrossing retires the Web Connector: a reliable local HTTP/qbXML pass-through for QuickBooks Desktop. It's a lightweight Windows system-tray app: your integration sends qbXML over a simple local HTTP POST and gets qbXML back — no SOAP, no polling timer, no QWCLOG to corrupt. It works with anything that can make a web request — which means it's for integrations you control (custom syncs, in-house scripts, middleware your developer maintains). Off-the-shelf apps that sync through the Web Connector are run by their vendors and can't be pointed at it; for those, the fixes above are the honest state of the art.

No more morning restarts. It auto-starts and runs quietly until you reboot on your terms.
Instant, on-demand sync instead of a 15–60 minute polling cycle.
Your data stays on your machine by default — and when off-site systems need in, you choose the path: a tunnel you run (free guide) or the built-in LedgerCrossing Remote relay ($39/mo, zero network config).
Readable logs that say what happened, instead of QBWC1085.
$299 one-time, per machine, unlimited company files. No subscription. Works with Pro, Premier, and Enterprise. 30-day money-back guarantee.

If you bill your time, the math is short: $299 is about one support incident's worth of babysitting the Web Connector — and this is the last one.

Buy LedgerCrossing — $299 →

Every QBWC Error Code, Fixed — the full error-code guide
QBWC1085: There Was a Problem With the Log File
Can You Run the Web Connector as a Windows Service?
QuickBooks Web Connector Alternatives in 2026

QuickBooks is a registered trademark of Intuit Inc. LedgerCrossing is an independent product for QuickBooks Desktop and is not affiliated with or endorsed by Intuit.