KABY LAKE VMWARE FUSION 10 UPDATE
After installing the April Security only update KB4015546, no more updates can be installed via Windows Update or. So far the results are consistent with MrBrian’s. NET security update KB4014985), same as (4).
KABY LAKE VMWARE FUSION 10 INSTALL
(5) I tried to install KB4014661 (IE11 Cumulative Security Update) or KB4014573 (.NET 3.5 security update, part of the. (4) I then attempted to install KB4015549 (April Security Quality Rollup) and the install failed with the error “Installer encountered an error 0x80240037”. The message “Unsupported Hardware” immediately appeared and Windows Update displayed the error “Code 80240037”. (3) After the reboot, I ran Windows Update and attempted to check for updates. (2) After the virtual machine started and with Windows Update set to Never Check for Updates, I installed KB4015546 (April Security-only update) and rebooted the virtual machine. The last line is needed in case the virtual machine fails to start. VMware required that the data be converted to binary from hexadecimal. The data was obtained from MrBrian’s supplied data, specifically the line “–cpuidset 00000001 000806e9 00100800 7ffafbbf bfebfbff”. My host CPU is Core i7 6800K.įor interested parties, here is what I have done so far: I use VMware Workstation 10.0.5 and a Windows 7 virtual machine (patched to September 2016) created before. I took the CPU data supplied by MrBrian (which is in fact the CPUID of a Kaby Lake mobile CPU) and converted them for use in VMware Workstation. I am pleased to report that I have successfully recreated (part of) the results of the test. Apparently, people choosing to have automatic updates OFF was intolerable for Microsoft, so they’ve set it up so that now the few people who ever changed the update settings will just disable the service, which makes it even less likely they’ll get future updates than if they’d just turned them off (particularly if they would have chosen the “notify but don’t install” option). In Microsoft’s zeal to assert complete control of people’s systems, they’re training a whole new generation of Windows users to do things like disable the Windows Update service and otherwise hack the system to get back the control that MS took away. Perhaps someone will even create a “disable CPU checking” service that works like the “disable theme signature enforcement” one. This is a tacked-on little change, and it should be relatively easy for someone to get rid of. I have little doubt that the people who brought us cracks for the Windows theme signature enforcement and other such things will find a way around this pretty quickly. Next month, do the same, and the month after, and the month after… Since the rollups are cumulative, you’d have reinstalled all of the fixes that were in last month’s rollup that you just deepsixed when you installed the new patch.
KABY LAKE VMWARE FUSION 10 PC
So what you’d have to do is uninstall the most recent rollup already installed on the PC (which should normally be the one from the prior month), then allow Windows Update to find and install the new one. This is the same method Radosuaf suggested, if I am correct.
I did the same tests as, but this time testing KB4015549 (April 2017 monthly rollup) instead of KB4015546 (April 2017 security-only update).
0 kommentar(er)
