MSYS2 + win7: 'invalid crypto engine'

(Highcarbschwabe) #1

I am having trouble with MSYS2 under windows 7 (x64):
“pacman” commands do not work, and MSYS2 complains about an ‘invalid crypto engine’.

Judging by what I have read about this apparently common issue is that it can have many causes and that it can be time consuming to identify your particular problem and fix it.

So, since it can be assumed that through MSYS2 many people lose significant amounts of time (I already did), are there better alternatives and shouldn’t the standard “how to set up your dev environment” recommendations at least warn us about the problems with MSYS2 and mention alternatives?

If there is no substitute, the addition of a troubleshooting paragraph with a collection of the most common problems + how to fix them would be very nice to have.

In themeantime: Did you come across the ‘invalid crypto engine’ issue? How did you fix it?

Thanks a lot!


I’ve had no problems, but I believe others do. Considering how widely used MSYS2 is (compared to VCV Rack), it doesn’t seem realistic to ask VCV to prepare a document on trouble-shooting MSYS2.

(Andrew Belt) #3

Is this a fresh MSYS2 install? Can you post the error message or a screenshot? I’ve never seen this problem, so it’s wrong to assume that just because you have it, everyone has it.

Also note that Windows 7 support ends in less than a year. Once Microsoft drops support, most software companies will drop support as well.

(Phil Golden) #4

Iv’e not seen this issue myself, but a quick google search shows others with the issue also. A few questions come to mind.

Is MSYS2 installed in the root of C drive? C:\msys64
I’m not too sure if running in safe mode can help but, what happens if you try to run in safe mode with networking?
Are there any programs from the following list that are installed? disabling those help?

(gc) #5

I had this error once on a different machine–I think it was a firewall issue in my case.

I assume you’ve seen (which also mentions the Big List of Dodgy Apps that @Coirt linked).

In my experience (not extensive) most Cygwin and Cygwin-derived issues come from the BLODA.