Clearing the Intuit Account sign-in loop in an older QuickBooks Desktop install

An Intuit Account prompt that never resolves can block your company file in an older QuickBooks Desktop version. Here is how to stop the loop.

You open the company file, the Intuit Account window appears, you sign in, and the same window comes straight back. The ledger is intact. What has failed is the handshake between your frozen install and the account system behind it. Our engineers clear this loop on older Desktop versions regularly, and the fix needs no upgrade.

The loop lives in the credential cache, not in your file

Several Desktop editions ask for an Intuit Account at open when the company file uses connected services such as bank feeds or payments. After the first successful sign-in, the install stores a token locally and reuses it quietly. That token is the weak point.

When the vendor reshapes its account platform on the server side, older tokens are invalidated. Your version keeps presenting the dead token, gets refused, and shows the sign-in window again. From the desk it looks like a rejected password. It usually is not one.

Why does the loop hit frozen versions hardest?

Server-side identity work never stops, but a frozen install stops receiving client updates, so the mismatch widens over the years. Two local factors make it worse. The embedded sign-in window in these versions rides on the system's legacy web engine, so its session cookies and TLS settings decide whether the handshake completes.

The account servers also require TLS 1.2. A machine still configured for older protocols alone will fail the handshake no matter how correct the password is. Licence validation shares the same cache, so one stale token can gum up both at once.

Back the file up before you change anything

None of the steps below touch company data, but work this close to the install still deserves a safety net. Make a full backup to separate media and confirm it restores. Press F2 inside QuickBooks and note the exact version and release, so you can reconstruct the environment later.

Clearing the cached credentials, step by step

1. Close QuickBooks completely, then check Task Manager for any leftover process and end it.
2. Open Windows Credential Manager, choose Windows Credentials, and remove every entry whose name mentions Intuit.
3. Clear the session the sign-in window depends on. Run inetcpl.cpl, and on the General tab delete temporary internet files and cookies. Leave passwords alone unless you accept losing saved ones elsewhere.
4. Stay in that window, open the Advanced tab, and tick Use TLS 1.2. Apply, then reboot.
5. Rename the entitlement cache so the licence revalidates cleanly. In C:\ProgramData\Intuit\Entitlement Client, rename the version-numbered folder, for example v8, to v8.old. Show hidden files first and use an administrator account.
6. Open the hosts file at C:\Windows\System32\drivers\etc in Notepad and delete any line naming an Intuit domain. Even one such line, often added to silence update prompts, breaks the sign-in window.
7. Check the system clock. A wrong date makes the certificates in the handshake fail, and the window reports it as a sign-in error.

Now start QuickBooks without opening a file, then open the company from the File menu and sign in once when asked. In most of these builds the prompt can also be cancelled and the file still opens, because the account gates connected services rather than the ledger itself.

If the prompt still returns

Sign the account out rather than fighting the window. From the Company menu open My Company, find the account panel, and choose Sign out. Then switch off any connected services the file no longer uses, since each one can re-arm the prompt at open.

Security software that inspects encrypted traffic can also break this window, so test once with that inspection disabled. One trap worth naming: the Intuit Account password and the file's own Admin password are separate locks. If the dialog asks for file credentials, the loop above is not your problem, and QuickBooks admin password recovery is the right page instead.

Keeping the loop away on a version you intend to keep

Document the licence number and product number somewhere offline, and keep the installer itself beside them. After any Windows work, recheck TLS 1.2 and the hosts file, since updates and cleanup tools have been known to undo both.

If your copy runs on a subscription that demands sign-in at every open, consider moving the company file onto a perpetual Desktop licence you already own. Company-file format upgrades are one-way, so plan that move before you act. A licence you own outright keeps the account system out of the path between you and your books.