Windows 10: Install AU on unsupported laptop

My wife's Acer has no Windows 10 drivers for it on the on the Acer site, same deal for my ASUS laptop and my 2 old desktop PC's. I just let Windows install the drivers via Windows update. Everything works on all of them with the stock Windows supplied drivers. Just because the OEM doesn't list them doesn't mean Windows can't find ones that work. AMD, NVidia, Synaptics, etc all supply drivers to Microsoft for distribution via Windows update.

 

Nope. Defender only.

Great. But I don't have the time to do it before he needs it back. Only around for the weekend.

 

That was it. The Logitech Mouse he had doesn't work with Logitech Options, and Set Point never got installed, so it would hang on the reboot. Unplugged the receiver, and it went through.

THANKS!

 

Logitech Unifying Receiver? I ask because I have one plugged into just about every PC I own. I haven't had any issues upgrading with them connected? Keyboards, trackballs, touchpad, no mice though.

 

Yes, Logitech Unifying receiver. On one laptop no problem with mouse connected, on the other one the boot process hang.

 

@rpo, I, too, like Kerry, have the Unifying Receiver plugged in, and have no issues with the mouse. I even use it between my desktop and laptop. Not doubting for a minute what you say is true. Maybe if you un-pair the mouse and re-pair it, that might straighten things out. Or a different USB 2.0 port.

 

Ok, that's weird? I never install Setpoint, not sure if that was the issue. You got it figured out and that's what counts. Every once in a while I install the Unifying part of setpoint. If I have to link unlink devices. I like having my trackball and keyboard on the one receiver.

 

As i said in a previous post, the issue was corrected by applying the October cumulative update.
God and Windows work in mysterious ways.

 

OK, FWIW, here goes.

The laptop was upgraded from Win8 to WinX. The Logitech Mouse that is being used with it, the M510, is not supported by the Logitech Options software that Logi now uses for their (pointing) devices. I did not know this until I went to install Options - after installing (thanks for wasting my time, Logitech!) it pops up a message saying that the connected mouse is not supported, and that I needed to install SetPoint.

The machine never had SetPoint installed - and never needed it. So , I uninstalled Options and continued to troubleshot other issues on the laptop.

When the machine was finally ready for me to make another attempt, I let AU start its thing again. Sure enough, on first boot, it hangs. So, I unplugged the receiver (yes, it is a unifying receiver, probably a very old one), and forced the laptop off an rebooted, it rebooted back and continued to install the AU.

FWIW, my own laptop *and* my desktop both have Logitech Unifying receivers. The laptop has one from the Logitech Performance Mouse MX, and the desktop has one from the MX Master. Neither machine has ever had a problem when rebooting during the WinX upgrade installation process. So, I didn't suspect that the one in my Dad's computer could be a factor at all.

Looking at the hardware, I also see that the unifying receiver from my Performance Mouse MX is older than the one that my dad bought, in terms of actual purchase, but that his hardware version is older than the on with my Performance Mouse MX.

IOW, he probably bought it from a discount retailer to 'save money'.

I've plugged in a generic onn wireless mouse and it is working perfectly fine with the machine.

Thanks again for the tip, rpo. I gave you rep on that one - I'd never have thought to look at the unifying receiver.