It looks like there’s a new version of that issue ticket here:
With 5.4 as target fix. It also has the suggested workaround of setting net.VerifyNetSessionID and net.VerifyNetClientID to 0.
It looks like there’s a new version of that issue ticket here:
With 5.4 as target fix. It also has the suggested workaround of setting net.VerifyNetSessionID and net.VerifyNetClientID to 0.