ProxMark 3 install stuck

I am trying to install PM3. I deleted the old directory completely, made a fresh install from the ProxSpase.7z. I started the RunMe64.bat. I get this error.


and the installation is stuck at 75%. I removed the directory and tried to install. I got the same result. Disabled Pacman signature check through the config file under /etc, and retried the install. This time, I did not get the error, however, the installation again got stuck at 75%.

For the third time, I deleted everything, restarted my system, and tried to install, but to no avail. I am still stuck at 75%. How can I go through the installation?

That looks odd… starting with cmd.exe…

  1. what directory did you unpackage the proxspace files into? We always suggest a path with no long names or spaces… something like C:\working\prox

  2. if you are starting runme64.exe with a double click, try first opening a command prompt and running it that way (Getting started with the proxmark3 easy - DT Info - Dangerous Things Forum)

2 Likes

If I’m reading this right, that error is for installing mingw-w64-x86_64-bzip2 but what’s hanging for you is mingw-w64-x86_64-python, the two problems don’t seem directly related?

In any case, the install completes for me despite the same error:

Although that step does take a bit, how long has it been stuck for you?

As an alternative, if you can’t get it to compile, you could consider trying the pre-compiled binaries from this site:

https://proxmarkbuilds.org/

Hello Thanks for responding.

  1. I am installing it on D:\InstRoot\ProxSpace (It was already working there. But I had difficulty in updating decided to delete and make a clean install. Also I have another computer where it was installed under the same directory and working). As you see not a long path and there is not spces around it.

  2. When I started from the command line first I got this error (pic 1).

After removing the file(db.lck) the setup continued, but with each step it told me it cannot find a file.(pic 2)

Finally stuck at imgw installation again (Pic 3)



Picture 3 shows it’s trying to install mingw-w64-x86_64-qt5-base, but earlier it was stuck on mingw-w64-x86_64-python, are you certain they are getting stuck and aren’t just slow?

That second error doesn’t seem to be terribly critical, and the initial errors in the first picture appear to have been resolved by removing that file, so I don’t think there’s any major harm in continuing from here, but personally I’d probably delete the whole install folder and start it fresh one more time

1 Like

Yeah delete and start fresh. Make sure the folder permissions for your user account are open enough (read/write or full). Open the command prompt without using the run as administrator option (the normal way, don’t right click and choose run as administrator).

1 Like

Already did it 3-4 times with the same result. Will try again…

Yes, now it has an error for both…

Fresh install, started runme64.bat from the command line. The result is still the same. It looks to me that the package cannot be downloaded for some reason. I will try another fresh install and change my country through VPN hoping that it might be a corruption issue in one of the mirrors.

Ok, did a fresh install to D:\InstRoot and started. The same problem occurred.

I did another fresh install this time at D: root. This time I got an error with bzip2 package as usual. But anyway, installation stuck at 76% as usual error while reinstalling Python package:

Hello,

I tried to give it another try in the evening. I tried to install. I refreshed the directory from the 7z file. Although the same error about the bzip2 was there, this time, the batch execution finished without any problem. I started git for proxmark3, and now it is compiling the image.


Persistence pays!

2 Likes

Do you have any idea what had prevented the installation and what is going on now? Becasue I saw some forum posts on similar issues especially concnetrationg around this bzip2 issue. But none of the posts did give a satisfactional explanation on when and why does it happen.