Logitech USB wireless KB/Mouse do not operate in Win XP

I dual boot a Win 7 and Win XP system and use the same
USB wireless keyboard and mouse for each (Logitech K800
keyboard and M510 Logitech mouse). Both keyboard and
mouse worked well on either system until I ran Advanced
System Repair Pro on each. Now, neither device works on
the Win XP system.

On both the Win 7/Win XP systems, the receivers show up
in Device Manager-Universal Serial Bus Controllers section
as USB composite devices; Win 7 driver version is
6.1.7601.24138 - Win XP driver version is 5.1.2600.0.

In Win 7 device manager, there are entries under Keyboard
and Mouse indicating 'HID keyboard device' and 'HID compliant
mouse'. Each has their own respective driver.

In win XP device manager, there are no such entries.
For some reason, there is no connection between the receiving
units and their respective input devices in Win XP.

At first, I thought that somehow the 2.4GHz connection had
turned off, but there is no reconnect button on either the
keyboard or mouse. Since the keyboard and mouse are not being
recognized in Win XP, it could be that the mouse and keyboard
drivers are not active although they exist on the Win XP
system in system32/drivers as kbdclass.sys/kbdhid.sys and
mouclass.sys/mouhid.sys. On bootup, there is no recognition
of new hardware and I cannot seem to install them under
'Add new hardware' in control panel. (yes, I have to start
Win XP with a ps/2 mouse and wired USB keyboard).

Can anyone help?

Why in the name of GOD would you ever run "Advanced
System Repair Pro" ?

Exactly!!! Too soon olde, too late schmart!!

NO! Seriously, if it doesn't have an UNDO , then your F'edup.

I tend to overcomplicate situations like this; the solution turned out to be rather simple. Simply updated the mouse and
keyboard drivers in Device Manager by selecting 'No' when asked if I wanted to use the Internet to find a driver. It only
looked on my hard drive and found the drivers already there. Install was automatic and the problem solved. Glad I wasn't
truly F'edup.

Did try to do a system restore as ASR supposedly created a restore point, but found System Restore turned off. Glad I
didn't need it.