![]() Lucky for me, I had setup a VNC connection to my Z600, so I just logged in from my Mac and at least got control of Windows that way. I couldn’t access the Windows machine anymore either – so how was I going to start the Logitech software to repair this mess? The light on the mouse still came on, but the light on the keyboard (usually comes on when you press CAPS LOCK) was also dead. It was as if I had two dead devices on my desk. So I plugged the mouse USB receiver into the Windows machine too, and now NOTHING was working anymore – neither in Windows nor on Mac. ![]() The trouble was the keyboard was no longer detected on the Windows machine. And even when I switched on my Windows PC, the mouse was still working on the Mac. ![]() I was happy, modelling things in Blender (which is a little cumbersome with a Mac trackpad, or perhaps I’m just not used to it anymore). The good news was that when I used the original mouse receiver on my Mac, with my Windows PC switched off, everything worked just fine. So now I had to figure out how to UN-pair both devices again and put them back to how things used to be (before I started messing with them). I regretted pairing both devices to the same receiver and wished I hadn’t done that, for this very eventuality. But really, there’s only so much space on my desk, and I really don’t need more clutter in front of me for just an occasional switch. I know, it’s exotic, and perhaps I should have just bought another mouse. It all worked fine on my Windows 10 machine, until I wanted to use the mouse (not the keyboard) with my Mac. Turns out it was relatively easy to pair both devices to the same receiver, thanks to a small piece of software that can be found here, along with instructions on how to use it: Being an all-efficient belt-and-braces kinda guy, I tried my luck. Apparently you can connect up to 6 devices to one receiver and store any spare ones inside the mouse or keyboard. However, I heard great things about these little receivers and wanted to free up a USB port, and thought I’d connect both devices to the same receiver. I could plug both receivers in, and both devices would work great. I also had a Logitech M325 mouse, both of which came with Unifying USB receivers. Let me know if this works for you or not! I wish this helps you.I’ve recently bought a new Logitech K360 keyboard for my HP Z600 workstation. You can use Logitech Options to customize everything now. This works for me, and I tried to restart the system, everything is good. You may uninstall the "SetPoint" afterwards. Open "Logitech Unifying Software", you will be able to process all the setup steps successfully. Now Windows should be able to detect this Unifying receiver. After refreshed, unplug and replug in the USB 3.0 port again. Now reactivate the HID device in the Device Manager. After installing, re-plug in the Unifying receiver to one of the USB 3.0 Port, on the backside. ![]() Just install it, and ignore all messages, such as you don't have compliable devices, etc. ![]() This software seems like can fix the missing file in Windows. I downloaded it as a reference, if you can find it on your own, please do so, the name of the software is called Logitech SetPoint. Wait the Manager windows refreshes, and the device you just disabled is disappeared. Insert the corded mouse, and wait for a response, once the cursor appears, and you are able to control with the corded mouse, unplug the Logitech Unifying receiver. Go to device manager (right-click the Windows icon), under "Mice and other pointing devices", disable all "HID-compliant mouse" devices, not you cannot use your Logitech mouse anymore. If the software saying it cannot detect the receiver, then this is the right for you. My devices are "M330" and "MX Keys," get Logitech unifying management software available on your device, and install it. You have a keyboard or mouse that supports the Unifying function. You will need one cord mouse and an Internet connection.įirst thing first, check the same receiver and devices on another device, to make sure all hardware is fine, and this is only related to Dell's desktop device. I think it might be some Dell's Windows system issue, or my Windows missed some critical files for some reason. I have fixed this issue with the following settings. ![]()
0 Comments
Leave a Reply. |