Connection ErrorBad RequestThis page went staleSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
This page went stale
Your security token was rejected, usually because the page sat open too long or you signed in elsewhere. Nothing was saved. Reload the page and try again.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
I've encountered this issue a couple of times. But through trial and error, I found a solution back then, and I'm recommending it now. You don't need to delete anything; just disable it. It might be recognizing the patch as a program invader and preventing it from performing its functions without prompting. However, it's also possible that there are incorrect registry entries. If the path is wrong, the patch might simply write files to a different directory. You can check the patch for bugs in the following way: install patch 1.5 (for example), and then try to install 1.1 (again, just an example). If the patch works correctly, it should prevent the installation of an older version.
Умирает не тот, кто устал, а тот, кто остановился.