MacOSX - Problem

14 posts / 0 new
Last post
MacOSX - Problem

Hi all,

I just wanted to inform you that the new version 4.5.2 of the Client software will not work on MacOS Clients when freshly installed:

Bug report:
Once the driver is installed, it will end up with a successful but will subsequently throw an error-message similar to the one from this forum post:

Freshly install VirtualHere.dmg v4.5.2 on any MacOS X from 10.11 - 10.13.
Try to bind a USB-device and install the driver software

Open a terminal; Execute:
sudo /Volumes/VirtualHere/ -y
sudo /Volumes/VirtualHere/ -u
Install VirtualHere.dmg v4.5.1

Best Regards,

Additional information

You can update to 4.5.2!

Once, you installed 4.5.1, you can simply update to 4.5.2. In high Sierra, you have to Allow the publisher in your security tab once again. To do so, you have to press ALT when you click on allow. After that, it will ask for a reboot that is not necessary and you can subsequently update the osxdriver with success.

Update not working

Ok, it is apparently not working - you cannot add the USB-device - Sorry for the confusion


Ok, i accidently uploaded a broken build yesterday, can you download again and it should work now.

Fresh install of 4.5.2 on macOS 10.13.4 fails installing client

Fails installing client driver with the error:

16:21:34 INFO :VirtualHere Client 4.5.2 starting (Compiled: May 15 2018 11:59:10)
16:21:34 INFO :Using config at /var/root/Library/Preferences/vhui Preferences
16:21:34 INFO :IPC available at /tmp/vhclient
16:21:34 INFO :Auto-find using Bonjour - on
16:21:34 INFO :Auto-find using Bonjour SSL - on
16:21:45 INFO :No drivers installed, I am installing new ones...
16:21:47 INFO :Using OSX 10.9/10.10/10.12/10.13 driver
16:22:32 INFO :Installed driver is now version
16:22:32 ERROR :IOIteratorNext = 0. com_virtualhere_vhhcd is not correctly registered in the kernel, please reboot and try again

Could you make 4.5.1 available so I could try the trick in this thread?


Did you approve the Virtualhere extension in the System Preferences in OSX?

I couldn't find the menu in system preferences...

I followed the advice in
Perhaps I misunderstood you? I expected to be able to select "per issuer", but this was global.

Sorry, realized my mistake

In the System preferences tab, extensions, VirtualHere is not an option.

Tried uninstall followed by install (failed)

sudo /Volumes/VirtualHere/ -u
sudo /Volumes/VirtualHere/ -d
The popup says "success" but command line reports:
sudo /Volumes/VirtualHere/ -d
06:14:23 PM: Using OSX 10.9/10.10/10.12/10.13 driver
installer: Package name is osxdriver
installer: Installing at base path /
installer: The install failed (Installeraren stötte på ett fel som förhindrade installationen. Kontakta programtillverkaren och be om assistans.)
anders:~/Downloads >

The part in swedish only says " the software developer...", nothing of value.


Ok i think the problem is you have not Approved the virtualhere extension when the client was started. You can do this again like this

See here for a quick overview

Basically you need to try run the virtualhere client, let it fail to load the driver. Exit the virtualhere client, open System Preferences... -> Security and then allow the Extension from VirtualHere Pty. Ltd. Then reboot the osx then run virtualhere again.

Thanks, driver installed without errors

Thanks for your help, the driver installed. Now everything "seems" to work. Unfortunately, I don't think the selected device, marked "(in use by you)" shows up. My tool (mplabx) cannot find the device and listing devices using:

> system_profiler SPUSBDataType

Does not show "VirtualHere USB Enchanced Host Controller:" at all. (I have my old laptop running OS X Yosemite 10.10.5 to compare with.)

Thanks, for your time. :-)

I think my problems... have changed to be shared with the ones described in another thread:


OK unfortunately you'll have to wait until apple fixes it in osx

Thanks a lot for your support

I wish you good luck "fighting" Apple.
Btw, I upgraded to a much newer MPLAB-X IDE (from v2.2 to v 4.15) which could find the ICD-3 device. So, as far as I'm concerned, the problem is solved. :-) I love your product!

Log in or register to post comments