https://www.guardsquare.com/dexguard

http://jacquelin.potier.free.fr/HeliumHexEditor/

From SunBeam

Just a heads-up - from what I tested with latest version, all one needs to do is F7 over first PUSHAD, hardware breakpoint on ESP, on access, then Shift+F9. And you'll land at JMP to OEP T_T.. Reminds me of UPX.. 

Magicmida

Magicmida is a Themida auto unpacker that works on some 32-bit applications.

Functions:

    Unpack: Unpacks the binary you select. The unpacked binary will be saved with an U suffix.
    Auto create data sections: Restores .rdata/.data sections. Only works on specific targets. This is a must for MSVC applications using Thread Local Storage because they dont work properly otherwise.
    
Dump process: Allows you to enter the PID of a running process whose .text section will be dumped (overwritten) into an already unpacked file. This is useful after using Oreans Unvirtualizer in OllyDbg. Only works properly if data sections were created.
    Shrink: Deletes all sections that are no longer needed (if you unvirtualized or if your binary does not use virtualization). Warning: This will break your binary for non-MSVC compilers.

Note: The tool focuses on cleanness of the resulting binaries. Things such as VM anti-dump are explicitly not fixed. If your target has a virtualized entrypoint, the resulting dump will be broken and won't run (except for MSVC6, which has special fixup code to restore the OEP).

Important: Never activate any compatibility mode options for Magicmida or for the target you're unpacking. It would very likely screw up the unpacking process due to shimming.

Windows sometimes decides to auto-apply compatibility patches to an executable if it crashed before. This AppCompat information is stored in the registry and is linked to the exact path of your executable. This can be a problem if you're upgrading to a newer Magicmida version that has fixes for your target. You can try moving your target to a different path or look around in the subkeys of HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags.

Old targets from 2007-2009 often don't run on Windows 10 and require an older OS version to unpack. The unpacked binaries should then work on newer Windows versions, given that the application itself doesn't have incompatibilities.
Anti-anti-debugging

Newer versions of Themida detect hardware breakpoints. In order to deal with this, injecting ScyllaHide is supported. A suitable profile is shipped with Magicmida. You just need to download SycllaHide and put HookLibraryx86.dll and InjectorCLIx86.exe next to Magicmida.exe. Do not overwrite scylla_hide.ini unless you know what you're doing.
Command line usage

If you'd like to automate unpacking, it's possible to invoke Magicmida as a command line application. To do so, pass the parameters /unpack <filename>.
Unpacking applications with uiAccess=true

When unpacking an application that has uiAccess="true" in its manifest, you'll likely get process creation error code 740 even when running Magicmida as Administrator. To get around this, you need to perform the following steps:

    In Magicmida.exe.manifest, change uiAccess to true and recompile.
    You need to have some version of Windows SDK installed.
    Run makecert.exe -r -pe -ss MMTestCert MMTestCert.cer.
    Run certmgr -add MMTestCert.cer -s -r localMachine root.
    In my case, I also had to manually copy the cert to the "Trusted Root Certificate" store.
    Run signtool.exe sign /s MMTestCert Magicmida.exe.
    Copy Magicmida to C:\Program Files (x86)\Magicmida and run it from there. This step is important because uiAccess applications need to be in a "trusted location".

https://github.com/Hendi48/Magicmida

https://github.com/ergrelet/unlicense

https://www.mediafire.com/file/ykmhw4ewo5e5gz7/MSI+Unpacker+v1.3.zip/file