DirectX Diagnostic Tool: no problems found (32 bit and 64 bit modes).

After 5.5 hours running, I finally killed the ClientPatcher.exe process. Still chugging along at 08% CPU but the memory usage now showed 49,608 K, so maybe you can’t call it completely “frozen”. No new MSI.log file popped up afterward; the only change in the install folder was the disappearance of the Lock2.txt file. I double-clicked ClientPatcher.exe and Lock2.txt reappeared. The only difference this time is that the memory usage is 71,476 K. This number is slightly variable: when I clicked on End Process (but then didn’t) the size changed to 71,444 K.

Tried that again in a copy of a fully installed game folder. The ClientPatcher.exe process is 117,468 K memory. 3 new files appeared in the folder: Lock2.txt, status.bin (contents “unpatched”) and the abortive Patcher.log file (open but ending in “running dreamworld control center and selecting a project should fix it”).