Forum Replies Created

Viewing 15 posts - 1 through 15 (of 102 total)
  • Author
  • in reply to: USB forwarding from Windows to Mac fails #32484


    I clearly see that there is some issue with loaning nxusb kexts on your macOS machine.

    Can you please share what macOS version you use?

    As well, you can try to update macOS and re-install NoMachine on it.

    To check the loading of drivers on the macOS machine run these commands.

    1. Close the NoMachine.

    2. Unload all drivers
    sudo kextunload /Library/Application\ Support/NoMachine/Extensions/nxusbvhci.kext/
    sudo kextunload /Library/Application\ Support/NoMachine/Extensions/nxusbvic.kext/
    sudo kextunload /Library/Application\ Support/NoMachine/Extensions/nxusblog.kext/ 

    All of these commands should fail with the reason: “(libkern/kext) not found”

    (kernel) Kext com.nomachine.kext.nxusblog not found for unload request.
    Failed to unload com.nomachine.kext.nxusblog – (libkern/kext) not found.

    If you have any other output, please restart your machine and try again.

    3. Load drivers to check that they are allowed in security preferences to be loaded.
    sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusbvhci.kext/
    sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusbvic.kext/
    sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusblog.kext/ 

    4. If you see such an error:

    /Library/Application Support/NoMachine/Extensions/nxusbvhci.kext failed to load – (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).

    That means that the user has to approve kext loading in the Security Settings, as described here:

    Such output also should be followed by a system pop-up, with the button: Open security Preferences.

    Once this is done for one kext, do that for the rest two ones, by launching the appropriate kextload command as described above.

    After this is done for all three drivers, restart your system and check USB functionality.

    5. If after launching the commands from step 2 you don’t see any output, that means that drivers are well loaded. Please run all three commands and after that run this command, to check that they are loaded:

    sudo kextstat | grep nxusb 

    The output should contain three lines with this kext ID’s:

    If you see such output, restart the machine and check the USB functionality.


    in reply to: USB sharing between Windows hosts #32478


    Can you please send us logs from both machines and the screenshot of the Devices -> Connect USB Device tab?

    You can send logs to forum[at]nomachine[dot]com (please use the topic title as the subject).

    in reply to: Update to 7.1.3 breaks USB sharing? #31972


    Thanks, happy to hear that everything works well now.

    Regarding the 10 seconds for listing the device, I can confirm that in this update there were no changes in code. That may cause such a delay. In general, it depends on how many OS-related factors and 10 seconds to list all local and remote devices could be considered as normal listing time.

    in reply to: Update to 7.1.3 breaks USB sharing? #31930


    Can you please share what OS and version are you using? And what is the kernel version as well?

    Can you also confirm that in both versions 7.0.211 and 7.1.3 nxusb.ko was well compiled, right?



    We already have a feature request for the automatic rebuilding of nxusb.ko module on a kernel update.

    Until it’s ready, you can manually recompile nxusb.ko module after kernel update

    Or you can re-install NoMachine after kernel updates and it will be automatically rebuilt.

    in reply to: USB not being recognized #31167


    Do you have Linux on both sides? If yes – try to install the required on the article packages and just simply re-install NM. It will build nxusb.ko during the installation.

    You can also manually check that on both machines nxusb.ko is built and exists on the path /usr/NX/bin/drivers/nxusb.ko

    Also, worth mentioning that the problem could be on any of both sides.

    in reply to: USB Install silently fails from v6 to v7 #30943


    First of all “USB device forwarding” and “USB Drive connecting” are completely different modules and work independently.

    After uninstallation of the previous NoMachine, you need to restart the machine, even better twice, to hint the Windows OS that drivers are removed and that’s a correct setting. After that, it will save a new configuration and you can install the latest NoMachine.

    in reply to: USB sharing from macOS Big Sur problem #30715


    Please accept our apologies for this issue. USB devices forwarding from MacOS Big Sur is not supported yet, but our development team is working on adding it, and soon we will release an update that will fix this issue.


    in reply to: Windows 10: No USB devices detected for forwarding #30341


    Windows side logs look good, and the USB forwarding module works well on that side.

    Most probably you have some issue with the remote, Linux side. Please check this article:

    As well as please attach logs from the Linux side if possible.

    in reply to: USB passthrough works sporadically #30101


    Regarding Windows.

    The UsbDk in upperfilters also might cause some problems on Windows side, just try to remove the program that added it, or remove only that key from upperfilters and check does it appears back after machine restart.

    Regarding Mac.

    The “one side forwarding” issue was caused by VirtualHere on my Mac machine. I fixed it by the following way.

    1. I have installed back VirtualHere.

    2. Via command line I uninstalled it by the proper way:

    2.1 Run this command (I runned it 2 times, first it installed drivers and second time in uninsalled them)

    sudo /Applications/ -b

    2.2. After. run this command and restart machine:

    sudo /Applications/ -u

    2.3 After restart run these commands:

    sudo kextunload -b com.virtualhere.vhusbd

    sudo chmod -R  777 /Library/Extensions/vhusbd.kext

    sudo rm -rf  /Library/Extensions/vhusbd.kext

    After restart the machine, and NoMachine’s USB forwarding should work proper way.



    in reply to: USB passthrough works sporadically #30028

    Meanwhile, I made some tests with VirtualHere on my Windows machine, and looks like, I can forward a device from the Windows to Mac (when Mac is a client), and from the Mac to Windows forwarding do not work.
    That’s probably because VirtualHere leaves some registered resources after it’s uninstallation. I’m investigating this issue.

    Can you confirm that behavior (one direction forwarding) on your side?

    in reply to: USB passthrough works sporadically #30027

    1. In the file log/nxusbd.log I see a couple of more lines comparing with your previous log. It’ most probably appeared before you were able to delete that kext. But to be sure, could you please delete this file and try to reproduce it few more times?

    2. I assume we have a similar problem on the Windows side.

    Could you please check this registry key on Windows:


    Do you see there something like DCV_USB_HUB_FILTER ? Or it’s the only nxusbf here?

    in reply to: USB passthrough works sporadically #30001


    I have found an issue with your Mac logs. It’s definitely about conflicting software KEXT loaded the same time as NM’s KEXTs are loaded.

    To be sure it’s a VirtualHere, I just installed it on our test Mac and were able to reproduce the same behavior and logs at our lab.

    Just run this command at your Mac’s terminal

    kextstat | grep usb | grep -v “apple” 

    And if you see here anything but NoMcahine’s KEXTs – that might be a problem.

    Even after manual stopping of VirtualHere and machine restart I still had VirtualHere’s driver loaded into the system:

    0xffffff7f853f0000 0x4000     0x4000     com.virtualhere.vhusbd (2.3.1) 520E80E7-44CE-3AFF-949D-291C7E817174 <59 6 5 3 1>

    So even having it installed, but not running may be a reason for issues (constant and not).

    The worst thing is that if you remove VirtualHere from Applications its driver will still remain in the system even after a restart of the machine.

    So to completely remove it you need to run the following commands in the terminal with admin rights:

    sudo kextunload -b com.virtualhere.vhusbd

    sudo /Applications/ -b uninstall

    sudo /Applications/ -u

    sudo rm -rf /Applications/

    sudo rm -rf /Library/Extensions/vhhcd.kext


    After restart com.virtualhere.vhusbd were not loaded anymore, and NoMachine forwarding worked again.


    in reply to: USB passthrough works sporadically #29979


    1.  Can you please check do you have any conflicting software from those list AR04Q01027 installed on any machine?

    2. Or maybe any other heave software that consumes huge resources of CPU and/or network?

    3. Can you please check the network ping time, is it constantly below 20ms and there are no spikes upper than 200ms?


     It will always be after being disconnected for a while, ill come back to it not working anymore.

    Have you tried to restart both machines and try again? Does it work?

    5. What type of device you are forwarding?

    6. If it will appear, you can collect logs and pass them to us. Collect them with an open session (with failed device forwarding). To collect logs from both sides use these articles: AR10K00697 and DT10O00163

    in reply to: USB passthrough works sporadically #29952


    Could you please tell us more details:

    1. What machine (Win on Mac) is under a private VPN?

    2. You connect with SSH or NM protocol?

    3. Is the protocol’s corresponding port (22 for SSH and 4000 for NM), or maybe some custom, open in your VPN network?

    4. Is that always reproducible (USB forwarding does not work) if you are connected through a VPN?

Viewing 15 posts - 1 through 15 (of 102 total)