Big Sur Xforce Keygen not opening

Instructions:

• Copy xf-adesk19 to your Desktop

• Open terminal  (Command+Space and type Terminal and press enter/return key)

• Paste the following code in terminal:

Code Block 
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null

• Wait for the command to finish. After completion run the following code:

Code Block 
brew install upx

• Now run this command:

Code Block 
sudo upx -d ~/Desktop/xf-adesk19.app/Contents/MacOS/x-force

• Close the terminal and open the xf-adesk19 on your Desktop.

Done!

after this, when you push Mem Patch open a windows with ERROR! Not admin, wrong version or custom error

Hi, i have the same problem with Core Keygen.app in Big Sur. Can you help me? I dont know what write in terminal for do it work!

Thanks in advance!

You do not have permission to open the application “xf-adsk20.app”.

Contact your computer or network administrator for assistance.

How to solve this issue. ????

I've run and installed it, but I'd like to remove it. How can I do that?

100% Guarantee Workable Answer is HERE

After surfing many replies to this "permission to open core keygen" issue, I just call out my "virtual macOS Mojave" and open the god damn app right away.

Yes, my degree is from business school.

Before I started I had to make sure my mac running on Big Sur can accept software installs from Anywhere.

In Big Sur Apple removed that option for the users but you can activate it by running this in your terminal

Code Block 
sudo spctl --master-disable

Then, I tried with the posted instructions here for homebrew, but actually, something went wrong so I went to their official website at brew.sh and got their installation code from there.

Its this one

Code Block 
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

After you type this in the terminal, you wait for the install and then you type:

Code Block 
brew install upx

For me, it didn't work putting the file on the desktop, so I put it in Applications, and then I wrote this in terminal:

Code Block 
sudo upx -d (and here instead of writing the directory its best to go to Applications > Right click xf-adesk19 and choose Show Package Contents > Contents > MacOS > x-force and simply drag and drop that file after the -d in your terminal and it should visualize the path)

And then press enter, and now u should be able to open that file on MacOS Big Sur.

Note if you already tried using the install code from this post and it didn't work, first run a Homebrew uninstall with this code:

Code Block 
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall.sh)"

And then run a fresh install with the code I just wrote.

Hope this helps.

Please, will share the download link xforce keygen Big Sur:>

Tried using the tips from @Snowghty to no avail. When I load the x-force file and press Enter, ups shows that nothing has been unpacked. I can't figure this out to save my life. Getting this thing to work is the last thing needed to retire my MacBook Pro from 2009 (yes, it's that old) to my new one. The keygen I have is for an older macOS. No idea where to find a more current one.

Does Xforce Keygen work with 2021 versions?

I applied the snowghty's solution. In the macs without chip M1 does work very well but in the mac with chip M1 doesn't work. ¿Someone have any idea how to fix it?

Hello guys,
You need to make sudo upx -d procedure not directly to xf-adsk20 file. You should right click the file first, then show the content

Contents-> MacOs->x-force

Now sudo upx -d (file location of x-force) simply select the file and move it to terminal. You will see it will be unpacked and start working.

However, with BigSur, I am having "Not admin, wrong version or customer error" Error. Although I given the permission by "sudo spctl --master-disable" , it is still giving error. Do you have any ideas how to solve out this?

because big doesn't supports keygen, you need to roll back to catalina i have done that too.

@persephonis

Could you please let me know step by step how you managed? I am still not able to open.
I have;

• Admin account

• Big Sur

• xf-adsk20

• enabled permission to open all apps

Many thanks in advance.

First: My English is Bad (I'm using Big Sur)
After install Homebrew, try command: brew doctor on terminal.
This command show how you install de XCODE software to execute the terminal commands.
You can try other way on homebrew website on "homebrew documentatio > installation > xcode3"
After install XCODE, repeat the homebrew installation, repeat a command "brew install upx".
After install UPX, use the command "sudo..." for unpack the file.
Enjoy.

Sorry for my english.
Hope this helps.

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

“xf-adesk19” cannot be opened because the developer cannot be verified.

how to solve it. thanks for the help

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. ;)

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