Jamesbberg,
No, none of the fixes suggested have fixed my issue, including checking the version of VC_redist.x64.exe installed. Here is the issue I'm experiencing, what I've identified, and my temporary workaround:
The suggestions to make sure you have the latest update reveal that Intuit isn't really paying attention. It IS the latest update - R5 that is causing the problem.
I have 6 servers that run QuickBooks Enterprise 2022 - two database servers and 4 remote desktop servers for my users to access their files. All servers run the same updated version of Windows Server 2012 R2. I have QB R5 successfully running on 5 of those servers. The last server, also w2k12 r2, will not run R5. When I update to R5, QB crashes at the splash screen. I can't even GET to a company file on this server since it crashes immediately. It crashes on everyone's RD profile so it can't be a bad qbwuser.ini file (or they are all bad).
After a lot of digging and research, I isolated MY issue to a malformed Digital Signature that is attached to the R5 download (see my previous posts for more details). What is most puzzling is that I ONLY have this issue on this single server. All other servers download the installer and the Digital Signature is fine. If I copy a known, good installer to the bad server, the certificate shows as malformed. I then built a new, remote desktop server, same OS, same updates, and I can download a good copy of the installer. If I copy the installer from the server that is crashing, it copies over just fine and I can install QBE R5. Therefore the problem is with this single server. However, that doesn't negate the issue because I believe this is the crux of the problem.
My workaround was to reinstall QBE 2022 R3 on this one server, which runs just fine. I'm hesitant to move my users to a new server since they've lost enough time already. Those who have rolled back to QB versions other than R5 have discovered they can work again.
I periodically repost these details in the desperate hope that someone, anyone, from Intuit will see it and use it to identify and fix the problem. I can get by running R3 only so long.
