Skip to content

Get Rid of QuickBooks Runtime Error Once and for All

QuickBooks Runtime Error

Last Updated on March 16, 2022

QuickBooks software, developed by Intuit® helps small and mid-sized businesses with their book-keeping and finance-related tasks. To make the QuickBooks software more user-friendly, tools are launched every now and then but, with every advancement, there are minor errors that pop up. One such halt faced by users is Runtime Error QuickBooks. In the blog, we cover the details of the QuickBooks Runtime Error and the resolutions for Runtime Error in QuickBooks Desktop. Follow the complete article for detailed troubleshooting instructions.

Looking for a Solution to QuickBooks Runtime Error? Call Support Number 1.855.738.2784 for Expert’s Guidance

What is QuickBooks Desktop Runtime Error and why it Occurs?

QuickBooks Desktop Runtime Error can appear suddenly while performing important tasks on the QuickBooks application. “Qbw32.exe – Memory could not be read” or “Runtime Error’ – Runtime has terminated in an unusual way – contact support” are the usual messages that appear indicating about QuickBooks Giving Runtime Error. The error can appear because of the following reasons:

  • The company file is corrupted or damaged.
  • The windows compatibility mode is turned on while operating the QuickBooks.
  • The QBW.INI file id damaged or corrupt.

IMPORTANT: Utilize QuickBooks Verify/Rebuild Data Utility if you suspect the errors is appearing because of data corruption.

Troubleshooting Steps to Fix QuickBooks Runtime Library Error

As we progress in this blog to list the methods which will help you solve QuickBooks Runtime Library Error, try rebooting the computer and check if the QuickBooks is opening up. If not, try one of the methods listed below. Make sure to follow the troubleshooting steps in the sequence listed below.

Method 1: Run the QuickBooks Application without Company File
  • To run the QB application you need to resolve the QuickBooks C++ related Errors.
  • For this first ensure that the QBW.exe is not running in the background of the computer processes.
  • Press ‘Ctrl + Alt + Delete’ and navigate to the Processes tab.
  • If you see a process running with the name of QBW.exe, right-click the process and select End Task.
  • Click Yes for the confirmation.
  • Right-click the ‘QuickBooks’ icon while pressing and holding down the CTRL key.
  • Click ‘OPEN’ and the software will open up without any company file opened in it.
  • Check if this resolves the error and if you are still getting the same error, then follow the next troubleshooting step.
Method 2: Open Company File without any other Running Windows
  • Close the QBW.EXE file by following the steps mentioned above.
  • After you have closed the QBW file, double-click the QuickBooks icon, (as before) and press and hold the ‘ALT’ key from the ‘NO COMPANY’ window.
  • While holding the ALT key launch the ‘Company file’, without any other windows being opened.
  • If you are still getting the runtime error in QuickBooks then try renaming the QBW.INI file.
Method 3: Rename the QBW.INI file

Make sure your Windows is set to Display Hidden Windows Files. The QBW.INI file is usually located in

Windows 7, Windows Vista: C:\ Program Data\ Intuit\ QuickBooks [Version] Folder where [Version] represents the version of QuickBooks Desktop software.

Windows XP: C:\ Documents and Settings\ All Users\ Application Data\ Intuit\ QuickBooks [Version] where [Version] is the version of your QuickBooks Desktop.

  • Apart from manually finding the file you can also locate the QBW.INI file with the help of windows search tool.
  • Right click the file and select Rename.
  • Rename it by adding .OLD as the extension.
  • Launch QuickBooks to check the status of the error.

However, if even after following the troubleshooting steps mentioned in this article does not resolve the QuickBooks Runtime Error, then you can always reach us at our Helpline Number 1.855.738.2784 for immediate help and support.

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!