Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Hello
1), Can anyone point me where can I find a solution for
"Unknown+User@DESKTOP-4G3DULF MINGW64 ~"
this happens when I try to install it in windows 10 and run: "runner64" and at the end shows that error.
2). When I try to install the driver is telling me that I have the latest driver installed. The devise manager shows that is in COM4, in the property manager General tab devise status says: This device is working properly but in the Events tab information says: Device USB\VID_9AC4&PID_4B8F\iceman requires further installation. I don't know if this problem is causing problem listed in #1.
I had follow the instructions, I had deleted previous installation and reinstalled thinking and I miss something but still the same end: "Unknown+User@DESKTOP-4G3DULF MINGW64 ~" .
Any advise will be always appreciated.
Thanks
Last edited by bestcarsauto (2019-06-24 12:08:38)
Offline
1) Did you delete the pm3 folder or any contents in it? I'll check ProxSpace in a Win 10 VM. What is your Win 10 build number and OS version?
2) That sound more like a hardware problem vid & pid values are correct and I believe Win 10 does not require a manual driver install. Although this could be normal behaviour as long as a COM port is assigned it should work. Try changing the USB cable and USB port. Does you Proxmark work on other systems correctly?
Last edited by gator96100 (2019-06-21 22:35:12)
Offline
Thank you for your reply:
Windows 10 Version 1903 (Just updated about 30 minutes ago) Built 18362.175
I had deleted previous installation and reinstalled thinking and I miss something but no luck
I found that DESKTOP-4G3DULF is the Device manager ID in my computer(on top of the device manager).
I was able to upgrade the Driver to the one that is in the repository file but that also din't help.
At this point still looking in google to see if I can solve the problem but is not much info when I google Unknown+User@DESKTOP-4G3DULF MINGW64 ~
Offline
Unknown+User happens when msys2/user_setup.sh does not run correctly. Make sure you run runme64.bat as admin.
Offline
Let me try run it as administrator I let you know if that works later.
Thanks
Offline
On a fresh Win 10 VM that is up to date I could not find a problem. Please post your "ProxSpace/msys2/etc/passwd".
Last edited by gator96100 (2019-06-22 00:37:19)
Offline
ProxSpace/msys2/etc/passwd
???I could not find file
Offline
Not luck running the runner64 as a administrator still same error "Unknown+User@DESKTOP-4G3DULF MINGW64 ~" at the end.
Offline
Not having ProxSpace/msys2/etc/passwd explains the Unknown+User problem. There is a problem creating the proxspace user. Does "ProxSpace/msys2/usr/bin/touch.exe" exist? Have you tried redownloading ProxSpace?
Offline
Hi
gator96100 thanks for your reply:
ProxSpace/msys2/usr/bin/touch.exe Yes is there now with the "ProxSpace/msys2/etc/passwd"
the "passwd" file does not exist and while installing or running "runner64" never ask me for a password, anyway I will download the zip again and I will try run it one more time and I will post the result.
Thanks again
Last edited by bestcarsauto (2019-06-22 17:31:05)
Offline
OK
I download a new zip file unzipped as instructions, installed as instruction and still having the same error
Offline
Unzip the Proxspace zip again, delete ProxSpace/msys2/etc/post-install/09-proxspace.post and change in ProxSpace/msys2/user_setup.sh from:
@echo off
setlocal
set "WD=%__CD__%"
if NOT EXIST "%WD%msys-2.0.dll" set "WD=%~dp0usr\bin\"
set "LOGINSHELL=bash"
to:
setlocal
set "WD=%__CD__%"
if NOT EXIST "%WD%msys-2.0.dll" set "WD=%~dp0usr\bin\"
set "LOGINSHELL=bash"
echo Setting up wprking directory:
echo %WD%
Post the complete output from the console.
Last edited by gator96100 (2019-06-23 23:28:07)
Offline
gator 96100 I really appreciate your your time and your help replying to try to solve my problem, I really do .
I had fix it after I spent a lot time on front the computer installing, reinstalling, searching, googleing ETC.
I will try to describe what is that I was doing wrong or what I think I did wrong from the beginner so other newbies like me don't do the same mistake:
I had installed the ProxSpace-master and proxmark3 files in c:/users/Owner's PC/Documents/GitHub.
To solve the problem what I did was to create a folder in c/: (root) and name it "projects"
after that I download ProxSpace-master zip in the projects folder and unzipped then using Github desktop clone the RRG/Iceman repository from https://github.com/RfidResearchGroup/proxmark3.git then copy all the contents from the proxmark3 folder into the proxspace pm3 foldern,
Run runme64 from ProxSpace-master folder then wait until finish and this time "BINGO"
no more errors
Follow the instructions from here: https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md
Then go to: https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Use_of_Proxmark/1_Validation.md
and https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Use_of_Proxmark/2_Configuration-and-Verification.md .
Now I will learn some commands and play to know more about this unit.
Thanks again gator 96100 for your help.
Offline
Your path did have a space in it, now it makes sense.
The first step under usage in the readme:
Extract 'ProxSpace' to a location on drive without spaces. For example C:\Proxspace or D:\projects\public\proxmark\proxspace are ok whereas C:\My Documents\My Projects\proxspace is not.
I suggest you add the prefix "solved" to the subject line
Offline
...an eye for details is important
Offline