I just upgraded to QB Pro 2017 and the "Crash: Com Error" started. This is now 2017 and this problem persists. I'm still using Windows 7 but don't understand why Windows would be causing the problem since the crash only started after the automatic upgrade. This can only be a QB problem for QB to fix. Anyone with a solution?
Using QuickBooks get Crash: Com Error
While Using a part of Quickbooks, I receive a "Crash: Com Error" Message. After I click OK on the window, all of Quickbooks shuts down. After about 4 hours on Intuit Tech Support they told me that this is a windows issues. Does anyone have any suggestions? I heard something abour fixing the registery for Vista, but could not find it on this site. Thanks.
Windows for home | Previous Windows versions | Apps
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
37 answers
Sort by: Most helpful
-
Anonymous
2017-10-28T14:31:13+00:00 -
Anonymous
2017-11-16T05:10:56+00:00 I have reverted to Build 16.0.8625.2121 of office 365 as suggested by someone over at quickbooks community. See above link.
Voila ... it successfully resolved the com errors. It's not a proper solution as you have to disable updates for office but it does tell me that there is a compatibility issue between office and quickbooks. I am running quickbooks pro 2017.
Intuit needs to get their act in gear and make quickbooks compatible with the latest update to office.
-
Anonymous
2017-11-16T11:22:20+00:00 Thanks WarningU2. I will have my IT manager follow your guidance.
Louis Holder
-
Anonymous
2017-12-15T14:43:35+00:00 This worked for me.
-
Anonymous
2017-11-15T01:55:26+00:00 I found this over at Quickbooks community
See BajaEcotours and Steve's comments ... I am going to try this tomorrow for a friend whose business is in trouble because she cannot send invoices to anyone ... I will update this ticket tomorrow with the result.
- BajaEcotours
- a month ago
Same problem here. Desktop Pro 2017. It has started crashing and giving the Com Error even when I am just saving and closing a new estimate, invoice or purchase order. I have spoken with level 2 customer support in the Phillipines 4 out of the past 5 days. They fix it, and then it just happens again!! Unf......believable! HOW ABOUT A FIX, PLEASE!
- steve
- a month ago
Account. Click the "Update Options" button, and choose "Disable Updates." Make sure to turn these back on when we get confirmation from Intuit that this is fixed, otherwise you put your computer at risk! 5) Give your computer a restart for full effect. Hopefully whatever changed between Office and Quickbooks will get fixed without forcing everyone onto QB 2018. Chime in if you guys have any questions, I like to help." data-inline-edit-type="textarea" data-inline-edit-url="/comments/3388550" id="inline_edit_comment_3388550_body" style="box-sizing:inherit;font-size:0.875rem;">If you guys are using Office 2016 365, I *think* that this was caused by a recent update. Here's how I was able to fix it for one of my clients, so far so good after two days:
- Open up a command prompt as administrator
- Enter the below command, BUT **replace the 3 spots that say DOT at the end, with periods. This website is idiotic and won't let me post because it thinks I'm posting a phone number, this is the only way I can get around that**
"C:\Program Files\Common Files\Microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16DOT0DOT8326DOT2107
- This will downgrade your office to the last version. I found that the .2107 version plays nicely with Quickbooks.
- After this finishes (takes 15-20 minutes), open up an office program like Word, then go to File > Account. Click the "Update Options" button, and choose "Disable Updates." Make sure to turn these back on when we get confirmation from Intuit that this is fixed, otherwise you put your computer at risk!
- Give your computer a restart for full effect.
Hopefully whatever changed between Office and Quickbooks will get fixed without forcing everyone onto QB 2018. Chime in if you guys have any questions, I like to help.
- bcarrington
- a month ago
The command should look like this image: https://i.imgur.com/bpPVOZY.png