SychicBoy [CS-RET]

Thanks for reporting this issue, I'll fix it in next version. A temporary solution is to enable `Keep Obfuscator Types` and/or disable `Remove Junks` options.

> https://www.sendspace.com/file/r4hb4o There's a problem with download link, please upload file in another website.

Hi, looks like the problem is about control flow deobfuscation, Send the target file from telegram: https://t.me/SychicBoy

You should use `preserve all metadata tokens` option.

So you should remove strong-name from assembly.

Which tool you used to remove strong-name?

How you used my tool to remove assembly strong-name when it's doesn't have a feature to remove assembly strong-name? https://forum.tuts4you.com/files/file/1353-removing-strongname-signature-in-net-applications/

You should remove strong-name from file that deobfuscated by .NETReactorSlayer using a third-party tool.

`strong-name removal protection` is one of .NET Reactor protection features. This feature prevent assembly strong-name gets removed by third-parties.

Ok.