Was this page helpful?
Thank you!

Comments or suggestions?

Enter Email Address (optional)

Resolve data damage, Part 1: Start here

Note:  For QuickBooks Desktop 2015 and 2016, please go straight to Use Rebuild and Verify Utilities

When data damage occurs, Intuit will help you, the user, as much as we can to get you back into operation, but the responsibility is yours.

Before you start troubleshooting data damage, be aware that you have some options:

How Do I Know If My File Is Damaged



Data Damage DO's and DON'T's


  • Maintenance Releases (updates) can help resolve and prevent future data damage issues.
  • For example, if you are running QuickBooks 2013 R1, update QuickBooks to the latest release to maintain stability and increase performance. 




Step 3: Using troubleshooting tools to resolve data damage

Basic Data Damage Troubleshooting uses these tools and will often resolve your data damage issue.







Diagnosing the symptoms of data damage is important for case documentation and for understanding what types of damage our customers are experiencing.

Please indicate where the customer was experiencing the damage, what the symptoms were for the damage (for example, crashing, unable to save a transaction, transactions not appearing on reports, etc.) or how they discovered the damage in the file.

Also, if you read the Qbwin.log file - please indicate what aspects of the file were damaged and what specific steps you took to resolve that damage.

Note: In some instances, creating a portable company file and restoring it resolves data damage issues. Please do not overwrite the existing company file if you use this troubleshooting step.

Note: Please, ask the customer if the file is backed up using Intuit Data Protect (IDP). If it is, moving the file local to be rebuilt and then putting the file back on the network can break the connection to the file and prevent further backups. File(s) may have to be re scanned or re selected to put back within the protection of IDP.

As Rebuild checks your file, it tests each transaction in your file and it will

  1. Do nothing to the transaction.
  2. Attempt to repair the transaction.
  3. Remove transactions or list entries that are damaged and cannot be repaired. Removing transactions is rare and occurs only in severely damaged files.

It also reads current data, e.g., number of transactions, and updates what is stored in your file.

If a transaction is damaged, Rebuild Data records messages in the Rebuild Log within the Qbwin.log file.

If a transaction is damaged and Rebuild Data cannot recognize list elements, it adds a "Rebuilt" element to a list. You will have to determine the name and type of the element and either rename it, or merge it into a new element.

KB ID# HOW20804
3/24/2017 4:52:31 PM
QYPPRDQBKSWS03 9138 Pro 2017 ae9870