Any other takers?
I suspect the printer is being picked up by Windows in the startup process and is being identified as an 'other device.' It's probably also causing a small series of error messages in the event viewer i.e. an IP address not being provided in the allowed timeframe (which the printer is not able to provide through it's wireless signal) and the other 3 error processes associated with that failure.
When the machine boots it then tries to identify the source of the problem, which is the 'other device,' the HP printer. And then Windows unsuccessfully tries to install software under 'other devices' where printers don't belong and fails, leaving a trail of HP printers in it's wake under other devices.
Surely there is a simple cure for this annoying (and currently only) issue I have?
