QBPro 2019 crash with features.dll error

Hi there, @bverry. 

I've got steps on how you can get rid of the error, @bverry. 

To start, you'll need to download and install the Tool Hub to help fix the error issues. Here's how:

1. Close QuickBooks. 
2. Download the QuickBooks Tool Hub file, then install it. 
3. Open the file you downloaded (QuickBooksToolHub.exe). 
4. Follow the on-screen steps to install and agree to the terms and conditions.
5. When the install finishes, double-click the icon on your Windows desktop to open the tool hub. 

Open the QuickBooks Tool hub you've install. This is a launchpad for the tools you’ll use to fix your issue. Select the Program Problems tab if you notice performance issues or any program problem persist. 

Note it may take 2-3 minutes to automatically download the background completely. 

If you have other questions with the process, don’t hesitate to comment below. Have a great day!

Hi, I had tried that with no luck. I'll try again. Assuming it fails again what is your next recommendation?

Thanks,

BV

As I expected the Tool Hub made no difference. I ran both the Quick Fix my Program and the Diagnostic Tool. There was lots of output in the command prompt window but there doesn't seem to be an easy way for me to capture that output. Is there a log file someplace that I can gather in order to show you these messages?

And speaking of messages. My original post that mentions the .NET Runtime Version (v4.0.30319) seems odd.  I have the latest version installed (v4.8.03761). Perhaps this is a red herring but it strikes me as wrong.

I'll make sure you get the company file up and running again in QuickBooks Desktop. bverry.

Thanks for providing us the details and performing the recommended steps to troubleshoot the issue. When do you encounter the error message?.

Before doing some troubleshooting steps, let's make sure QuickBooks Desktop to the latest release and you meet the system requirements.

To better isolate this issue, let's try opening a sample company file to check if you're having a problem with only one file and not the program itself. You can also open it from a different location to check if the problem might be coming from a damaged folder.

To open a sample file:

1. From the No Company Open window, select Open a sample file.
2. Choose any sample file on the list.

To copy the company file to a different location:

1. Right-click anywhere on your Desktop and click New and choose Folder. Then, name the folder QBTEST.
2. Open the folder where the company file is saved.
3. Right-click the file, then hit Copy.
4. Paste the company file in the QBTEST folder that you created.
5. Open the company file from the QBTEST folder.

If the same thing happens, it's possible there's a damaged data in your software. You can check out this article to troubleshoot the issue: Fix data damage on your QuickBooks Desktop company file. You can also repair QuickBooks Desktop to fix any damaged components in the software. Then, try opening QuickBooks Desktop again.

Please touch-based with me if there's anything else I can do to be of assistance. I look forward to hearing from you again.

Hi RCV Team, I have an interesting update. On my Windows 8.1 machine I restored to the oldest restore point I could find. While that has caused some issues with other applications it does seem to have fixed QB! I will continue to restore my company file from a backup tomorrow.

What I think caused my corruption is a VPN application from Shrewsoft. I had to install that app in order to communicate with one of our clients. The restore point I restored the system to is prior to that app installation. However, I do need to bring my company file back to where I need it, on a W7 laptop. That laptop also had the Shrewsoft app installed but, alas, restore points available don't take me back prior to the app installation. If I'm going to enjoy the same success I had on my W8.1 machine I'm going to have to try to wipe out any sign of Shrewsoft. I suspect I'll be using regedit to scour my registry (I've already uninstalled the app with no improvement). 

Stay tuned...

Thank you,

BV

Seems my problems stemmed from the altering of a Security Option (see attached) when I installed Shrewsoft VPN. With FIPS enabled QB would crash. With it disabled all is well again!!!

BV

Hi there, @bverry. Thanks for providing an update.

I'm glad to hear you're back in business again! We strive to help you out here in the Community and want you to know we'll always have your back.

Thank you for bringing us your questions. I look forward to seeing you again in the Community!

I was pulling my hair out over this for the past two days.  FIPS was the culprit. As soon as I disabled it in Local Group Policy (and Reboot) everything began working again. 

Thank you! 

That note was posted 3 years ago.  Has QB or anybody else found a work around?  qbw.exe is still throwing an exception code (C5) in QB 23 for the FIPS security requirement.