airhv
airhv copied to clipboard
Air14
Applications lose ability to communicate over network
As soon as the on.bat script is executed and the drivers start, applications fail to communicate over the network, including localhost. Active connections drop, and new connections fail. No debugger running yet and all driver options were previously set to disabled (unchecked) and saved. Tcpview shows sockets are created for each attempted connection, however wireshark shows no traffic from the applications hitting the interface. Once the off.bat script is executed and the drivers stop, connectivity is restored in short order.
Is this known/expected behavior?
Windows 10 Pro 22H2.
Is this happening on a real hardware or in a virtual machine?
Real hardware. The server is a dedicated test environment, not running VM's.
I should note, it appears only applications are affected, and not system services. As the server is accessed via RDP, and that connection is not interrupted.
Is this server your private machine that you have physical access to, or is it something like Google Compute Engine, AWS EC2, etc. ?
Is this server your private machine that you have physical access to, or is it something like Google Compute Engine, AWS EC2, etc. ?
Private server. It's a Dell T620 that is physically in my possession.
Can you check if this happens when you start airhv.sys, or if both drivers need to be loaded?
Can you check if this happens when you start airhv.sys, or if both drivers need to be loaded?
So the issue does occur when only airhv is started.
I did note some more specifics on the symptoms as well, so please bare with me as I'm trying to spot anything that may be relevant for you, but it's such a "in the background" type thing that I'm not sure what's related and what's not.
The application I have running and would be attaching the debugger to has a web GUI interface accessed at localhost:port. Prior to starting either airhv or the hyperhide drivers I have the webGUI up and connected, ( to note, I have tried loading the drivers first and executing the application with the debugger rather than attaching, in that case web gui is not accessible at all to begin with ) it shows information about the application as well as some uptime timers etc. Once I start the drivers ( or as last tested, only airhv ) everything does actually stay working, until I click a command in the webgui.
At first I thought it was immediately when drivers start, because the next step would be to execute a routine in the webgui, which doesn't work. But I noted today that if I don't execute anything, the timers etc do continue to update in the GUI. But as soon as the application makes a state change, or possibly due to opening threads?, everything drops on communication. It is 100% repeatable, and only occurs with the drivers.
Could you build new airhv and check if the last commit 31253da586b8b0f9de3f65d4c34e642f38d4dd5e fixed the issue? (Don't try to start hyperhide as it is not yet compatible)
Could you build new airhv and check if the last commit 31253da fixed the issue? (Don't try to start hyperhide as it is not yet compatible)
Sure. Will report back once I have a chance to do so in the next day or two.
Could you build new airhv and check if the last commit 31253da fixed the issue? (Don't try to start hyperhide as it is not yet compatible)
Unfortunately the issue still occurs with a build from latest source. If there's any kind of system logs I could provide, or debugging steps I can assist with, please let me know.
When running airhv/hyperhide in the past, once in awhile ( I'd say maybe 1 in 10 - 15 uses ) when starting the services it would lock up the server and require a hard reboot. When testing this build of airhv ( by itself, not with hyperhide as instructed ), it locked the server, but this time it did so when I stopped the service, which has not happened before. May not matter/be related, but caught my attention, so passing along.