I hate to say it, but I’m stuck.
Do you have physical or virtual access to the machine if it comes to that?
Since I know you’re a computer guy, I’ll speak techy.
In the past, this has been a low-level issue with one of Bloom’s dependencies being a different version than one of its dependencies’ dependencies expects. The problem occurs when Bloom is trying to initialize its localization files but the localization library is unable to load its dependencies, creates a 0-length file, and crashes.
But in the past, I’ve been able reproduce the problem easily by removing the localization files in
~\AppData\Local\SIL\Bloom\localizations (causing it to regenerate the localization files). I can’t create the problem that way with 4.8.0. So there must be something different about that machine.
A couple things to try…
- You could delete the files in
~\AppData\Local\SIL\Bloom\localizations yourself on the off chance there is a bad one there and Bloom isn’t trying to regenerate them.
- You could install the beta, 4.9. This can run alongside (but not at the same time as) the Release (4.7 or 4.8). Besides allowing the user to gain the features of 4.8+, this might give us some clue as to what is going on (knowing if it works for 4.9 or not). https://bloomlibrary.org/installers