(Patch Problem) Timed out waiting for patching process to exit.
|
when download of the patch is finished i get this error.
"Timed out waiting for patching process to exit" Error Any Ideas ? Last edited by Ruudoniac#4033 on Aug 4, 2012, 7:04:00 AM Last bumped on Jul 18, 2023, 3:39:50 AM
|
|
|
I had to reinstall the game to be able to play again.
Thought that it was fixed. But now we got 0.9.11f patch and the same error poped up. I dont think that reinstalling the entire game whenever a patching is needed is a solution. Please help ;( |
|
|
Hi there, I'm not sure why you would be getting this problem, but I can suggest a workaround.
There should be a file called "Client.tmp" in your game directory. If you delete the old "Client.exe" and rename "Client.tmp" to "Client.exe", and then run that, you should get in to the game. Please let us know if that works. Path of Exile II - Game Director
| |
|
Happened again with 0.9.11g patch
so i gave your workaround a shot. And it Worked, yay ! Thanks alot, if you need any info to identify whats causing this, just let me know. Last edited by Ruudoniac#4033 on Aug 9, 2012, 7:19:22 AM
|
|
|
I just wanted to say that this problem obviously still occurs at 0.10.5!
But the workaround works aswell! :) Maybe that helps, if anyone else has the problem! "The one who dies with the most toys is still dead."
- Geth, keeper of the Vault. |
|
|
Looks like it happens again in my case with 1.0.0d.
The workaround works with the additional step of deleting the old "PathOfExile.exe" and renaming "PathOfExile.tmp" to "PathOfExile.exe". |
|
|
A friend of mine just had this problem. According to him he is just downloaded a fresh standalone client from the site, patching failed with timeout and
" did help him. Extra info, his packcheck.exe said: " Last edited by Archan111#4592 on Dec 14, 2022, 4:58:48 AM
|
|
|
work for me
https://github.com/lnwza777/Auto_update_and_install_poe/tree/main |
|
|
Sounds like another process has open handles, meaning the process that created the handle might not have properly duplicated that handle for the process that needs it?
From what I read, even when a child process is created inheriting handles, the handle itself must have HANDLE_FLAG_INHERIT set to be inherited. If DuplicateHandle is used to provide process B with a handle from process A, does process A have the proper rights for the handle to actually be duplicated (PROCESS_DUP_HANDLE)? Lastly, the new handle does not depend on the closing of the existing one through some sort of async, right? Always fun to guess from a distance ;-) Did you try turning it off and on again?
|
|
|
Experienced this issue on a fresh install of the latest patch.
The workaround is still good. |
|
