On Tue, 9 Jul 2019 06:13:21 -0500, VanguardLH wrote:

Eric Stevens wrote:

They are probably on whatever drivrs Driver Detective fished out for
them Your point is a good one. I shall try it.

Don't know from where you are getting drivers with that software.

It seems to get them from original sources as well as whatever
Microsoft seems to offer. In many cases its possible choose from a
selection. I've used it for several years and have had no reason to be
unhappy with it.

Also,
not having the latest driver is not some serious flaw in configuration.
Sometimes older drivers work better than new one. New code = new bugs.

Did you configure Win10 to *not* update the hardware drivers? You could
roll back to the prior driver version.

https://www.windowscentral.com/how-r...ver-windows-10

I didn't think of that at the time. I just made a clean upgrade of
Dell.

Uniied corded. If I have identified the model correctly Corsair has a
K520R and Dell has just been fitted with a MK270R.

Those are wireless mice, not corded.

I don't know why I wrote 'corded'. I know it was late at night.

https://www.logitech.com/en-us/produ...ss-combo-mk520
https://www.logitech.com/en-us/product/11052?crid=1759

I thought that was a problem with the Dell when I found the battery in
the mouse had ruptured and oozed inside he mouse.

Every battery I've had leak was made by Duracell. Despite all their
advertising, I've found them to be the most destructive (other than
those really crappy cheapies that come with the hardware).

This was a 'GP Alkaline' which came with the mouse.

Do you think people really can tell exactly what role the various
startup programs/services play in the swamp that is Windows 10?

Yep, they can. Looking at the path for the executable can indicate what
it is for. Right-clicking on the file and looking at Properties -
Details can sometimes reveal who made the software and what it is for.
Sometimes you have to search the web.

Well, I don't have to go to those lengths. Somehow the problem now
seems to have gone away.

The first thing I did this morning was look for Logitech drivers. All
I can say is that their site is horrible. Eventually I found what
appeared to possibly be what I wanted and I down loaded Setpoint,
Connectivity and Unifying.

I ran Unifying, which loaded, popped up and looked at me for about
half a second, and then disappeared without any comment.

Next was Connectivity. This offered me the chance to re-pair the
keyboard with the dongle but confirmed that it was already working
correctly.

I then ran Setpoint which appeared as though it might be driver.

After all this I intended to restart Dell to see if the keyboard
problem had improved. However as I was still backing out from layers
of Logitech, my screen turned green (my choice) and a familiar "Do not
shut down your machine etc" apeared. Next thing I knew I was in about
7 minutes worth of update and restart. And when I went to log in, the
machine responded to my typing immediately.

While the change could have been due to the Logitech software, I think
it is much more likely that it was a bug in the version of 1903 I had
downloaded.