Malwarebytes AntiMalware

while testing MBAM due to a reported issue

On a default x64 build - there are 113 NLS files copied into Syswow64 and only 3 NLS into system32...

I can safely delete all the .NLS files in Syswow64 with no seemly ill effect on x64 Build...

but I do require these .NLS files in System32 (1252 not a requirement for me)
All these system32 NLS files are blocked from deletion and MBAM launches without error

Code: [Select]

//--Kyhi MBAM EN-US test good require sys32 files
Require_FileQ,c_874.nls
Require_FileQ,c_932.nls
Require_FileQ,c_936.nls
Require_FileQ,c_949.nls
Require_FileQ,c_950.nls
Require_FileQ,c_1250.nls
Require_FileQ,c_1251.nls
//Require_FileQ,c_1252.nls
Require_FileQ,c_1253.nls
Require_FileQ,c_1254.nls
Require_FileQ,c_1255.nls
Require_FileQ,c_1256.nls
Require_FileQ,c_1257.nls
Require_FileQ,c_1258.nls
Require_FileQ,c_20127.nls
Require_FileQ,c_28591.nls

With a EN-US x64 Default Build with Display, Audio and Network Drivers ONLY

the 3 Locked System32 NLS files are
936
1255
28591

I think they should be added to system32 via 1-Copy Files
Still No ill effect removing all 113 NLS files from Syswow64

And able to remove 110 out of 113 from System32 (except those 3 on EN-US)

Which means MBAM locks the 12 other NLS files..

For me anyway...

I give up,


reply 25
http://theoven.org/index.php?topic=1589.msg18844#msg18844

Shortly:
Since all working one way or another, with not having such wide time and with wasted time,
 I give up. 

OK

But are you testing with or without a network connection first ??

That is all I have been asking of you..

probably I tested without network connection.

nls locked files maybe about mbam or not, except complex languages, generally 4 - 5 files locked, on enu 2 is enough. (else bsod on boot).
 ps: pictures given on relevant posts with examdif...

As written before, I do not expect a progress on nls mismatch cases before simpler case examdiff pro solved..

and as written before, I give up drawing same circles,
 I am fine with plugins which all working one way or another.

Hi All
just to help clarify the error that some are finding on the older Malwarebytes AntiMalware plugins (v2)
on the Yomi server, as far as i can see
If you use the plugin Malwarebytes_Anti-Malware_L.Script (Download version) it will download the
latest server version, which no longer have the files mbamext,1.dll or mbamext,2.dll hence that error.
file-wise, they haven't been updated for a long time

If you use the packed version
Malwarebytes_Anti-Malware_PackedVersion_L.Script and it's associated file
Malwarebytes_Anti-Malware_PackedVersion_L_File.Script it would not error as the encoded file would be
correct for that time
So your options are either rework old plugin for newer files
or help with bob.omb's v3 development  at
http://theoven.org/index.php?topic=2278.msg25508;topicseen#msg25508

Thanks APT,

quick fix: updated (Download version) on server, so plugin not usable by new users anymore. 

also add link to bob.omb's v3 development

Malwarebytes 3 Plugin - For Win10PESE x64 - Packed Version -



Plugin v.1: https://mega.nz/#!cuZUBAbS!TalAadJ2Kmirm-9NxxUfuKCtfNBzzDRT--p-gl0EgRA (~70mb Download)

Can't wait to the see the XPE version 

XPE already has a Known Working Malwarebytes 3 Plugin..

Uses MBAM Newest Server Download to Provide Required Files..

It Works on Both x86 and x64 Builds..

And Runs From X (Ram) or Y (USB) Drive..


Thanks.. 

Do you mean this??

http://theoven.org/index.php?topic=2488.msg27328#msg27328

Innounp should now work correctly to integrate the MB3 plugin, no need to install after boot, this is the reason I was excited to see your version...
  This has been a long wait for v3

It is just a matter of extracting and then renaming ALL the program files...