Error 36 Patch crash/loop

sigillmacfinn

We've been able to use the minimize/screen re/safe mode hack to get the game running since last update but now we cannot complete the patch as we get Error 36 "A file was locked that could not be opened for writing" the patch then attempts constantly to re-start until we hit Error 36 again & re-start & error 36 etc - this seems to occur at the "mirroring" part of the patch run.

Help!

kalehn

Same error here

sigillmacfinn

Patch now completes - HuzzaH! but still need to use the minimize/force verify
/safe mode method to get online - so many lost Invokes!!! Thanx for the Stone of Health though

adriaen666

If the logs (file ERRORS.log) contains lines like:

150821 06:35:49 15 [1] ESC : The patchclientlib is returning error code : 36\nA file was locked that could not be open for writing
150821 14:30:13 32 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing - Could not delete previously renamed file (D:/GRY/neverwinter/Neverwinter_pl/Neverwinter/Live/crypticError.exe.deleteme)

1. Turn off launcher.
2. Turn on Task Manager.
3. Go to "Processes".
4. Find process "crypticError.exe.deleteme" and kill it.
5. Delete "crypticError.exe.deleteme" file from your Neverwinter directory.
6. Turn on Neverwinter.

jw09

adriaen666 said:

If the logs (file ERRORS.log) contains lines like:

150821 06:35:49 15 [1] ESC : The patchclientlib is returning error code : 36\nA file was locked that could not be open for writing

150821 14:30:13 32 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing - Could not delete previously renamed file (D:/GRY/neverwinter/Neverwinter_pl/Neverwinter/Live/crypticError.exe.deleteme)

1. Turn off launcher.

2. Turn on Task Manager.

3. Go to "Processes".

4. Find process "crypticError.exe.deleteme" and kill it.

5. Delete "crypticError.exe.deleteme" file from your Neverwinter directory.

6. Turn on Neverwinter.Thanks! adriaen666 that did the trick ^_^

miasmat

In case you want to debug why the launcher is failing in the future, you can add "-console" to the launcher shortcut commandline. It'll show you the file name that's in-use, or other details that might help figure out what's gone wrong.