Win7 Virtualbox is giving this error when trying to launch a vm: Error loading 'crypt32.dll': 1790

Question

I installed virtual box 4.3.28 in my windows 7 box, tried to open an imported VM and got the error below.

I've seen some posts from about 1/2 year ago stating this was a problem with some windows security fix, but I do not have that fix installed and I have installed the supposed cure for it, to no avail.

KB3004394 is not on my system

older fixes that aren't helping me ( I do not see the offending KB file installed on my machine)

Vagrant laravel box, guest machine entered an invalid state

https://www.virtualbox.org/ticket/13677

error I am seeing:

1618.161c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume1\Windows\System32\crypt32.dll
1618.161c: Error (rc=0):
1618.161c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=8 \Device\HarddiskVolume1\Windows\System32\crypt32.dll
1618.161c: Error (rc=0):
1618.161c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\windows\system32\crypt32.dll' (C:\windows\system32\crypt32.dll): rcNt=0xc0000190
1618.161c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\windows\system32\crypt32.dll'
1618.161c: Fatal error:
1618.161c: Error loading 'crypt32.dll': 1790 [C:\windows\system32\crypt32.dll]

Answer 1

I had same error: Error loading 'crypt32.dll' on Win7 64bit, Vbox Version 5.1.10 r112026 (Qt5.6.2).

I've resolved in this way:

1. Start cmd as Admin
2. Run command: sfc /scannow

Answer 2

From superuser: https://superuser.com/questions/851148/crypt32-dll-is-broken-for-virtualbox-since-patch-tuesday-9-dec-2014

Download patch from: https://support.microsoft.com/en-us/kb/3024777

Important: make sure you download the x64 version for 64-bit systems.

Answer 3

I had the same issue with vb 4.16 and this fix solved it. http://www.microsoft.com/en-us/download/confirmation.aspx?id=45307

Answer 4

download latest version of vm virtualbox. if you are using 4.3.xx, it has this bug.