http://bugs.winehq.org/show_bug.cgi?id=60005 --- Comment #27 from Michael Setzer II <mikes@guam.net> --- Looking at log file with claude.ai and it reports this. Mentions audio, but its not doing any audio?? Found it. Line ~432225: thread 012c calls terminate_process(handle=0000, exit_code=2147319808). That's not a normal clean exit — 2147319808 in hex is 0x80010000, which is an HRESULT with FACILITY_RPC set (the high bit + facility code 0001 = RPC/COM facility). In other words, some COM/OLE component call returned an RPC-facility error, and something (either that component or Pegasus itself) responded by calling ExitProcess with that HRESULT as the exit code — not a system-level crash, but the app tearing itself down after an internal RPC/COM failure. Notably, right before that termination call, 012c was doing registry writes to Software\Microsoft\AudioCompressionManager\DriverCache\... — ACM (Audio Compression Manager) codec cache entries (imaadpcm, msadpcm, msg711, l3acm, msgsm610). So thread 012c was in the middle of ACM/multimedia driver registration when it apparently hit that RPC-facility error and self-terminated. That's very plausibly your actual "freeze point" — the app didn't truly hang, it silently died mid-ACM-registration, and because it was in a modal/parent role, the rest of the process tree (0020, 0120, 0128, etc.) got torn down after it, which is what looks like a frozen/blank window until you force-close. To confirm and pin the specific call that failed, it'd help to re-run with +ole,+rpc added to WINEDEBUG (in addition to what you had) to see exactly which COM interface call returned that error right before the terminate_process: -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.