
Fix QBwin.log encryption errors
by Intuit• Updated 4 days ago
Learn how to fix the following errors in the QBWin.log after the Verify Data utility fails in QuickBooks Desktop.
- LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber Failed: The decryption has failed. CHECKPOINT: Failed to decrypt customer's credit card number. Customer ID: nnnn
- LVL_ERROR--Unable to decrypt social security number/Social Security number
These errors come from damaged encryption of sensitive fields such as credit card, Social Security, and bank account numbers. Here’s how you can fix them.
Note: Before troubleshooting, update QuickBooks Desktop to the latest version and create a backup or a portable company file.
Check the QuickBooks admin user for damage
- Sign in to your company file as an admin.
- Change the admin password, and QuickBooks will re-encrypt your file.
Important:Â If QuickBooks crashes while encrypting, contact us. We may need to send your file to Data Services to remove sensitive information. - Go to File, then select Close Company.
- Close QuickBooks.
- Open QuickBooks, then sign in as an admin.
Reenter encrypted data
When we fix your company file, some encrypted data might be removed. Don't worry, you can usually restore it from an older backup (.qbb or .qbw) and paste it into the fixed file.
Note: These steps won't recover employee bank accounts or routing numbers for accounts.
More like this
- Top data damage errors in QuickBooks Desktopby QuickBooks
- QBWin.log: LVL_ERROR--Error: Verify item history target quantity on order mismatch errorby QuickBooks
- QBWin.log: Verify Account Balance failedby QuickBooks
- Verify Error: QuickBooks found a problem with the Acct # / Card # / Note field for other assetby QuickBooks
- Find QBWin.log or QuickBooks.log filesby QuickBooks