因此,我今天注意到设备管理器中的一个未知设备。当我检查其属性时,该设备看起来非常活跃。 时间线看起来像这样:
2018.08.03 07:23.45 Device install requested
2018.08.03 07.24.32 Device migrated
2018.08.03 07.24.32 Device configured (wvms_mp.inf)
2018.08.03 07.24.33 Device started (VMSNPXYMP)
2018.08.03 07.34.15 Device deleted
2018.08.03 07.34.32 Device configured (wvms_mp.inf)
2018.08.03 07:34.45 Device started (VMSNPXYMP)
2018.08.30 08.44.31 Device deleted
2018.08.30 08.44.32 Device configured (wvms_mp.inf)
2018.08.30 08.44.32 Device started (VMSNPXYMP)
2018.09.03 06.18.32 Device deleted
2018.09.03 06.18.32 Device configured (wvms_mp.inf)
2018.09.03 06.18.32 Device started (VMSNPXYMP)
2018.09.04 06.18.32 Device deleted
2018.09.04 06.18.32 Device configured (wvms_mp.inf)
2018.09.04 06.18.32 Device started (VMSNPXYMP)
2018.09.17 06.18.32 Device deleted
2018.09.17 06.18.32 Device configured (wvms_mp.inf)
2018.09.17 06.18.32 Device started (VMSNPXYMP)
2018.09.17 07.24.32 Device configured (null)
2018.09.23 07.24.32 Device configured (null)
2018.09.24 07.24.32 Device configured (null)
2018.10.01 07.24.32 Device configured (null)
2018.10.05 07.24.32 Device configured (null)
2018.10.06 07.24.32 Device configured (null)
2018.10.11 07.24.32 Device configured (null)
2018.10.15 07.24.32 Device configured (null)
2018.10.16 07.24.32 Device configured (null)
2018.10.18 07.24.32 Device configured (null)
2018.10.19 07.24.32 Device configured (null)
2018.10.29 07.24.32 Device configured (null)
我不知道这种活动。但我搜索了wvms_mp.inf文件,它似乎正在存储有关网络的一些设置。
以下是示例:
; IPv4 IP Checksum offload
HKR, Ndi\Params\*IPChecksumOffloadIPv4, ParamDesc, 0,
%Ip4IpChecksum%
HKR, Ndi\Params\*IPChecksumOffloadIPv4, type, 0, "enum"
HKR, Ndi\Params\*IPChecksumOffloadIPv4, default, 0, "3"
HKR, Ndi\Params\*IPChecksumOffloadIPv4\Enum, "0", 0,
%CmnDisabled%
HKR, Ndi\Params\*IPChecksumOffloadIPv4\Enum, "1", 0,
%OflEnabledTx%
HKR, Ndi\Params\*IPChecksumOffloadIPv4\Enum, "2", 0,
%OflEnabledRx%
HKR, Ndi\Params\*IPChecksumOffloadIPv4\Enum, "3", 0,
%OflEnabledTxRx%
; IPv4 TCP Checksum offload
HKR, Ndi\Params\*TCPChecksumOffloadIPv4, ParamDesc, 0,
%Ip4TcpChecksum%
HKR, Ndi\Params\*TCPChecksumOffloadIPv4, type, 0, "enum"
HKR, Ndi\Params\*TCPChecksumOffloadIPv4, default, 0, "3"
HKR, Ndi\Params\*TCPChecksumOffloadIPv4\Enum, "0", 0,
%CmnDisabled%
HKR, Ndi\Params\*TCPChecksumOffloadIPv4\Enum, "1", 0,
%OflEnabledTx%
HKR, Ndi\Params\*TCPChecksumOffloadIPv4\Enum, "2", 0,
%OflEnabledRx%
HKR, Ndi\Params\*TCPChecksumOffloadIPv4\Enum, "3", 0,
%OflEnabledTxRx%
; IPv6 TCP Checksum offload
HKR, Ndi\Params\*TCPChecksumOffloadIPv6, ParamDesc, 0,
%Ip6TcpChecksum%
HKR, Ndi\Params\*TCPChecksumOffloadIPv6, type, 0, "enum"
HKR, Ndi\Params\*TCPChecksumOffloadIPv6, default, 0, "3"
HKR, Ndi\Params\*TCPChecksumOffloadIPv6\Enum, "0", 0,
%CmnDisabled%
HKR, Ndi\Params\*TCPChecksumOffloadIPv6\Enum, "1", 0,
%OflEnabledTx%
HKR, Ndi\Params\*TCPChecksumOffloadIPv6\Enum, "2", 0,
%OflEnabledRx%
HKR, Ndi\Params\*TCPChecksumOffloadIPv6\Enum, "3", 0,
%OflEnabledTxRx%
; IPv4 UDP Checksum offload
HKR, Ndi\Params\*UDPChecksumOffloadIPv4, ParamDesc, 0,
%Ip4UdpChecksum%
HKR, Ndi\Params\*UDPChecksumOffloadIPv4, type, 0, "enum"
HKR, Ndi\Params\*UDPChecksumOffloadIPv4, default, 0, "3"
HKR, Ndi\Params\*UDPChecksumOffloadIPv4\Enum, "0", 0,
%CmnDisabled%
HKR, Ndi\Params\*UDPChecksumOffloadIPv4\Enum, "1", 0,
%OflEnabledTx%
HKR, Ndi\Params\*UDPChecksumOffloadIPv4\Enum, "2", 0,
%OflEnabledRx%
HKR, Ndi\Params\*UDPChecksumOffloadIPv4\Enum, "3", 0,
%OflEnabledTxRx%
; IPv6 UDP Checksum offload
HKR, Ndi\Params\*UDPChecksumOffloadIPv6, ParamDesc, 0,
%Ip6UdpChecksum%
HKR, Ndi\Params\*UDPChecksumOffloadIPv6, type, 0, "enum"
HKR, Ndi\Params\*UDPChecksumOffloadIPv6, default, 0, "3"
HKR, Ndi\Params\*UDPChecksumOffloadIPv6\Enum, "0", 0,
%CmnDisabled%
HKR, Ndi\Params\*UDPChecksumOffloadIPv6\Enum, "1", 0,
%OflEnabledTx%
HKR, Ndi\Params\*UDPChecksumOffloadIPv6\Enum, "2", 0,
%OflEnabledRx%
HKR, Ndi\Params\*UDPChecksumOffloadIPv6\Enum, "3", 0,
%OflEnabledTxRx%
; IPv4 TCP Segmentation offload
HKR, Ndi\Params\*LsoV2IPv4, ParamDesc, 0, %Ip4TcpLsoV2%
HKR, Ndi\Params\*LsoV2IPv4, type, 0, "enum"
HKR, Ndi\Params\*LsoV2IPv4, default, 0, "1"
HKR, Ndi\Params\*LsoV2IPv4\Enum, "0", 0, %CmnDisabled%
HKR, Ndi\Params\*LsoV2IPv4\Enum, "1", 0, %CmnEnabled%
; IPv6 TCP Segmentation offload
HKR, Ndi\Params\*LsoV2IPv6, ParamDesc, 0, %Ip6TcpLsoV2%
HKR, Ndi\Params\*LsoV2IPv6, type, 0, "enum"
HKR, Ndi\Params\*LsoV2IPv6, default, 0, "1"
HKR, Ndi\Params\*LsoV2IPv6\Enum, "0", 0, %CmnDisabled%
HKR, Ndi\Params\*LsoV2IPv6\Enum, "1", 0, %CmnEnabled%
当某些未知的事物更改了与某些网络设置有关的设置时,我会感到怀疑。有人可以告诉我这是否是正常活动吗?我可以读哪本书来了解这一点?
答案 0 :(得分:1)
我也遇到了与设备管理器记录的相似日期完全相同的问题。由于某些未知原因,Hyper-V虚拟以太网适配器在第一次删除事件发生之日或前后被损坏。您会注意到,“ Hyper-V虚拟以太网适配器”已从设备管理器中的网络适配器列表中消失。
如果不是最初的故障,攻击或错误,我对症状的解决方案是卸载未知设备,然后转到控制面板“程序和功能”,然后关闭“打开或关闭Windows功能”中的所有Hyper-V选项。 ”,然后重新启动,然后如果需要或可能需要Hyper-V,请返回“打开或关闭Windows功能”,然后将重新构建“ Hyper-V虚拟以太网适配器”,并重新出现在设备管理器和该未知设备中将消失(目前)。当然,将来它可能会再次出现,因为我们仅解决了症状,而不是虚拟以太网适配器损坏的错误/攻击或实际原因。修复的虚拟设备使用与未知设备完全相同的inf文件。我希望能够回答足够多的问题,以便再次使设备管理器外观整洁:-)
答案 1 :(得分:-1)
不确定,但我相信它是Hyper-V虚拟交换机管理器的驱动程序。