Recovering a QuickBooks Desktop Company File Using ADR and TLG Files

Last reviewed 2026-07-26 4 min read

When a QBW file fails standard repair, assembling Auto Data Recovery and transaction log components can restore recent data that backups alone would lose.

When a QuickBooks Desktop company file is corrupted beyond what Verify, Rebuild, or the standard File Doctor utility can resolve, the primary .QBW is no longer a reliable recovery source. At that point, our engineers look to two secondary components: the Auto Data Recovery (ADR) snapshot and the .TLG transaction log. Used together — and in the right order — these components can reconstruct a file that is newer and more complete than the most recent scheduled backup. This playbook covers how we evaluate which source has the freshest data, how we assemble a recoverable file set, and when manual transaction reconstruction becomes necessary.

Inventory All Available Sources

Before attempting any recovery, gather every potentially usable file. Search the workstation and server for:

The primary .QBW file (even if it will not open).
The most recent .QBB backup and its companion .TLG from the same backup session.
The ADR folder, typically located at C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files\Auto Data Recovery.
Any .DNR (Data Negligible Recovery) files, which are ADR-related artifacts.
Temporary or shadow copies on the server volume.

Record the modified timestamp and byte size of each file. These two data points drive every subsequent decision in the recovery.

Evaluate Source Freshness and Completeness

The goal is to identify the source pair that captures the most recent transactions. Compare timestamps across all gathered files:

If the ADR .QBW snapshot is newer than the last .QBB backup, the ADR file likely contains transactions recorded after that backup.
If the .TLG from the original file location has a timestamp close to the last known successful use of the file, rolling that log forward against either the ADR snapshot or the .QBB backup can bring the recovered file to near-current state.
If the ADR snapshot and the .TLG are from the same approximate window, they may already be a matched pair and can be opened together directly.

When the ADR snapshot is older than the last backup but the .TLG is current, the better strategy is to restore the .QBB backup and then apply the live .TLG to it. For background on how the transaction log interacts with the company file during normal operation, see our QuickBooks file repair overview.

Assemble and Test the Recovery Candidate

Once the freshest viable pair is identified, copy both files to a clean working directory on a local drive — never attempt recovery over a network path. Name the files so the .QBW (or restored .QBB) and the .TLG share the identical base filename, which QuickBooks requires to link them.

Open the .QBW while holding the Ctrl key to suppress any network or multi-user prompts. If the file opens, immediately run Verify Data from the File > Utilities menu. Verify checks for list damage, transaction integrity, and balance-sheet linkage errors. If Verify passes, proceed to reconciliation checks. If Verify fails, note the specific errors and attempt a Rebuild; if Rebuild also fails, the candidate pair has structural damage and the next source should be tried.

Validate Data Integrity Against Known Balances

A file that opens and passes Verify is not necessarily correct. Cross-check the recovered file against independent records:

Compare the trial balance as of the ADR snapshot date to bank statements or prior-period reports.
Reconcile the most recent bank and credit card accounts to confirm that cleared transactions survived.
Review Accounts Receivable and Accounts Payable aging summaries against customer and vendor statements.
Spot-check payroll liability accounts if payroll is processed inside the file.

Any gap between the recovered data and known balances identifies transactions that were entered after the ADR snapshot but not captured in the .TLG.

Rollback Points and Decision Gates

At each stage, preserve the working file before making changes:

After the initial successful open, create a .QBB backup labeled with the date and source pair used.
After Verify passes, create a second backup.
After reconciliation adjustments, create a third.

These checkpoints let you return to a known-good state if a later step introduces problems.

When to Escalate for Manual Reconstruction

If no combination of ADR, .TLG, and backup produces a file that passes Verify — or if the recovered file is missing large blocks of transactions — automated recovery has reached its limit. At that stage the file requires manual data reconstruction by a recovery engineer who can extract transaction fragments directly from the damaged .QBW at the database level, merge them with the best available source, and rebuild broken list-entry links and target chains by hand.

Clean Outcome

A successful recovery produces a single .QBW file that opens in single-user mode, passes Verify with no errors, reconciles to external statements within an acceptable tolerance, and contains all transactions entered up to the last known working session. Once that standard is met, the file can be returned to production with a fresh backup cycle established immediately.