Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Hello everyone,
Thank you for reaching out to us here in the Community about the issue. Let me share some updates about the ongoing investigation in QuickBooks Desktop.
The investigation is still open, and a specific time frame for the complete fix is unavailable. Our team is working on it and conducting further examination because of the unusual result when using the Desktop version.
Also, we're collecting some logs and information about the problem. We encourage affected users to send data to resolve the crashing right away.
For now, I recommend reaching out to our Technical Support Team. Once we have an update, we'll be sending out notification emails.
Our customer support for Pro, Premier, and Plus is available from 6 AM - 6 PM PT (Monday - Friday). For Enterprise, any time, any day. See the steps to get a hold of a specialist:
You can also check this link for more details about how to use the QuickBooks Tool Hub to repair QuickBooks: Fix common problems and errors with the QuickBooks Desktop Tool Hub.
Drop me a comment below if you have more concerns about the issue or if you need assistance accessing QuickBooks. I'll be around to help you some more.
So still no idea what the programmers broke, how they broke it, or how to fix it. Got it.
How about just making an "update" that takes out the garbage that is R5??????
Hello,
I was able to report a bug (everytime the program crashed) from the "Help" button in QuickBooks. Help>Send Feedback Online>Bug Report. The past few months that option has no been available because when i clicked on Bug Report a Script error occurred. If i clicked continue running the script, it would not do anything at all.
Trying to print payroll checks, program shuts down once again. Tried to do the Bug Report and this is the script error
@Bill MiLo RE: So still no idea what the programmers broke, how they broke it, or how to fix it. Got it.
Well, it's only been six weeks. Let's not rush them. Based on recent past performance, I expect an update in about 3 months. Maybe.
My workaround had worked for a few weeks until now. I had clients say it's having the same crashing experience they had a couple of weeks ago. I went ahead and contacted support and told them I needed an R5 workaround. I have been told they do not have a workaround and their engineering team is still working to find a solution to this issue, but rest assured we will be notified once this is fixed. So I checked my workaround. The settings I had in edge pop up Allow list [*.]intuit.com has disappeared. This time I went into the client domain server and added [*.]intuit.com to "Allow Pop-up Windows on specific Sites" in the group policy and pushed it out to all PCs. Also, don't forget to set the default to Edge.
6 weeks? this has been down since May. Half of my customers already moved to Drake Accounting, and some even to *ugh* Peachtree.
@r_sotojr RE: 6 weeks? this has been down since May.
Time flies! Oh, but don't worry because they've been "working diligently" on it. A rep here wrote that and so it must be true.
At least that's what the manual at their call center tells them to say... Not like the actual engineers ever care to listen to the customers or read these posts.
At least I am getting their AD for upgrading for online version before it crashes. Lucky me
OK, I am sure that once I submit my wow results, my quickbooks will begin crashing, again and again ... but, since it has NOT been crashing, I have been wanting to post what I did ...
Someone, at sometime, somewhere in this feed, possibly near the beginning of it all, posted a suggestion of NOT USING HOMEPAGE - home page was programmed to open at startup.
I changed my preferences for startup to NOT load HOMEPAGE - and - have NOT crashed, since!!
I have created icons that I once used from the homepage, into the icon bar of quickbooks, allowing me to not need the homepage.
I recently closed the current 'company' I use 90% of the time, and opened the second 'company' I have in my program. As the homepage was loading - CRASH! I rebooted quickbooks, re-opened that company and immediately removed the homepage and updated my preferences to not load homepage at startup.
If you have not tried this, yet, please try.
I dread any upcoming 'updates' to quickbooks, for fear the goal will be to fix something my quickbooks is not doing but they feel will 'fix' it :(
GOOD LUCK!
Correct. That "workaround:" has been posted already on 6/26 and 6/27 by myself after reading @BigRedConsulting post about it. Hold the [Alt] key before loading the company file. After that, so you don't have to hold the key down every time... disable the home page from loading.
>Another way to keep the Home window from appearing is to change a preference. Each user should do this as the setting is per user. To change it go to Edit | Preferences | Desktop View | My Preferences. Then un-check the "Show home page when opening a company file" option.<
After the company file loads, you can then open the home page. I have been doing this with no issues. Maybe people will see your message with mine again so we don't continue to have the same repeated answers from the QB team who suggest 10 different things and repeat 101 times on how to "contact support" for more help in this issue, of which they can't help with. Sure.... one can only dream... :-/
@BigRedConsulting wrote:Well, it's only been six weeks. Let's not rush them. Based on recent past performance, I expect an update in about 3 months. Maybe.
QuickBooks Desktop and Enterprise Desktop 23.0 products are expected to be available to accountants on September 6, 2022, and September 20, 2022, for general release to others.
Inuit said they would keep the "internal browser" up-to-date; they have not! They use CefSharp as the internal browser and the version they are using is a year old. Needless to say, it does NOT have any of the security or operational fixes issued by Google (Chromium based) or the CefSharp team in the past year. The crash this morning was in the Windows Kernel being called by C:\Program Files\Intuit\QuickBooks 2022\CefShar.BrowserSubprocess.exe Intuit, get it FIXED! It is an easy critical fix to issue (just update the CefSharp files) and most of these issues go away!
I have done that to both of my companies, disabled the Home page startup. I don't have issues with the program crashing when opening any more, but i still have sporadic shut downs. When I am going to print something mostly. Checks, Deposit Slips, reports, check register, etc... It does not happen all the time and when it does, after you click on the print button it just hangs for a few seconds and boom, shuts down. I restart and do the same thing, and it usually is Ok and it prints. It's very annoying especially if someone is sitting here waiting for a check or a report. I have already tried most of the "fixes" and to no avail. It still happens but not as often as before. Good Luck, i hope that solved your problem!
And i spoke too soon, Just tried to print the check register and it hung for about 10 seconds and the program shut itself down. Had to restart once again.
I had the exact same issue on a one of user workstation. I tried a bunch of different fixes but still not working.
It's definitely NOT an updated version of CefSharp. The support page that states "Updates will be provided if and when they become available" is a joke and should be removed. "If and when"? How many revisions have been released since Chromium/84.0.4147.105?
Thank you for providing some information @AlcaeusF
Contacting support does little since we've all tried all their fixes:
-Run tool hub
-disable UAC
-check permissions
-reinstall
-file doctor
-update
-clear cache and cookies
Yep, there have been 20 major Chromium releases since 84 (now on 104). Adobe also uses the CEF modules and had a terrible time with CPU usage, crashes, etc. last year but they did (and do) update CEF and those issues have gone away. Intuit, take a lesson from Adobe if for no other reason than look at the CVEs (security flaws) that have been fixed over those 20 major Chromium releases that you are knowingly exposing your customers to by not upgrading CEF.
@PeteSL RE: Yep, there have been 20 major Chromium releases since 84 (now on 104).
Built 84 appears to be the most recent version that Intuit has managed to get into the latest build of any QB version-year. I checked several recent version-years, including 2019, 2020, and 2021 and some of the Chromium versions are as old as builds in the 50's. I think 54 was the oldest I saw.
So, it doesn't appear that Intuit ever updates this 3rd party browser - or at least doesn't do so regularly. There is no mention of updating it in any of the release notes I've ever read.
@BigRedConsulting wrote:So, it doesn't appear that Intuit ever updates this 3rd party browser - or at least doesn't do so regularly. There is no mention of updating it in any of the release notes I've ever read.
Unfortunately, when they moved away from IE 11 which was maintained by Microsoft, they specifically stated they would keep their internal browser up-to-date as previously stated and quoted by others in this thread. What I was pointing out that they are not doing what they publicly stated and are therefore putting their customers at risk, both from a performance (software crashing) and security (unpatched CVEs) perspective. Definitely a black mark on Intuit.
Well i was feeling lucky today, been working in the QB program since 9am this morning, no crashes or shutdowns. Well......spoke too soon, just tried printing a deposit slip and here we go again, shut down, no error message. ARG!!!
And again, not 1 hour later, same thing, printing a deposit, click on print and it hangs a few seconds with the blue ring spinning, then shuts down.
This isn't the kind of impression that I'd like you to have and we know how much time it can take when something isn’t working the way you need it. This is why we make great efforts to deliver customer satisfaction at all times and to fix an issue as soon as possible, netofpa.
We can use the Print & PDF Repair Tool from the QuickBooks Tool Hub to fix most of the common printing issues. Then, make sure that you're using the latest release of your QBDT product since QuickBooks crashing is usually caused by a damaged component in the program. This way, you'll always get our bug fixes and security patches.
If the same thing happens, try installing the QuickBooks Tool Hub and run the Quick Fix my Program utility. This tool helps resolve major issues and errors that a user might face while working on the software. We recommend running it on Windows 10, 64-bit for the best experience. Here's how:
Once done, it's time to run the Quick Fix my Program utility:
To learn more about this process, you can check out this article: Repair your QuickBooks Desktop for Windows. We can also run the Rebuild Data tool to fix any company file data issues. Here's an article you can refer to for more details about fixing data damage on your QuickBooks Desktop company file. I'm also adding this article to learn how to obtain the different tools that will help you fix common issues and errors: Fix common problems and errors with the QuickBooks Desktop Tool Hub.
In case you need help with other QuickBooks Desktop-related tasks, feel free to browse this link to go to the page. It has our general QuickBooks topics, video tutorials, and Community answers: View all help for QuickBooks Desktop.
This is the best way we can do to resolve your issue as soon as possible. Should you need any other help with QuickBooks, please don't hesitate to comment below and I'll get back to you.
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