Users of QuickBooks Desktop have once again started reporting that it is crashing after the most recent Windows X (Windows Ten) Updates were installed on their Computer. It seems that the earliest reported incidence of this may have been around August 26th, but it has grown in increasing regularity and severity since September 1st.
QuickBooks Unrecoverable Error being reported by some users resulting from most recent Windows Update.
QB-Crash_Sept-2020
The Unrecoverable Error was being reported by users when attempting various QuickBooks activities ranging from attempting to open QuickBooks, to open a QuickBooks Company file, to open a particular Report, or Print a Report, or Email from QuickBooks. Obviously this isn't the same 'exact' error we experienced last spring, although it could be similar or result from the same underlying cause. By the way, one side effect of this problem is that 3rd-party applications that connect to QuickBooks Desktop via the SDK 'Integrated Application' feature are also failing.
I personally have not experienced this problem, nor have I had any of my own 'few' remaining QuickBooks windows clients (remember I retired a couple of years back and I have very few QuickBooks clients I now support) report having this problem (yet, "knock on wood") in part because we attempt to either control their Windows updates, or work with their IT-management to do so.
We are aware, from multiple readers who have written in, that individuals with this problem are reporting that they are spending several hours working through diagnostics and standard protocols to identify the problem with Intuit Technical Support, and that they in fact confirm that it does appear to be another 'Windows Update' related issue.
Individuals who appear to have 'overcome' the problem all report that their only solution was to perform a system restore to a restore point well prior to (about a week before) the Windows Update occurred because they couldn't identify exactly which one of the multiple individual updates was the actual culprit.
Of course this couldn't come at a worse time... right before the long holiday weekend. But, if you have started experiencing this newest problem following a Windows X update within the last few days then please consider posting your experiences in the comments to this article.