Unknown devices on Windows 10
I noticed that I have unknown devices in my Device Manager on Windows 10 machine:
Where do they appear from? What to do with them?
EDIT1:
Device by connection view:
Device instance path and hardware ids:
ROOT\NET\0001 ptun0901
ROOT\NET\0002 ptun0901
ROOT\NET\0003 ptun0901
...
EDIT2:
My mainboard is Gigabyte Z390 AORUS PRO. Installed the following from CD:
Intel(R) Management Engine Software(300 Series) Install Driver
Intel(R) HECI Device Driver You MUST install this driver to ensure proper system operation.
Version:1846.12.0.1177
Size:69.40MB
INF Update Utility(300 Series) Install Driver
For Intel 300 Series Chipset
Version:10.1.17968.8131
Size:4.48MB
Intel(R) HD Graphics Driver Install Driver
Intel(R) Iris(R) Plus Graphics, Intel(R) Iris(R) Pro Graphics, Intel(R) HD Graphics and Intel(R) UHD Graphics on 6th Gen/7th Gen/8th Gen/Apollo Lake/Gemini Lake
Version:25.20.100.6617
Size:1025.06MB
Intel Rapid Storage Technology driver Install Driver
Intel driver for AHCI and RAID mode.
Version:17.2.6.1027
Size:21.22MB
Realtek High Definition Audio Driver(300 SER) Install Driver
Realtek High Definition Audio Driver
Version:6.0.1.8586
Size:62.13MB
Intel(R) Network Connections Software Install Driver
This release includes software and drivers for Intel(R) PRO/100
Version:23.5
Size:252.77MB
Intel Serial IO Driver Install Driver
Fro Intel Chepset Serial IO device on Win 10
Version:30.100.1902.3
Size:2.29MB
EDIT3:
I uninstalled all unknown devices and will try to reboot:
but unknown device did not disappear.
As per your information from the hardware IDs, the many “Unknown device” instances with the problems (yellow triangle) are TAP-Win32 virtual network interfaces. They are often using with VPN software like OpenVPN. You indicate you removed some VPN software lately. It apparently only removed the TAP-Win32 driver without removing the virtual network interfaces.
You already succeeded in removing all the broken virtual network interfaces.
The remaining device, “SMS/MMS”, is not broken and working as designed. The driver developer just neglected to define its device category, so it ended up in “Other devices”. This is not a problem in any way. If you want further information on this device, you should check its hardware IDs like before as well as the associated drivers on the “Driver” property page. Others on the internet associate this device with a paired Bluetooth phone.