0xc000001d error - failed to initialize

[moot]

The special installer from this page is signed by Oleg N. Scherbakov.

When I Google the name there appear to be references to rouge/virus associations.

Bottom line... is Malwarebytes_2.1.8_SSE2_Hotfix.exe (from this link) safe?

Does Schervakov have a partnership/relation to Malwarebytes.org?

[daledoc1]

Hello and welcome back:
 
Yes, the special installer is safe.

(If you use NoScript in Firefox, you will need to temporarily allow "box.com" and "boxcdn.net" for the download.)
 
>>However, unless you have an older system with certain single core processors and Windows XP, and unless you are getting that particular error when you try to upgrade to/install MBAM 2.1.8.1057, the hotfix ought not to be necessary.

 

IOW, it only applies to a very small subset of users.
 
If you run into problems, even after running the hotfix, please read the following and attach to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

 

NOTE: More info about v2.1.8 HERE; User Guide ONLINE; User Guide PDF; FAQ: Common Questions, Issues, and their Solutions

Please let us know how it goes.

Thanks,

[moot]

Thank you for the prompt response... I guess I am among a 'small subset' that still have to use XP on older processors to run diagnostic software/hardware.

I am able to load and run 2.0.4.1028 but when I accept the 'new version available' it will load but then lock up the computer (with 0xc000001d-error).

I will try the hotfix and post back.

[daledoc1]

Thanks for the additional info.

 

Yes, please let us know if the hotfix works.

 

If it does not, we can save a bit of time if you would please attach to your next reply here in this thread the 3 Diagnostic Logs from THIS PINNED TOPIC .

 

Thank you,

[moot]

Forgot to ask... are there any special instructions on how to run the hotfix? i.e., uninstall, etc.

[daledoc1]

Hi:
 
Darn, that's a good question.
I confess that the instructions here could be a bit clearer.

 

However, the sticky topic does not mention performing a Clean Reinstall, and the hotfix executable file is quite a bit smaller than a full MBAM installer.

 

I am not 100% certain and don't have an XP VM or test box to try it.

BUT I think one merely needs to run the hotfix on top of an existing installation of MBAM 2.1.8.1057:

 

 

If you are receiving this error, luckily there is a special installer that you can use to avoid the problem. Please download the special installer from this page. Once downloaded, simply double-click to run, and the program should install as normal.

 

AFAIK The hotfix only changes MBAM dlls, not system files.

So, it ought to be perfectly safe to try it.

IIRC, I am pretty sure that's what affected users did a few weeks ago, when the issue first surfaced and reports filtered in.

 

As a general rule, it would be a good idea to reboot the computer after running it.

 

If all else fails, we can start again from scratch, or you can post the 3 Diagnostic Logs for @AdvancedSetup and the forum experts to review.

 

Please post back and let us know how it goes,

[Firefox]

Simply run the hotfix on top of the existing copy of your Malwarebytes....

If Malwarebytes is running (and it probably isn't if your getting this error) exit it first.

[daledoc1]

^^ Much obliged, @Firefox.  That's what I thought. Thanks for confirming. ^^

 

@moot: please post back when you have a chance, to let us know....

[moot]

Here is what worked for me:

 

MBAM 2.0.4.1028 was running (realtime). I applied the hotfix (which copied the qt*.dll's & qwindows.dll). When message came that newer version was available I let it install and at the end unchecked the 'Launch...' and clicked finish. The computer appeared to lock up. I waited about 15mins and when windows won't open, Start button didn't come up, etc.... I had to power off.

I powered back up, went directly into Safe Mode and ran the hotfix. I then restarted and let the computer boot to Normal Mode.

Malwarebytes 2.1.8.1057 ran at startup and began downloading updates. MBAM Premium was up and running. All looks good.

 

Thank for your help and let me know if I can provide any other information that may help others...

[daledoc1]

Here is what worked for me:

 

MBAM 2.0.4.1028 was running (realtime). I applied the hotfix  <snip>

Thank for your help and let me know if I can provide any other information that may help others...

 

2.0.4.1028 is a very old, outdated version.

The hotfix was likely written to run only on the more recent build (2.1.8.1057), rather than making such a big version jump?

Moreover, as @Firefox had advised, it likely would have been preferable to exit out of MBAM Realtime protection before running the hotfix.

 

Perhaps that might explain the behavior your observed (we will need to wait for @Firefox or a staff member to confirm).

 

In any event, we're glad you were able to sort it out.

And we appreciate your taking the time to report your experience.

 

Cheers,

[moot]

Ok... just to clarify... when the new version (2.1.8.1057) was being installed I saw the files (qt5*.dll's) being copied. The install unloaded the previous version (icon removed from tray) and did not launch the new version. I think the behavior was due to the new version starting processes/services even though the gui was not launched. The dll's (that the hotfix replaces) caused the machine to lock up. Running the hotfix in Safe Mode and then rebooting normally allowed the processes/services to run/load correctly... imho

 

All is well that ends well... at least I will have enough posts to get my signature ... I hope...