Sonic Pi 4.6.0 fails to boot on Windows 11 25H2 (tau connection timeout) but 4.5.1 works

[kirbylockard]

Summary

Sonic Pi 4.6.0 fails to boot on one Windows 11 25H2 machine, but Sonic Pi 4.5.1 works on the same machine, and Sonic Pi 4.6.0 works on a different windows machine.

System Info

• Sonic Pi version: 4.6.0
• OS: Windows 11 Version 25H2
• CPU: x86_64

Expected Behavior

Sonic Pi should boot successfully and open the GUI.

Actual Behavior

Sonic Pi fails to start with:
"GUI was unable to connect to the Ruby server"

Key Observations

• scsynth (audio engine) boots successfully
• tau (Erlang VM) starts but never completes handshake
• Ruby server repeatedly logs UDP errors
• Eventually times out waiting for tau

Relevant Log Output

From daemon.log:

• SuperCollider 3 server ready
• SuperCollider Server connection established

From spider.log:

• "Critical: UDP Server Tau Comms ack server..."
• "An existing connection was forcibly closed by the remote host"

Final error:

• "Unable to connect to tau (Promise timed out after 30 seconds.)"

Comparison

• Sonic Pi 4.5.1 boots successfully on this same machine
• Sonic Pi 4.6.0 works correctly on a different machine
• This suggests a 4.6.0 compatibility/runtime issue specific to this system

Troubleshooting Attempted

• Ran as administrator
• Disabled Windows Defender firewall
• Fresh install after factory reset
• No third-party antivirus or enterprise security software present

Additional Notes

Windows prompted for Erlang network permissions when installing 4.5.1 but not for 4.6.0.

[globalCitizenEarth]

Yes I found that 4.6.0 x64bit version works perfectly on Windows 11 Home edition x64 bit and my windows 10 Home edition x64 bit computer accepts 4.5.1 version x64 bit version but spits many error messages when I attempted at first the 4.6.1 x64 bit version.
So for windows 11 4.6.0 is a win and for Windows 10 4.5.0 is a win.
Hope this helps and if not then well no harm, no foul.