Thanks for testing this. Good to know that a work around is possible, even if it is not perfect.
From this Java issue I see that it is already existing in 1.8 build 25. And still not fixed.
Have you update the jdkhome property in the etc/snap.conf file or exchanged the jre folder within the SNAP installation? Otherwise the new Java installation will not be used by SNAP. For your information SNAP ships 1.8 build 60 of Java JRE.
Meanwhile we have updated all our machines to Windows 10. But we haven’t experienced this problem before. So I think this is not only a Java problem. Probably something else in combination with Java causes this problem otherwise more people would be affected.