QuickBooks Desktop was working. Now clicking the icon does one of three things: a splash screen flashes and disappears, a crash dialog interrupts the launch, or nothing happens at all. This is a different problem from an installer failing mid-setup, and it's a different problem from one specific company file refusing to open — QuickBooks itself won't start, independent of any file.

That distinction matters because it changes where you should be troubleshooting. A numbered error like 1603 or 1722 appearing while setup itself was still running points to a Windows Installer problem, covered in our piece on QuickBooks Desktop installation errors — the fixes there won't help you here.

‍

A program that opens fine but throws an error on one specific company file is a file-level problem, not a program-level one. This page is for everyone else: QuickBooks itself, as a program, will not launch.

The good news is that Intuit documents this as a small, specific set of causes — a damaged local settings file, a damaged licensing-data file, a Windows security policy that blocks the program outright, or a background process getting in the way. None of it requires reinstalling Windows, and reinstalling QuickBooks itself is the last step, not the first.

Which Symptom Do You Have?

Before running through the full sequence, it helps to know which pattern matches what's on your screen. Intuit's own support documentation treats these as related but distinct starting points.

‍

What you seeWhat's most likely happeningWhere to start

‍The "Opening QuickBooks" splash screen appears, then disappears, and nothing opensA damaged local configuration file, a damaged licensing file, or — on some Windows 10 Pro and higher machines — a Windows security policy blocking the programTool Hub Quick Fix, then the file-rename steps belowQuickBooks opens partway, then Windows shows a "QuickBooks has stopped working" dialogAn overly long company name, a damaged QBWUSER.INI file, or damaged program filesTool Hub Quick Fix, then the same file-rename stepsThe program hangs indefinitely on the loading screen, or clicking the icon does nothing at allA background process conflict, or a program installation that's become corrupted

Tool Hub Quick Fix first, then Selective Startup isolation and the Install Diagnostic Tool if it persists

Two other patterns are worth naming so you don't work through the wrong fix. A program that opens normally while one specific company file won't is a file-level problem rather than a program-level one, covered in our piece on company files that won't open in QuickBooks Desktop instead of this page. A window that opens but looks blank, tiny, or has fuzzy icons is a display problem, not a launch failure — covered separately near the end of this page.

The Official Fix Sequence

Work through these in order. Each step is designed to try the least invasive fix before the more disruptive one, so don't skip ahead to reinstalling before you've tried the steps that don't require it.

‍

1. Close QuickBooks completely and download QuickBooks Tool Hub fresh from Intuit. Don't reuse an installer you downloaded previously, and don't get it from a site other than Intuit's own servers. Tool Hub is updated on its own schedule, and running an outdated copy is a common reason a "fixed" problem resurfaces. Save the QuickBooksToolHub.exe file somewhere easy to find.

‍

2. Install Tool Hub, then run Quick Fix my Program. Because it closes background processes QuickBooks is currently using and runs a fast repair without touching anything else, this is the lightest fix Intuit provides — and it resolves a meaningful share of launch failures on its own, typically in a couple of minutes. Open the file you downloaded, accept the terms, and let it finish installing. Once Tool Hub is installed, select the Program Problems tab, then "Quick Fix my Program." Try opening QuickBooks again before moving to the next step.

‍

3. Isolate whether the program or a specific file is the problem. Still stuck after Quick Fix? Close every window, then open QuickBooks without letting it automatically load your last company file: hold Alt while selecting Open, or hold Ctrl while double-clicking the QuickBooks icon to suppress your saved application settings. A program that opens this way is fine — the problem sits with a specific file, a different issue than this page covers. One that still won't open even with nothing loading confirms the problem is the program itself, and the next steps address that directly.

‍

4. Rename QBWUSER.ini. This file stores your local QuickBooks application settings, and Intuit documents a damaged copy as a direct cause of the splash screen vanishing or a stopped-working crash. Open File Explorer and navigate to C:\Users\[your username]\AppData\Local\Intuit\QuickBooks [year]\. Right-click QBWUSER.ini, select Rename, and add .old to the end of the file name. QuickBooks rebuilds this file automatically the next time it opens successfully. The only side effect is that your list of recently opened company files resets — nothing about the files themselves is touched.

‍

5. Rename EntitlementDataStore.ecml. This is the file QuickBooks uses to verify your license locally, and Intuit documents it as a separate common cause of the same symptom. It takes about a minute: press Windows+R, type C:\ProgramData\Intuit\Entitlement Client\v8\, and press Enter.

That folder is hidden by default, so if Windows says it doesn't exist, turn on "show hidden files and folders" first, then try again. Right-click EntitlementDataStore.ecml, select Rename, and add .OLD to the end. Like the file above, QuickBooks regenerates it automatically; you may be prompted to re-validate your license the next time the program opens, which is expected. A fresh copy of this same file later throwing its own licensing or activation problem, rather than a launch failure, is a distinct issue covered in our piece on QuickBooks Desktop license and product number errors.

‍

6. Run the QuickBooks Install Diagnostic Tool. Back in Tool Hub, select the Installation Issues tab, then "QuickBooks Install Diagnostic Tool." This checks and repairs underlying Microsoft components QuickBooks depends on, not just QuickBooks' own files. It can take up to 20 minutes — let it finish without interrupting it, then restart your computer before opening QuickBooks again.

‍

7. Repair the QuickBooks installation through Windows itself. Because this replaces damaged program files without removing your settings or license data, it's worth trying before a full reinstall: open Windows' own Programs and Features (or Apps & Features on newer Windows versions), find QuickBooks Desktop in the list, select it, and choose Repair rather than Uninstall. Plan for 10 to 15 minutes, most of it unattended.

‍

8. Uninstall and reinstall as a last resort. When the program files themselves are too damaged for a repair to fix, a clean uninstall followed by a fresh install from a newly downloaded installer is what resolves it. This is the most disruptive step on this page and the only one likely to take longer than 20 minutes, so it belongs last. Your company file lives separately from the QuickBooks program and isn't affected by this step, but back it up first as routine practice regardless.

‍

How you'll know it worked: QuickBooks opens to its normal startup screen — either the No Company Open window or your last company file loading — without a crash dialog or a vanishing splash screen. That's the sign the program itself is healthy again.

The Windows Security Setting That Can Block QuickBooks Entirely

One cause is easy to miss because it lives in Windows, not in QuickBooks: a Group Policy setting called "System cryptography: Use FIPS compliant algorithms." When this policy is turned on, it can block QuickBooks Desktop from launching at all, and Intuit documents it specifically for the vanishing-splash-screen symptom.

To check it: press Windows+R, type gpedit.msc, and press Enter to open the Local Group Policy Editor. Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Find "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing," and set it to Disabled. Restart your computer, then try opening QuickBooks again.

One caveat worth knowing before you look for this: Group Policy Editor isn't available on Windows Home editions, only on Pro, Enterprise, and Education. If your machine is running Windows Home, this specific fix path doesn't apply, and you can skip to the other causes on this page.

This is a different problem from your operating system itself not meeting QuickBooks' requirements at all. A Windows edition or mode QuickBooks doesn't support in the first place makes a launch failure a symptom of that broader mismatch, not something Tool Hub or a policy change can fix — see our coverage of getting QuickBooks running on an unsupported Windows 10 setup if that fits what you're seeing.

When the Cause Is a Background Process, Not QuickBooks Itself

Intuit's own documentation names "background process conflicts" as one of the causes behind QuickBooks failing to open — something else running on the machine interferes with QuickBooks before it can finish loading. Antivirus software, another accounting or backup tool, or a third-party utility can all cause this, and it's often invisible from QuickBooks' side alone.

Because the goal is to strip away everything except what Windows itself needs to run, so you can tell whether something else is truly the interference, Selective Startup — a Windows mode reached through the System Configuration utility — is the way to isolate it. Worth knowing up front: Intuit documents Selective Startup primarily as an installation and uninstallation step, not as a fix written specifically for this exact launch-failure symptom. Using it here is a reasonable extension of the same background-process-interference logic Intuit does name as a "won't open" cause, not a claim that Intuit's own Selective Startup instructions were written for this symptom.

To use it: press Windows+R, type msconfig, and press Enter. On the General tab, choose Selective Startup and make sure Load System Services is checked. Switch to the Services tab, check Hide All Microsoft Services, then select Disable All. Uncheck Hide All Microsoft Services again, find Windows Installer in the list, and check it back on. Select OK, then Restart when prompted.

Try opening QuickBooks with only essential services running. A successful launch means something in your normal startup lineup was the interference. When you're done testing, return to Normal Startup the same way (msconfig > General > Normal Startup > OK > Restart) rather than leaving the machine in this reduced state.

A launch failure that started right after a Windows update installed, rather than out of nowhere, points toward this same category of cause — a recent update is a common trigger for exactly this kind of interference, and it's addressed specifically in our piece on QuickBooks Desktop compatibility problems following a Windows update.

If QuickBooks Opens But the Window Looks Wrong

Getting past the splash screen and seeing the program, but with a window that's blank, unusually small, or has fuzzy icons and text, is not a launch failure. It's a display-scaling problem, common on high-resolution or multi-monitor setups, and Intuit's fix for it is different: adjusting the QuickBooks.exe compatibility settings for high-DPI scaling, switching QuickBooks to One Window view under Preferences, and confirming your Windows display resolution is set high enough. None of the steps above will fix a rendering problem, so that's the path to follow instead when this is what you're actually seeing.

When to Stop Troubleshooting and Get Help

Most launch failures resolve at Quick Fix my Program or the file-rename steps. Working through the full sequence above — including a Windows repair and, if necessary, a clean reinstall — without QuickBooks opening is a reasonable point to stop repeating the same steps.

It's worth escalating sooner, rather than continuing to retry, if the identical failure shows up on a second machine (which points toward something environmental rather than one damaged local file), or if the delay is costing real business time. Once QuickBooks is open and working again, a program that later freezes or becomes unresponsive during use is a separate, distinct problem from a launch failure — see our coverage of QuickBooks Desktop freezing or crashing after it opens if that's what happens next. And if the program opens successfully but stops you at a sign-in screen instead, that's a different failure point too, addressed in our piece on troubleshooting QuickBooks Desktop sign-in problems.

Frequently Asked Questions

Will renaming QBWUSER.ini or EntitlementDataStore.ecml delete anything important?

No. Both files store local settings and license-verification data, not your financial records. QuickBooks rebuilds each one automatically the next time it opens successfully. The only visible side effect is that your recently opened file list resets, and you may need to re-enter or re-validate your license information once.

‍

Do I need to be online for these fixes to work?

An internet connection helps, particularly for the Install Diagnostic Tool and for QuickBooks to re-validate your license after the EntitlementDataStore.ecml rename, but the file-rename steps themselves work offline. Connect before finishing the sequence if you can.

‍

Why does QuickBooks open fine on one computer but not another with the same company file?

Because a launch failure, by definition, is local to the machine — a damaged settings file, a Windows security policy, or a background process conflict all live on that specific computer, not in the company file itself. A company file that opens on one machine and not another points toward a file- or network-level issue instead, which is covered separately from this page's scope.

‍

Is it safe to disable the Windows FIPS setting, and will it affect other programs?

This setting controls which encryption algorithms Windows enforces system-wide, and Intuit documents disabling it specifically as a fix for this QuickBooks symptom. An organization with a specific compliance reason for requiring FIPS-compliant encryption should have whoever manages that policy sign off before it's changed, since other software that also checks this setting can be affected.

‍

Why does the same launch failure keep coming back after I fix it once?‍

The most common reasons are running an outdated Tool Hub installer instead of a fresh download, or a Windows update or security-software update silently re-damaging the same local file each time. Downloading Tool Hub fresh from Intuit whenever you troubleshoot, rather than reusing an old copy, avoids the first cause.

Bottom Line

A QuickBooks Desktop program that won't launch is almost always traceable to one of a few specific, well-documented causes: a damaged QBWUSER.ini or EntitlementDataStore.ecml file, a Windows FIPS security policy, or a background process getting in the way — not a deeper problem with your company file or your installation as a whole. Work through Tool Hub's Quick Fix first, then the two file renames, then the Install Diagnostic Tool, then a Windows repair, with a full reinstall as the last resort rather than the first move. If the FIPS policy or a background process turns out to be the cause, both have a specific, documented fix rather than requiring guesswork. And if this isn't actually your symptom — if setup itself failed, or one company file won't open, or the OS itself isn't supported — the more precise page for that problem will get you there faster than working through this sequence for a launch failure you don't have.

‍