No matter what I did with the VM version 10-11, adding several lines to the vmx file, the boot from the iso always stopped at around 60% of the progress bar, and the last lines in vmware.log where: I installed the unlocker-2.0.8 and tried to install El Capitan. I'm not sure I can post here a direct link, yet googling for it should provide a direct link effortless.įirst installation was esxi-5.0 and then some updates/upgrades till version esxi-6.0u2 If it's in a Windows insider build, I assume it'll make it through the regular builds, sooner or later so it's going to be necessary.įor the record, I've used delcert tool (from XDA Developper forum) to strip digital signature from DLL and EXE. So, IMHO, the next flavor of unlocker should also deal with the digital signature of the patched files, and strip them so the patched binary files don't appear as forged from the OS point of view. keyboard and mouse input are back in VM's. So, I took all the individual files that were modified by the unlocker, and stripped the digital signature (so they appear as not signed), and it worked.

It can be well understood as a security feature preventing any forged executable from receiving input of a typed password or so. And it seems that if an executable with a damaged signature is launched, the windows build I have isolate the process from any keyboard or mouse input. Patching the binary files destroy the validity of their digital signature. I have finally identified the culprit, which is probably a new security scheme recently enforced by Windows.

CPU-Z 2.08 for mac instal