Unknown Devices

[StuartR]

After I upgraded my HP Elitebook 8460p laptop to Windows 10 it shows two unknown devices. I haven't yet noticed what isn't working, so I'm not sure whether to ignore this or panic.

Any thoughts?

[stuck]

A Google search on 'unknown device root net 0002' finds this as the second hit:
https://h30434.www3.hp.com/t5/Notebook- ... -p/5305619
Does that help?

Ken

[StuartR]

Ken,

That was VERY helpful. I hadn't remembered to look at the HArdware Ids on the Details tab of the device properties. One of the unknown devices is my HP Printer, which seems to be working perfectly. The other is the SoftEtherVPN driver for my VPN software, which is also working fine!

Hmmm

[viking33]

I wonder if these are "Ghost Devices"?
This still works in Win7,8,10.
--------------------------------
set devmgr_
How to remove unused devices in Device Manager.
--------------------------------------------------------------------
Go to command prompt. (start>run, type cmd then enter)
To show really hidden devices and troubleshoot ghost devices:

At command prompt type:

"set devmgr_show_nonpresent_devices=1. Enter.
Change folder towindows\system32. (ex. C:windows\system32)

Type" start devmgmt.msc, press enter.
In Device manager select "view" and click "show hidden devices".
Now all devices should show up. Non-present devices are seen dimmer.
And can be deleted.

[StuartR]

They're not "ghost" devices Bob, as I can see them in the normal device manager view. I am reinstalling the HP and VPN software, then I'll delete the devices and reboot...

[StuartR]

I deinstalled SoftEther VPN and the HP Printer software. Then deleted both unknown devices and rebooted the laptop. I reinstalled all the software and allowed the laptop to reboot a couple of times during the process. The devices haven't reappeared and all now seems well.

Thanks for the interest, and the pointers.

[stuck]

I was going to suggest, "If it ain't broke, don't fix it" but it looks like you've already fixed it

Ken

[StuartR]

I took a full image backup before upgrading to Windows 10 Ken, and another one straight after, so there was very little risk here.