/*
16 Feb

Updated Meltdown and EnigmaVB Unpacker

About Error Messages

Users can't read.

Or maybe they don't want to read. I don't know.

But one thing I know for sure - you must make your tools foolproof. If your tool is showing an error message, make sure even your grandma could understand it. Otherwise you'll be getting lots and lots of invalid bug reports.

For example, this is the error message my EnigmaVB unpacker used to show (as reported by ho3ein at Tuts4You):
enigmavb_error_message

It seemed to be very clear to me. First, tool tells user all the versions of Enigma Virtual Box it supports. Then tool explains that it expects to see a PE section with a name ".enigma2" but it found section with a name ".rsrc" instead. To me it's absolutely clear what happened: this file is not protected with Enigma Virtual Box (or it's hacked).

But you won't believe how many times this gets reported as a bug.

There was a similar problem with Meltdown. It clearly stated which versions of DeepFreeze it supports. Then it printed the detected DeepFreeze version. However, the error message didn't explicitly say "This version of DeepFreeze is not supported", it said "DeviceIoControl failed." It makes perfect sense from developer's point of view, but apparently is very confusing for users.

So, here are improved versions of my tools, fixing the error messages and some other stuff..

Improved EnigmaVB Unpacker

First of all, I fixed the error message. I also added detection and tested compatibility with the latest EnigmaVB v7.40. Hopefully, this will make users happier and less confused. smile
EnigmaVBUnpacker_v034

Improved Meltdown

Meltdown 1.7 fixes confusing error message with DeepFreeze Standard v8.x. Thanks to Alexander for reporting it.

I also took a closer look at DeepFreeze Enterprise versions and found a way to make Meltdown more user friendly. If DeepFreeze Enterprise v7.20+ is detected, Meltdown will get OTP Token automatically and immediately generate correct password.

meltdown17

Download links

Enigma Virtual Box Unpacker: Please get latest version from this post
Meltdown v1.7: https://www.mediafire.com/?b0bamd3t2d6bbkq

20 thoughts on “Updated Meltdown and EnigmaVB Unpacker

  1. Noob users the most of the time don't understand error messages or pretend to don't understand to try get help anyway. This is the flip side in doing public tools these days.

    By the way thanks for updates :) Really great job.

  2. Your unpacker v0.34 is unable to unpack this file {removed_link} Is it because the size is too large? I'm getting 'Out of memory while expanding expanding memory stream ' error.

    • Thank you for the bug report, I will check it later today.

      EDIT: Now that I see your file, it's really too big (3GB+). According to different forums:

      TMemoryStream has never supported memory blocks > 2GB. It was not updated when Int64 support was added to TStream in Delphi 6. It was not updated when support for Win64 was added in Delphi XE2.

      I will check if I can somehow work around that. But it requires quite a lot of work. :(

    • It looks like the file was not properly downloaded - it's smaller than it should be. If it's working correctly, it's a problem in my unpacker and I would love to fix it. If it's not working, please try downloading the file again.

      Also, could you upload the file somewhere and send me the link? Download link will not be made public.

  3. I would die for a fix. Please don't rush but if you free time I would love to hear your side on my error.

    My exe: (Tested that it also boots properly.)
    {link removed}

    • Your file is protected with "Enigma Protector", not "Enigma Virtual Box" - it's a different product from same authors.

      I will fix the misleading error message in my unpacker - but that won't help you to unpack your file.. :)

  4. I thought they were exactly the same. Enigma protector also has the option to virtualize files so what exactly is the point of enigma virtual box? Thanks for your help as well! :)

  5. Thanks for the links and help kao. I completely understand now. I feel like a major noob, but when I try to register for the tuts4u account, they want me to decode a string, and I'm not honestly sure which encoding they're using. I'm familiar with a few but not this one. Thanks.

  6. whats up bro
    would you please help me it looks like i need your help, i scanned my app with snd cryptor scanner it says its protected with Enigma encryption (WiteG)
    and RC4 so when i use your utility it doesnt detect Enigma it say its hacked so is because of rc4 or something else please just give a clue this is worth a life
    you got my email please do respond i will give you a link to the my App and i will make it worth

    • Enigma encryption algorithm has nothing to do with Enigma Virtual Box. There's nothing I can help you with.

  7. Is it possible to release the source code of the meltdown tool or at least create a console version of it? Need to output password or error messages on console. Thanks in advance!

Leave a Reply

Your email address will not be published.

Number

*/
16 Feb

Updated Meltdown and EnigmaVB Unpacker

About Error Messages

Users can't read.

Or maybe they don't want to read. I don't know.

But one thing I know for sure - you must make your tools foolproof. If your tool is showing an error message, make sure even your grandma could understand it. Otherwise you'll be getting lots and lots of invalid bug reports.

For example, this is the error message my EnigmaVB unpacker used to show (as reported by ho3ein at Tuts4You):
enigmavb_error_message

It seemed to be very clear to me. First, tool tells user all the versions of Enigma Virtual Box it supports. Then tool explains that it expects to see a PE section with a name ".enigma2" but it found section with a name ".rsrc" instead. To me it's absolutely clear what happened: this file is not protected with Enigma Virtual Box (or it's hacked).

But you won't believe how many times this gets reported as a bug.

There was a similar problem with Meltdown. It clearly stated which versions of DeepFreeze it supports. Then it printed the detected DeepFreeze version. However, the error message didn't explicitly say "This version of DeepFreeze is not supported", it said "DeviceIoControl failed." It makes perfect sense from developer's point of view, but apparently is very confusing for users.

So, here are improved versions of my tools, fixing the error messages and some other stuff..

Improved EnigmaVB Unpacker

First of all, I fixed the error message. I also added detection and tested compatibility with the latest EnigmaVB v7.40. Hopefully, this will make users happier and less confused. smile
EnigmaVBUnpacker_v034

Improved Meltdown

Meltdown 1.7 fixes confusing error message with DeepFreeze Standard v8.x. Thanks to Alexander for reporting it.

I also took a closer look at DeepFreeze Enterprise versions and found a way to make Meltdown more user friendly. If DeepFreeze Enterprise v7.20+ is detected, Meltdown will get OTP Token automatically and immediately generate correct password.

meltdown17

Download links

Enigma Virtual Box Unpacker: Please get latest version from this post
Meltdown v1.7: https://www.mediafire.com/?b0bamd3t2d6bbkq

20 thoughts on “Updated Meltdown and EnigmaVB Unpacker

  1. Noob users the most of the time don't understand error messages or pretend to don't understand to try get help anyway. This is the flip side in doing public tools these days.

    By the way thanks for updates :) Really great job.

  2. Your unpacker v0.34 is unable to unpack this file {removed_link} Is it because the size is too large? I'm getting 'Out of memory while expanding expanding memory stream ' error.

    • Thank you for the bug report, I will check it later today.

      EDIT: Now that I see your file, it's really too big (3GB+). According to different forums:

      TMemoryStream has never supported memory blocks > 2GB. It was not updated when Int64 support was added to TStream in Delphi 6. It was not updated when support for Win64 was added in Delphi XE2.

      I will check if I can somehow work around that. But it requires quite a lot of work. :(

    • It looks like the file was not properly downloaded - it's smaller than it should be. If it's working correctly, it's a problem in my unpacker and I would love to fix it. If it's not working, please try downloading the file again.

      Also, could you upload the file somewhere and send me the link? Download link will not be made public.

  3. I would die for a fix. Please don't rush but if you free time I would love to hear your side on my error.

    My exe: (Tested that it also boots properly.)
    {link removed}

    • Your file is protected with "Enigma Protector", not "Enigma Virtual Box" - it's a different product from same authors.

      I will fix the misleading error message in my unpacker - but that won't help you to unpack your file.. :)

  4. I thought they were exactly the same. Enigma protector also has the option to virtualize files so what exactly is the point of enigma virtual box? Thanks for your help as well! :)

  5. Thanks for the links and help kao. I completely understand now. I feel like a major noob, but when I try to register for the tuts4u account, they want me to decode a string, and I'm not honestly sure which encoding they're using. I'm familiar with a few but not this one. Thanks.

  6. whats up bro
    would you please help me it looks like i need your help, i scanned my app with snd cryptor scanner it says its protected with Enigma encryption (WiteG)
    and RC4 so when i use your utility it doesnt detect Enigma it say its hacked so is because of rc4 or something else please just give a clue this is worth a life
    you got my email please do respond i will give you a link to the my App and i will make it worth

    • Enigma encryption algorithm has nothing to do with Enigma Virtual Box. There's nothing I can help you with.

  7. Is it possible to release the source code of the meltdown tool or at least create a console version of it? Need to output password or error messages on console. Thanks in advance!

Leave a Reply

Your email address will not be published.

Number