Get 50% OFF QuickBooks for 3 months*

Buy now
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Simplify payday and set payroll to run automatically on QuickBooks. Explore QuickBooks Payroll

Reply to message

View discussion in a popup

Replying to:
azpcp
Level 3

Reply to message

@Maybelle_S  Don't run to "THE TEAM" with this as a solution, a new computer does NOT resolve the problem for everyone.

 

Same issues on my old computer so I purchase a new computer. The new computer has an 11th Gen i7 processor, and 32GB of memory, yes, 32 that is not a typo, all other specs are well above QB requirements. QB crashes excel and chrome every time when opening or closing a company file. The only things installed on the new computer are QB Dekstop Pro Plus, Office 365, Adobe Reader and Chrome. From the very first initial opening of a company file QB aborted and crashed Chrome and Excel. 

When opening a company file I have to have Chrome and Excel both closed before then I can open and use QB and before I close a company file I have to make sure that I save everything and close Excel and Chrome first, then close the company file or I will lose work and everything will crash.

 

I also use Adobe Reader open when working in Quickbooks and be able to edit PDF's. If I have a company file open BEFORE I open a PDF in Adobe I can not edit the PDF. I have to have Adobe and the PDF open first, then open Quickbooks to be able to edit PDFs.

 

The common factor here is Quickbooks. This IS absolutely a QB problem and QB is the cause. It is ridiculous that there are this many people complaining and Inuit is not accepting responsibility for distributing a defective product and is not doing anything to resolve it. This is unacceptable and speaks volumes about how much Intuit does not care about its customers.

 

Running the Tool Hub DOES NOT WORK either!

You would think with the huge increase in price this year we'd get better support.

 

Also, I want to remark on another "Solved" thread that said that running in the admin account fixed the problem. I always run in an admin account and still have the problem. 

Ridiculous that these threads are being marked as solved.

Need to get in touch?

Contact us