I'm not sure I understand exactly what is going on, but from what I can tell you are having WMIC errors? As much as I test my releases, they are still not up to MS's standards and do not have the same error control handling. It is possible that a single install did not go well and that you might need to re-install. 99% of the tests I performed were on vms but even so of the failures I've experienced, some of those did fix themselves just by re-installing. I've had that issue on both the normal MS releases and my AIO ones so I don't know if it happens more often on custom images. Perhaps there is some kind of issue with the backend dism stuff that applies the image and it doesn't initialize correctly on a rare occasion. If the issue persists, try making sure there is no hardware overclocking or anything that could be causing conflicts.
It could purely be one of the quirks of windows. A particular situation in that x + y not equal z as one element not quite right. It could just be vm software that it not like for some reason.
I might try to get an alternative installation source of LTSB 2015. Good luck for me, obtaining that old stuff. @murphy78 That's why I have done multiple test installs, the first one I had the UNKNOWN result on is a VM of the infamous "Windows 10 Enterprise LTSB 2015 N Privacy" image from you-know-who. Edit: Downloaded original LTSB 2015 installation source and installed. It is showing absolutely the same UNKNOWN shenanigans. Chalk it off to some Threshold 1 bug. Generic.exe still works, so, it must be doing something different.
Have uploaded QT Test2 (T2) to betatesting area, now with another method to parse the SLIC name IF it is returned as 'UnKnown' or not detected via WMI methods... May take a few seconds longer when it parsing but not much more than that and this other way only is used when the other WMI ways not find the SLIC name/brand. Well i hope it works as my laptop not got a slic and the routine gets skipped.
It must be something in the old kernel that may not of been written in at that time and like a lot of things it was added in, or bodged depending on how you see it...
I did think of the /c: parameter But it may not make much difference as it seems using acpidump still may not show the slic.
Th2 was my first long term w10, then i skipped rs1, updated to rs2 and was still on that until i built my new pc this year. I skipped rs3 to 5 even 18xx, 19xx ones
I will remove the added code and the acpidump.exe file as it not needed now. As it only seems to affect that old os.
I wonder if this is a common error with that build. I'm not suggesting that it happens on all hardware or something, but perhaps it happens often enough that they might have issued some kind of update to address the issue. I wonder.
It may seem uninspiring that a simple bios check via wmi gives that odd result but who knows what other wmi calls did the same because a programmer not wrote some code. Ms may at some point found out and fixed it - silently as they sometimes have and no documentation.
i had looked into the HVCI and because of the many factors to check to prevent BSOD's etc i don't think i could safely enable this via a option , or set of options to control if enabled, or not.