Closed haggen closed 7 years ago
This is bad, need to fix this asap.
@haggen can you provide the output of of the application when not run with Admin but also with --debug
.
@Regner Later this evening I'll get the output (can't right now). Meanwhile I remember it saying that it couldn't listen on the device Device\{xxx-xxx...}
.
Here it is:
PS C:\Program Files\Albion Data Client> .\albiondata-client.exe -debug
INFO[2017-08-23T23:13:32-03:00] Starting the Albion Data Client...
INFO[2017-08-23T23:13:32-03:00] This is a third-party application and is in no way affiliated with Sandbox Interactive or Albion Online.
DEBU[2017-08-23T23:13:32-03:00] Watching processes for Albion to start...
INFO[2017-08-23T23:13:33-03:00] Watching Albion process with PID "1656"...
DEBU[2017-08-23T23:13:33-03:00] Will listen to these devices: [\Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}]
FATA[2017-08-23T23:13:45-03:00] Error opening adapter: The system cannot find the device specified. (20)
PS C:\Program Files\Albion Data Client>
What is the device id when you start it as admin. maybe he is looking at the wrong devices.
@Ultraporing Good point. Here it is, but please note that it's output from version 0.0.11.
PS C:\Program Files\Albion Data Client> .\albiondata-client.exe -debug
INFO[2017-08-25T17:49:28-03:00] Starting the Albion Data Client...
INFO[2017-08-25T17:49:28-03:00] This is a third-party application and is in no way affiliated with Sandbox Interactive or Albion Online.
DEBU[2017-08-25T17:49:28-03:00] Watching processes for Albion to start...
INFO[2017-08-25T17:49:29-03:00] Watching Albion process with PID "11372"...
DEBU[2017-08-25T17:49:29-03:00] Will listen to these devices: [\Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}]
DEBU[2017-08-25T17:49:29-03:00] Starting listener (online: \Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}:63779)...
DEBU[2017-08-25T17:49:33-03:00] Starting listener (online: \Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}:62034)...
DEBU[2017-08-25T17:49:35-03:00] Starting listener (online: \Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}:63536)...
We can see that the ID is actually the same, so it's probably about permission.
to me it looks strongly like a pcap problem. Pcdummy and I tried to reproduce the error with VM's and new user accounts without any privileges. But sadly we didn't get it, so this answer is kind of speculative. But all evidence points to pcap in my opinion since you are able to get the deviceID from windows[\Device\NPF_{FEF24484-FEB0-4762-9B87-789798DD5D69}]
but it fails to open the adapter. And since we are using pcap to open the adapter, I can conclude by process of elimination that this should be the case.
Did you check if pcap is blocked somewhere (the dll's and exe file you installed) or are set by windows as untrustworthy, maybe even a Virus scanner that gets stupid ideas?
"I tried to write my answer for you and the other devs. Maybe they got a Idea with the help of this new information"
My Windows (10 Pro x64 Version 1703 Build 15063.540) installation is pretty clean. I use very few software besides games (Steam, Discord, Battle.net, etc.). I use Linux to work so it's mainly a game station. Never installed anti-viruses, firewalls or anything of this sort. UAC (that thing that says "you need administration privilege...") is disabled.
WinPcap was installed using the installer provided here. Baseline is I followed the wizards and did nothing special.
I'll see about pcap's DLL.
I found no DLL in WinPcap's directory, only a rpcapd.exe
. Perhaps it's installed somewhere else? I also found a log, don't know if it helps but here it is anyway:
WinPcap 4.1.0.2980 Installation LOG
-----------------------------------------------------
Debug Information
Operating system detected on registry: 8 - AMD64
True operating system (kernel.dll): 8 - AMD64
npptools.dll present on the system: false
netnm.inf present on the system: false
nmnt.sys present on the system: false
End of log
-----------------------------------------------------
mine looks the same:
WinPcap 4.1.0.2980 Installation LOG
-----------------------------------------------------
Debug Information
Operating system detected on registry: 8 - AMD64
True operating system (kernel.dll): 8 - AMD64
npptools.dll present on the system: false
netnm.inf present on the system: false
nmnt.sys present on the system: false
End of log
-----------------------------------------------------
The wpcap.dll should be in C:\Windows\System32
and in C:\Windows\SysWOW64
With the next update albiondata-client.exe will run with higher privileges on Logon by default (minimized to systray). So no more access issues.
When I run the client I get this:
Now if I run it as administrator it works. Tested version 0.0.8 on Windows 10.