That's extremely unlikely and it's concerning that you think the exact same error at the exact same point starting after the exact same last-known good build is "not related." If that's a possible failure mode of your code base then your code base is pure shit.
I linked to several detailed bug reports and told you very clearly that I had the "exact same" problem. It is not encouraging that you won't even read the bug reports, and certainly doesn't encourage anyone to further help you.
I really don't understand your childish behavior. You flaunt your unwillingness to cooperate, as revenge for the offense allegedly inflicted on you by someone. This is stupid and naive. There is nothing difficult about naming your version of the Virtual Machine.
The error "Failed to open txtsetup.sif" can theoretically pop up for a million reasons\scenarios, and even fixing all of them may not help in your particular case, without providing information from you.
However, this error is extremely rare. Developers can't fix a bug that they can't reproduce. Therefore, extra efforts are needed to catch, eliminate or bypass it.
Hysterical insults on volunteer developers of a free open source project are not the best example of interaction.
You also provide a list of bug reports that are just similar, but probably not related to your particular issue.