Can't install MBAM3

[Traffa]

Same as last time, gets to the end of the Install and I get the following error message:

 

HKEY_Classes_Root/malwarebytes

RegCreateKeyEx failed; code 1450.

 

What is wrong with the install, please. I had Firefox close. It should install the Free version so I can put in my license key.

Edited September 15, 2017 by Traffa
typo

[Porthos]

2 hours ago, Traffa said:

Same as last time,

Can you try installing the latest 3.2.2.2029 over your existing product and let me know if that worked.

Just download the latest installer from : https://downloads.malwarebytes.org/file/mb3

Run the installer on top of your existing product. No need to uninstall.

Edited September 15, 2017 by Porthos

[dcollins]

If the suggestion from @Porthos doesn't work, can you please provide the logs requested below:

 

[Traffa]

15 hours ago, Porthos said:

Can you try installing the latest 3.2.2.2029 over your existing product and let me know if that worked.

Just download the latest installer from : https://downloads.malwarebytes.org/file/mb3

Run the installer on top of your existing product. No need to uninstall.

Previous product has been uninstalled. Chameleon spat the dummy with the same error message. I believe it is something in the Install process. Using Regedit appears to be the only way I know of to fix this issue. I have to wait till Wed next week for my ISP Support to have a go, I'm not gunna play with Regedit. I have the details on how it's done but don't feel confident enough to try it w/o damaging my Registry.

(Previous post "Problem with Upgrade to Premium", 29th June, 2017)

 

•  
• New Member
•  
• 
• Members
•  
• 11 posts

• Report post
•  
•  #7

Posted July 3 (edited)

I called Telstra Platinum (subscriber) here in Australia and they fixed the problem. They gave me the following notes:

Got a registry error when installing Malwarebytes.
Insufficient system resources.
Can't boot in safemode via MSCONFIG due to insufficient system resources.
http://www.migrate2iaas.com/node/10683 << attempting fix.
Worked.
Installed Malwarebytes.
Will not open now.
Running Malwarebytes Chameleon to try to fix the issue.
Insufficient system resources again.
Regedit - changed value from 60 to 90.
Booted into safe mode.
Still not working - same error.
Changed value from 90 to 120.
Booted into normal mode.
Issue now fixed.

(End of 29th June post)

The link there details how and where to change the setting using Regedit.....)

Edited September 16, 2017 by Traffa
Adding an additional comment

[Traffa]

My ISP technical support (Telstra Platinum) says the issue is with Windows 7 and I will need to talk to Microsoft about this. See link below for a description of the problem with Windows....

 

https://support.microsoft.com/en-us/help/237304/fix-regopenkeyex-may-fail-with-status-1450

[Traffa]

The problem is a corrupted version of Windows 7. It is NOT an MBAM issue apparently. I need a new copy of

Windows 7. I haven't done that yet and I miss my MBAM Premium.

[Traffa]

I have a solution to the problems I experienced trying to activate MBAM.

The Microsoft technical person said it is most likely Windows 7 that has been corrupted on my PC and thus the error msgs (as above). He said that the solution was to install a new copy of Windows 7, a clean copy and THEN try to activate MBAM (Premium).

I came up with another solution.

I had been unable to successfully install Windows Updates automatically, no matter when I tried it. Then, I hit on the idea of choosing to install ONE update at a time manually. I did this several times over the past week as new Updates appeared. Each time these individual Updates were successfully installed. I got to the point where no new Updates were available...and then yesterday decided,  ok,  maybe I can install MBAM now.

It worked. MBAM successfully installed.

I ran a full scan and it picked up 2 threats (PUPs) that it placed in Quarantine. The Windows anti-viral software could not see these.

So now.....it's all good!

 

 

 

[Porthos]

3 minutes ago, Traffa said:

So now.....it's all good!

Thanks for the update.