Everything posted by RDL2017
This problem appears to have been fixed in MBAM 22.214.171.1240 beta. For details see "3.4 beta fixes update Failure when TEMP is on RAM Drive" in Malwarebytes 3.x Beta - Malwarebytes Forums at https://forums.malwarebytes.com/topic/222955-34-beta-fixes-update-failure-when-temp-is-on-ram-drive/ Thanks for the fix.
Please read my post again, more carefully. You will see that I was actually supplying information which had already been requested from several other people who then failed to provide it. The problem has been reported by others but none of them had replied when asked about RAM drives. My post confirms the trigger of this bug and, in passing, provides a quick and temporary change which circumvents it. I was already well aware that this problem had previously been reported but that no-one had confirmed its connection with RAM drives. I'm totally bemused by your telling me of
Runtime Error (at 47:120): Could not call proc =================================== Microsoft Windows 10 Pro x64 Version 1607 (OS Build 14393.1480) My %Temp% and %Tmp% are normally set to a RAM drive, in format 'Z:' (no quotes). Attempting to update, offline, from MBAM 126.96.36.1993 free to MBAM 188.8.131.523 free using mb3-setup-consumer-184.108.40.2063.exe I repeatedly found that immediately after selecting the language, installation failed with the message: "Runtime Error (at 47:120): Could not call proc" I saw the same behaviour when I tried the mb3-setup-consumer-220.127.116.119.exe beta ins