Big Sur Xforce Keygen not opening

"You do not have permission to open the application “xf-adesk19”. Contact your computer or network administrator for assistance."
This is not opening on MacOS BigSur. What to do?
  • “xf-adesk19” cannot be opened because the developer cannot be verified.

    how to solve it. thanks for the help

  • Try this. ---> http://howhide.com/big-sur-xforce-keygen-not-opening

  • http://howhide.com/big-sur-xforce-keygen-not-opening

Add a Comment

Replies

Hello,

Deepl. will be my interpreter for the rest ;-)

I've been struggling for a few days now, but I've just found a solution that worked in my case.

I've been going round and round in circles, and I've come to believe that the problem is not about Big Sur giving permission to the application, but more likely a problem between UPX (since we're talking about an application compressed with upx) and Big Sur.

That said, it is possible to see that the compression with UPX must be kept, otherwise the application (its Unix executable in fact) that has been decompressed will instantly disappear from the screen...

To get around all these constraints I did some manipulations in a less aggressive environment, namely a Mojave virtual machine that I had to create for the occasion (Catalina would perhaps also be suitable...).

Under Mojave then :
1) Uncompress the app as said above :

upx -d [/...]/myApp/Contents/MacOS/myApp

2) Re-compress the app, but at the minimum level to preserve compatibility with Big Sur :

upx -1 [/...]/myApp/Contents/MacOS/myApp

That's all ! The app is now supported by Big Sur and can be launched directly :-)

Hopefully this will help a lot

PS : At the end of the process of using the app, I got an error message (from the target app) which had no consequence on the intended purpose.

Hello, in a macbook big sur M1 it is possible to do the whole procedure, I call brew install upx and it tells me that command not found, does anyone have a solution?

Homebrew is well installed on your MB?

sudo upx -d /Applications/xf-adsk20.app/Contents/MacOS/x-force

worked on BigSur 11.4 please do not forget -d option here or you will get a NotCompressibleException.

after install of homebrew and upx as mentioned in above user comments.

I am happy. :)

Hi all! I have followed all of the instruction, still no succes. When i run sudo upx -d command, it says 0 files unpacked and doesn't really help. I have tried it with different crack (x code) files. Any more ideas? Thank you in advance

For M1 mac users out there running on Big Sur with the CORE keygen (I think it might work with other keygens as well)

The command brew install upx won't going to work

Instead, use

brew install --build-from-source upx

in which will take the upx code and then build it from scratch

Copy the keygen to Desktop

Open terminal and write

sudo upx -d <path to the keygen>

Important note:

Dragging and drop the keygen app into the terminal with sudo upx -d WILL NOT WORK

Instead, the path to the keygen will have to be the entire path from

Keygen app -> Show Package Contents -> Contents -> MacOS -> The keygen name

And then drag that into

sudo upx -d

An example of a complete terminal line that you'll be executing will look like this:

sudo upx -d /Users/<your username>/Desktop/CORE\ Keygen.app/Contents/MacOS/CORE\ Keygen

This works for me, and I hope it will also for other people out there, despite it's a late reply

Hi everybody,

I can open now my folder but when I hit on mem patch in the xforce app it shows me this error message " not admin, wrong version on custom error", does anybody have the solution to fix this? I'm running under Monterey 12.0.1, Thank you

  • I'm getting the same error! Did you managed to fix it? Thanks

  • Same problem! All fine till "Not admin, wrong version, custom error".

    Any idea how to solve it??

  • Same error, is there any solution?

Add a Comment

Perfect "sudo upx -d" to restore XForce. To overcome "not admin..." problem, just set "csruth disable" while in recovery mode. The serious problem is that then XForce starts and plays "mem patch" correctly but the "request code" action generates only 57 characters instead of 64. Tested on mac-mini M1 and Monterey with XForce 2019, 2020 and 2020.1. I think only solution is to wait for an updated version of the keygen. But if anyone had a solution in mind in the meantime, I'd be more than grateful. ;)

  • "csrutil disable", sorry.

  • that's not the case actually, x-force always generate 57 characters (as any other Autodesk product with x-force keygen, in windows also) 64 characters only generated if you use official offline activation by Autodesk (by buying their product of course) I guess the problem is within the keygen itself not supporting M1/M2 for its Mem Patch command (not supporting ARM), you can try with Mac Intel, it will work I don't think x-force still making keygen for Autodesk Mac product anymore

Add a Comment

I have it running on Monterey , and mem patch success ! , but wrong activtion code all the time.

  • Same thing here, Running Montery, I manage to unpack the keygen but the activation code is wrong all the time.

  • me too, I got it as far as I could but wrong activation code.....no dice

  • SAME!!! anyone to solve this problem??????

Add a Comment

pouvez vous m’aider sur le même sujet ? Je galère merci