Repairing QuickBooksDesktop.xml When the Recent Files List Disappears
When the Open Previous Company list goes blank after discontinuation, a damaged QuickBooksDesktop.xml file is usually the cause; here is how to rebuild it.
On a long-term QuickBooks Desktop installation that no longer receives updates, the Open Previous Company list and the company-file search rely on a small XML file that QuickBooks reads at every launch. When that file becomes corrupted, truncated, or is deleted by cleanup tools, the recent-files list simply stops populating. The program itself still works — you can still open any company file manually — but the convenience of the recent list is gone, and on multi-user setups the file-search function may also fail to locate company files on the network. Our engineers see this regularly on installations that have been running for years without a clean reinstall, and the fix is straightforward once you know where to look.
What breaks and why
QuickBooks stores its recent-company list in a file named QuickBooksDesktop.xml (on some versions, QBWUSER.INI plays a parallel role for window preferences). The file lives in the user's %AppData%\Intuit\QuickBooks folder on Windows. Every time you open a company file, QuickBooks writes a new entry to this XML file. If QuickBooks crashes during a write, if a third-party cleanup utility deletes the file, if a Windows profile migration corrupts it, or if an antivirus quarantine locks it mid-write, the file ends up empty, truncated, or syntactically invalid. On the next launch QuickBooks cannot parse it, silently discards it, and presents a blank recent list.
On unsupported installations the risk is higher because there are no more product updates that might quietly patch file-handling edge cases. The XML file also accumulates stale paths — old network drive letters, renamed server shares, decommissioned workstations — and a single malformed entry can cause QuickBooks to ignore the entire list.
Preparation
Before making changes, close QuickBooks on every workstation that accesses the company files. Make a copy of the current QuickBooksDesktop.xml file (even if it appears empty) so you have a baseline. If the file is absent entirely, note that as well — the repair procedure is the same either way.
Identify the correct folder. On Windows 10 and 11 the path is typically:
C:\Users\<username>\AppData\Roaming\Intuit\QuickBooksIf the AppData folder is not visible, enable hidden items in File Explorer or type %AppData%\Intuit\QuickBooks directly into the address bar.
Procedure
-
Close QuickBooks completely on the workstation, including any background processes. Check Task Manager for
QBW32.exeandQBDBMgrN.exeand end them if they persist. -
Navigate to the AppData folder using the path above.
-
Rename the existing file from
QuickBooksDesktop.xmltoQuickBooksDesktop.xml.old. If no file exists, skip this step. -
Open QuickBooks and open your primary company file using File → Open or Restore Company → Open a company file, then browse to the
.QBWfile manually. -
Open each additional company file the same way, one at a time, allowing QuickBooks a few seconds between each to register the path. QuickBooks will recreate a fresh
QuickBooksDesktop.xmlfile automatically as it writes each entry. -
Close QuickBooks, then reopen it. The Open Previous Company submenu under the File menu should now list every file you opened, in reverse-chronological order.
-
Verify on a second launch that the list persists. If it does, the XML file has been written correctly and the repair is complete.
Stale network paths
If the recent list populates but certain entries produce errors when clicked, the XML file likely contains outdated UNC paths or mapped drive letters that no longer match the workstation's current configuration. Open each problematic entry from the No Company Open window, browse to the correct location, and QuickBooks will overwrite the stale path on the next write cycle.
Preventing recurrence
Set the QuickBooksDesktop.xml folder as an exclusion in overly aggressive antivirus rules — not the company file folder, just the user preferences folder. Avoid running registry or disk cleanup utilities that target %AppData% without reviewing what they plan to delete. If the file corrupts repeatedly across reboots, the underlying cause is usually a failing storage sector on the system drive or a Windows profile that is not flushing writes cleanly; in that scenario, running chkdsk and testing with a fresh Windows user profile will isolate the root cause. For company files that themselves show signs of structural damage during this process, our engineers recommend a full Verify and Rebuild cycle before relying on the restored recent-files list for daily use.