It's probably the same bug as this one:
https://bugs.launchpad.net/widelands/+bug/1685527
The best way to test this is with a debug build, for example this one: https://ci.appveyor.com/project/widelands-dev/widelands/build/job/7yskgifi1ny5mlnf/artifacts
This will give you some log output like in the other bug. On how to access the log output in Windows, see our FAQ:
https://wl.widelands.org/wiki/Technical%20FAQ/#how-do-i-get-log-output-in-windows-for-debugging
Windows Vista is end of life, but it would still be interesting to see what the problem is and if we can at least display an error message somehow.
It's probably the same bug as this one:
https:/ /bugs.launchpad .net/widelands/ +bug/1685527
The best way to test this is with a debug build, for example this one: https:/ /ci.appveyor. com/project/ widelands- dev/widelands/ build/job/ 7yskgifi1ny5mln f/artifacts
This will give you some log output like in the other bug. On how to access the log output in Windows, see our FAQ:
https:/ /wl.widelands. org/wiki/ Technical% 20FAQ/# how-do- i-get-log- output- in-windows- for-debugging
Windows Vista is end of life, but it would still be interesting to see what the problem is and if we can at least display an error message somehow.