Closed vinc2019 closed 4 years ago
Thanks for the bug report. A few questions:
Yes, that is exactly what I mean, virtual machines running inside a host machine We have different virtual clients and servers in our Hyper-V environment. And also on my W10 Machine with a test Hyper-V environment, it does not work.
I found out that I do not have the problem with virtual W7 machines. It only appears on W10 and Server 2016.
@velaar Does it make sense to support virtual machines? This was originally written as a utility to keep track of hardware inventory, not VMs and containers.
I think you're right. I only use the VM computer for testing. The problem also appears on physical devices with the Windows 10 not on Windows 7. Can it be that it runs only with certain .Net versions? Is there a possibility to activate a deepening debugging? Or better said, a possibility to see more logs? I can't solve the problem, it is frustrating.
@velaar Does it make sense to support virtual machines? This was originally written as a utility to keep track of hardware inventory, not VMs and containers.
VM is such a niche case. I think it can be achieved with a settings switch for testing purposes. However there are so many different VMs around and Windows WMI reacts in different ways to what they emulate. I think shouldn't implement this support as there is little practical value.
Close the case?
Agreed. Given that this is a hardware inventory tool, I'm not sure it makes sense to include VMs.
Unfortunately, I get all the virtual devices no matter whether PC or server the following known message:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at Marksman.Sentry.RunWMI() at Marksman.Marksman.Main(String[] args)
Does anyone have the same problem with the virtual devices and does anyone know a solution? Thank you very much for your help.