Bill Bigge
Comments
"So the issue is more : "Why did Windows 7 not produce a firewall popup" instead of "Multiplayer broken", isn't it?"
There you go, I changed the title to "Why did Windows 7 not produce a firewall popup" Does that make things better?
If I had known before I filed the bug report that it was an issue over MC interacting with windows firewall then I would have indicated it in the title at the time . . . in fact I probably wouldn't have filed it as a bug report at all, wouldn't I.
"Keep in mind that the "popup" is in fact a "popunder" when having Minecraft fullscreened."
On windows 10 it was a pop up - it kicked MC off fulscreen mode - on windows 7 there was no pop up or pop under at all, the entire thing was handled in the background with no dialog boxes appearing - hence the mystery and confusion over the cause of the issue.
Hopefully others haven't hit this issue but if they have then this report may come up when they search for a solution and they won't think its a bug and file more reports.
Ok, its working now. For some reason windows firewall on the windows 7 machine had blocked the Java exe for minecraft. The pop up I saw on the windows 10 machine was the same issue but the win7 machine didn't produce an alert so I only discovered it by manually adding an exception for java.exe in the runtime/bin folder for the minecraft installation. I'm curious about why the latest snapshot would trigger this when it was the only thing that had changed on either machine - we had played 1.13-pre3 a few days before with no problems. Nothing new had been installed on either machine and Java was already at the latest version.
How do I attach a crash report when the game has not crashed?
Disabling windows firewall made no difference.
This should not be marked as invalid because it is an issue with Realms - this happens when an upload to the realm fails, causing the realm server to crash and become unavailable.