cancel
Showing results for 
Search instead for 
Did you mean: 
bhi
Level 3

Received an error window "AVMTimer: QBW32.EXE - Fatal Application Exit"

This error earlier error appeared (see screenshot) on our host PC (win10) for QuickBooks Desktop Enterprise 19.

 

What does this error mean and how can we fix or prevent it? 

2 Comments 2
JonpriL
Moderator

Received an error window "AVMTimer: QBW32.EXE - Fatal Application Exit"

Hello @bhi,

 

I have here a list of the possible instances which can be the reason why you're prompted with such an error message.

  • The Company name is too long
  • Damaged or missing QBWUSER.INI file
  • Corruption on your hard drive
  • Damaged program files or QuickBooks Desktop installation
  • Damaged Windows operating system

When errors happen, it’s best to update your QuickBooks to the latest release version. Updates will make minor changes in the data file for compatibility. You can read through this article to learn more: Update QuickBooks Desktop to the latest release.

 

Once done, let’s start our troubleshooting by downloading and running the QuickBooks Install Diagnostic Tool. Here’s how:

  1. Download the QuickBooks Install DiagnosticTool.
  2. When prompted, save the file to the local Desktop.
  3. Close any open programs and run the QBInstall Tool.
  4. Restart the computer after running the tool to ensure the components are properly updated.

Lastly, you can also check out this article for more detailed steps along with several solutions you can try. Screenshots are provided in the article together with the steps: QuickBooks Desktop won't open, has stopped working, or not responding.

 

Keep me posted in the comments if you have any other questions. I'll be here to lend a hand.

bhi
Level 3

Received an error window "AVMTimer: QBW32.EXE - Fatal Application Exit"

Thanks for your reply @JonpriL 

We have not received that error since I first posted about it here. I will try your suggestion next time the error appears.

 

Please note that all workstations running QB have already been updated prior to the initial appearance of this error.

Need to get in touch?

Contact us