QuickBooks Shows the Last User's Name on a Shared / Terminal Server? Lock Down qbw.ini

QuickBooks Desktop is installed on a server and several people RDP in to use it. Each time someone opens QuickBooks, the login screen pre-fills the last person’s QuickBooks username instead of a blank prompt — so users keep seeing each other’s names. It’s not a bug in the company file; it’s a shared settings file.

Why it happens

QuickBooks stores its startup settings in qbw.ini, which lives in a machine-wide folder (under C:\ProgramData\…), not in each Windows user’s profile. Its [LOGIN] section holds LASTUSERNAME=, recording whoever logged into QuickBooks last. Because the file is shared by every Windows user on that server, the last login’s name carries over to the next person.

There’s one qbw.ini per installed QuickBooks version, each in its own folder — so on a box with several versions you’ll have several files, e.g.:

C:\ProgramData\Intuit\QuickBooks 2024\qbw.ini
C:\ProgramData\Intuit\QuickBooks Enterprise Solutions 20.0\qbw.ini
C:\ProgramData\Intuit\QuickBooks 2017\qbw.ini
C:\ProgramData\Intuit\QuickBooks 2015\qbw.ini
C:\ProgramData\Intuit\QuickBooks 2013\qbw.ini

Fix each version your users actually open.

The fix: blank LASTUSERNAME, then make qbw.ini read-only

The goal: QuickBooks should always show the full login prompt (username + password), so no one’s name is pre-filled for anyone else.

1. Close QuickBooks in every session on the server.
2. In File Explorer, turn on View → Hidden items (ProgramData is hidden), and open the version’s folder, e.g. C:\ProgramData\Intuit\QuickBooks 2024\.
3. Open qbw.ini in Notepad. Find the [LOGIN] section (add it if it’s missing) and set the value blank:

   [LOGIN]
   LASTUSERNAME=

   Save.
4. Make it read-only so QuickBooks can’t re-write the name. Two ways:
   • Quick: right-click qbw.ini → Properties → tick Read-only → OK.
   • Robust on a server: in Properties → Security, Deny → Write for the Users group (a plain read-only attribute can be cleared by a process; an NTFS deny is firmer for multi-user boxes).
5. Repeat for each version’s qbw.ini. Now every user gets a clean login prompt — no leaked names.

Important caveat: QuickBooks sometimes needs to write to qbw.ini

Locking the file means QuickBooks can’t update anything in it — and that includes values it may legitimately need to change, especially during updates/patches or when you change a startup setting. Day-to-day this is harmless, but if a QuickBooks update misbehaves, or a setting won’t stick:

• Temporarily clear read-only (uncheck the attribute / re-allow Write), let QuickBooks run its update or save the change, then re-apply read-only.

So treat read-only as a “normally on, off briefly for maintenance” switch.

For other per-user settings

The name leak is the headline issue, but if you also want each person’s preferences kept separate, give every user their own Windows account on the server. Most QuickBooks per-user state already lives per-profile in %APPDATA%\Intuit\QuickBooks <version> — qbw.ini is the machine-wide exception, which is exactly why it needs the read-only treatment above. (Multi-user hosting itself: see Error H202 and QuickBooksDBXX won’t start.)

FAQ

Do I really need to edit every version’s file? Yes — each installed version has its own qbw.ini in its own folder. Lock the ones your users actually launch.

A QuickBooks update failed right after I set this. Clear the read-only flag, run the update, then re-apply it. The locked file is the first thing to check when an update or setting change won’t take.

Can each user keep their own last username instead of a blank prompt? Not from this single shared file — it’s one machine-wide qbw.ini for all Windows users. Blanking it and forcing the full prompt is the clean, low-risk fix; it just means everyone types their QuickBooks username each time (which is also better for privacy on a shared server).

Sources: Intuit Community — Editing QBW.ini, QBW.INI — QuickBooks initialization file reference (E-Tech)