I second trying Pharo under WSL for robustness. I wrote a blog entry on how to set it up, and I think it's still valid:
https://fuhrmanator.github.io/2019/02/27/Pharo-in-WSL.html - Since you'd be using WSL2, you have to do things differently for��the DISPLAY variable:��
https://github.com/microsoft/WSL/issues/4793#issuecomment-588321333
As to the question of why Windows on Pharo is less stable, I have some experience using over the years other programs ported to Windows from OSS, e.g., LyX and InkScape. I have seen a repeating pattern: key OSS devs of certain libraries are hyper-sensitive to how things are done in Windows (rightly so, some things are very different and require creative��solutions that break when Windows changes).��We all know OSS resources are limited. Consequently the libraries don't get the love.or testing they need. Despite this I think the Pharo��team does a great job supporting Windows.
