Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Hello Community,
We upgraded from windows 7 pro to windows 10 pro last Friday. Everything went well. Ran QB Desktop Premier Contractors Edition 2018 all weekend. No issues. Sent the system back to the office this morning, after booting, QB will not open. The splash screen comes up and then it just goes away. This is the main computer that houses the QB database that is used in a multi user environment on a peer to peer network. I can open QB from another computer just fine so it isn't the database. Looking at the event viewer, right after boot up MSInstaller ran several times. There is then a .net runtime error
Application: qbw32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 78C1352F
Stack:
followed by an application error:
Faulting application name: qbw32.exe, version: 28.0.4015.2806, time stamp: 0x5ea0bc4a
Faulting module name: Features.dll, version: 28.0.4015.2806, time stamp: 0x5ef110b7
Exception code: 0xc0000005
Fault offset: 0x0036352f
Faulting process id: 0x3fd0
Faulting application start time: 0x01d659102facf7dc
Faulting application path: C:\Program Files (x86)\Intuit\QuickBooks 2018\qbw32.exe
Faulting module path: C:\Program Files (x86)\Intuit\QuickBooks 2018\Features.dll
Report Id: 9d0e31fb-8d68-4c6a-939c-c259a79b4a1e
Faulting package full name:
Faulting package-relative application ID:
I have uninstalled everything I could find that installed this morning but no joy. Windows 10 Pro version 2004 build 19041.264. Does anyone know how to fix this? This is becoming a crisis as we need to be able to access QB on this computer.
Thanks for your help
Found the answer here:
disabling the security policy as described in the above post fixed the problem, Thank you to the poster.
I am having the exact same problem. Same error output and same operating system. Unfortunately, my FIPS is already disabled so that fix won't work. I even tried enabling/rebooting/disabling/rebooting. Another colleague had the same problem and ultimately reset his computer which fixed the problem. I didn't have luck with that either. I also tried the Tool Hub without success. Would really appreciate any other ideas.
Thank you.
Thanks for joining the discussion and sharing the things you've done to resolve the problem, @tb38,
If the QuickBooks Tool Hub doesn't fix the error when opening QuickBooks, run the Repair Tool. This utility resolve common errors in the software. Perform the steps below:
Note: If you don't see Programs and Features, select Programs instead. Then select Program and Features.
To learn more about repairing the program and the complete instructions, go to this link: Repair your QuickBooks Desktop for Windows.
If you get the same problem after this troubleshooting, I recommend reaching out to our Technical Team immediately. Our representatives can run some database fixes and diagnosis to identify underlying issues with this unexpected behavior.
Here's how to get support:
Kindly update me on how things go by adding another comment below. I want to make sure you're all set, and I'm here if you need further guidance. Have a great day! All the best.
I ran across this nonsense today. Same error with features.dll. Program would start up and then close.
The tool hub is completely useless. So don't even bother with that.
Uninstalling the program and deleting the folders from all the locations where intuit stores files did not work either.
What worked in my case was this. I downloaded the latest version of .Net from here. I installed .Net 4.8.1 and restarted.
This time when I restarted the program. It actually started up and let me in.
So for those of you with this issue. Try updating .Net on your system.
It's 2024 and its still an issue. FIPS MODE is becoming a government requirement. Hopefully, Intuit will begin using FIPS140 compliant cryptographic algorithms in its Features.dll by 2025?
I recognize the relevance of enabling QuickBooks to stay FIPS-compliant so you can keep going in managing your business operations, MikeZee.
Currently, QuickBooks Desktop is unable to support FIPS140-compliant cryptographic algorithms required by DISA STIG and the government.
For now, you can send this valuable feedback directly to our product developers to allow QuickBooks on FIPS mode and avoid errors. Doing so will help us improve your overall QuickBooks experience.
Here's how to send feedback:
Additionally, we're actively involved in the TRUSTe certification program. Our dedicated team of security experts consistently monitors Intuit products and services and collaborates closely with top government and industry-leading cybersecurity firms.
I'm also including this resource to help you fix any data damage in the future: Fix data damage on your QuickBooks Desktop company file.
We'll always be around whenever you need additional assistance. Please don't hesitate to leave a reply in the comments below. Stay safe and have a good one!
QB doesn't suit you. Consider switching to an ERP class product (e.g. Netsuite, Accumatica). You can purchase a third-party conversion service.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here