I notice that BTIDisabledBySystemPolicy on all of these equals True. This is also False on all of the unaffected ones, so this makes it a little more clear. AFAIK, this supposedly means the required Registry settings (in the MemoryManagement key) are not present. If anyone knows differently, please inform me. The KB article seems to suggest this but is a bit vague.
Those Registry keys are present and the systems have since been rebooted, but possibly another reboot would resolve it. On Wed, Feb 7, 2018 at 1:43 PM, Charles F Sullivan < [email protected]> wrote: > We've patched our VMware hosts (ESXi 6.0) using the "HyperVisor Specific" > patch (ESXi600-201711101-SG). The Windows guests have the appropriate > January CU installed along with the prerequisite Reg keys. > > On about 10 of 150 VMs, *KVAShadowWindowsSupportEnabled* equals False. > Everything else on all VMs looks as you would expect when no microcode > patch has been installed on the hosts. > > The explanation for that result says "....If it is False, either Windows > operating system support is not present, or the feature has not been > enabled." Does anyone know how to resolve this? On all of the other > guests it seems as though the host patch resolved it. The host must not be > the issue because on a given host, a small number of VMs are affected. The > guest OS version varies on these few affected guests as well. > > Any ideas? > -- > > Charlie Sullivan > > Sr. Windows Systems Administrator > > Boston College > > 197 Foster St. Room 367 > <https://maps.google.com/?q=197+Foster+St.+Room+367%0D+%0D+Brighton,+MA+02135%0D+%0D+617&entry=gmail&source=g> > > Brighton, MA 02135 > <https://maps.google.com/?q=197+Foster+St.+Room+367%0D+%0D+Brighton,+MA+02135%0D+%0D+617&entry=gmail&source=g> > > 617-552-4318 <(617)%20552-4318> > -- Charlie Sullivan Sr. Windows Systems Administrator Boston College 197 Foster St. Room 367 Brighton, MA 02135 617-552-4318
