Hi Promise3,
My issue started when I tried to update QuickBooks Enterprise 22 from R3 to R5. QB would not prompt me that an update was available, therefore I downloaded the latest update for QBE 22 from Intuit's website:
https://downloads.quickbooks.com/app/qbdt/products?productName=QuickBooks%20Desktop%20Enterprise&edi...
Beneath the 'full' application download is this option:
Already Downloaded? Get the latest updates
Release: Release 5(R5) | Size: 264 MB
That file is named en_qbwebpatch.exe and can be found in the downloads file on the computer where you are updating QB. If you right click on the exe and then click on the Digital Signatures tab. On the server where QB 2022 R5 crashes, that download file has a bad digital signature file attached. Once you click on the digital signatures tab, there is a box about halfway down that lists the signatures attached to the file. There should only be one and its for Intuit, Inc. Highlight that and then select the Details box. When the certificate pops up, the server where QB R5 crashes shows the following error for the Digital Signatures Details:
Digital Signatures Information
One of the countersignatures is not valid. The file may have been altered.
If I download the full QBE Installer, I see the same bad digital signature on the server in question.
If the update was downloaded and installed automatically after you prompted "yes" to update, then the installer executable is transient and usually deletes itself after the file is updated. One way to test if you see the same bad certificate on the computer where QB is crashing, you can follow the link above to download the R5 update and then you can check that file with the instructions above and if you see the same 'countersignatures not valid' error, then chances are that is the problem.
I've been in IT for 22 years and am the manager for our IT department so this stuff is like second nature to me. If my instructions are confusing or don't make sense please let me know and I can put something together with screenshots, etc. It probably won't be until tomorrow since I worked an all-nighter this week (on Windows Updates, I hate updates!) and I'm getting ready to crash.
I have yet to determine why this only happens on a single server (I have 6 servers with QB installed). My workaround for now was to reinstall using the download from February 2022, which is R3, (when I upgraded from 2019 to 2022) and simply not let it update.
