How could this have been marked as "Solved", rolling back the patch isn't a real solution. I assume that QB would only allow a user to defer the update 3-4 times before forcing it, as this has become the new normal for QB. 

We need a patch to solve this issue that is affecting so many users. This patch literally renders QB unusable on the server and only workstations operating in Windows on the network can open the file and have full functionality without the COM Error crashing it.

In our case, anytime QB needs to access the internet in connection with a function, this crash occurs, such as Receive Payment, Help, etc.