I'm not able to comment, so I'll just answer here.
If you have to perform the unpacking manually, you should ask yourself - to what extent do you need it unpacked? What are you trying to achieve with the unpacked file?
More often than not, you don't need it fully unpacked, so that it looks similar, if not the same, as the original file.
In any case, with any packers, I suggest you just load up x64dbg with anti-anti-debugging plugins. Try a few configurations here and there - the standard hooks etc. should work.
If you are looking at static analysis, you will want to use tools like Scylla to dump the program at runtime and reconstruct the IAT (Import Address Table), which will give you information for calls to windows API / dlls.
If the unpacker scripts don't work, perhaps there are tutorials online on how you can unpack it by hand - fully or partially? Even if the tutorial is an old one, it can usually still be a good reference. The packer's protection techniques do not really change at the core most of the time.