Repeated disconnects to login screen during session/port transition (logs captured)

Summary Kuro repeatedly stalls, returns me to the login screen, and shows a Disconnect message. I close the client only after the Disconnect message appears. Therefore, the later clean exit/TerminateProcess(exit_code=0) entries are cleanup after the disconnect, not the cause. Client and system - Kuro client version: 3.2.0 - dinput8.dll version: 2.0.0.0, SHA256 8E7F3B67C5ABCFE4918C6EDB7A3FE86ABEF2981395E82E08CCD8F6CD241F5072 - Windows 64-bit, DisplayVersion 25H2, build 26200.8655 - GPU: NVIDIA GeForce RTX 4070 SUPER, driver 32.0.16.1062 - Storage: healthy NVMe SSD - Physical Ethernet: 1 Gbps - Chat mode: Classic (ChatMode=0) - ImGui viewports: disabled (enableViewports=false) - Windows 7 compatibility mode, Run as administrator, and Disable fullscreen optimizations are already enabled - Xbox Game Bar and Game DVR were disabled before the 17:22 reproduction Reproduction 1 - October 2, 2026 around 16:57 CST (UTC+8) - Client PID 12968. - Gameplay TCP endpoint changed from 92.114.107.112:7582 to 92.114.107.112:8484 at approximately 16:57:20. - At the same time has_user_local changed to 0. - The client recorded protocol-reset about three seconds later. - The process did not crash. It remained alive until I closed it after seeing Disconnect on the login screen. - Physical-gateway monitoring showed no packet loss or link failure. Reproduction 2 - October 2, 2026 around 17:22 CST (UTC+8) - Client PID 3364. - Around 17:22:03, has_user_local changed to 0 while the client was still running. - At approximately 17:22:07 the client recorded reason=protocol-reset, caller_last_error=183, has_user_local=0. - The client returned to login and displayed Disconnect. - I closed it at 17:22:20, producing the expected clean exit code 0. - There was no unhandled exception for this incident. - Twenty immediate probes to the physical router had 0% loss. Windows logged no Realtek/NDIS/TCP/DHCP link event. Other observations - A separate 30-sample router test had 0% loss, 0.53 ms average latency, and 9 ms maximum latency. - The physical NIC recorded no new RX/TX errors or discarded packets during live testing. - Process Lasso did not switch power plans repeatedly during gameplay; observed switches occurred only when Kuro started or exited. - Disabling Game Bar/Game DVR did not prevent the disconnect. - An earlier separate incident at 16:12:25 produced an unhandled 0xC0000005 access violation. I am treating that crash separately from these login-screen Disconnect events. Log files available I have the full crash_pipe, latest_state, map_load, visible_dialogs, launcher_observed_exit, and widget_world_entry logs for both captured reproductions. The forum composer does not expose an attachment field, so I can provide the 42 KB ZIP bundle through whichever channel staff prefer. Please correlate the timestamps/PIDs above with server-side login, channel, and map-transition logs. The first capture shows a gameplay server-port transition immediately before the protocol reset.