Bibleworks 10 not working after windows update may 2019
![bibleworks 10 not working after windows update may 2019 bibleworks 10 not working after windows update may 2019](https://getin-topc.com/simgs/bibleworks-8/bibleworks-8-offline-installer-download-getintopc.com_.jpg)
It is very strange to me that CFG blocked C:\WINDOWS\System32\vmcompute.exe almostĮxclusively I would think that heuristics would except and exclude any Microsoft signed and originated process, even/especially if it performs with hypervisor-required privileges but perhaps they are being extra cautious or the newly updated Windows Security Thanks, this fixed the problem! I was 95% of the way there.I saw in the logs a bunch of MSR Access Violations that *something* was stopping the Hyper-V process instructions.
![bibleworks 10 not working after windows update may 2019 bibleworks 10 not working after windows update may 2019](https://exegeticaltools.com/wp-content/uploads/2015/07/Screenshot_5.png)
I had the same problem and managed to solve it by doing the following.ģ, Click "Exploit protection settings" at the bottomĥ, Locate "C:\WINDOWS\System32\vmcompute.exe" in the list and expand itħ, Scroll down to "Code flow guard (CFG)" and uncheck "Override system settings"Ĩ, Start vmcompute from powershell "net start vmcompute" Did anybody else run into this problem and is there a repeatable, reliable, and robust way to fix this? What causes it? I use Hyper-V and Docker forĭevelopment purposes and I do enjoy the latest update to Windows 10.
BIBLEWORKS 10 NOT WORKING AFTER WINDOWS UPDATE MAY 2019 INSTALL
I am unsure exactly what is going on as I have cleaned the Windows 10 update cache and tried everything to bootstrap a working install of Hyper-V short of refreshing the entire Windows 10 install (which I am not going to do). The error when using Hyper-V Manager is to check that exact service because itĬannot access any objects through it. When I try to enable them manually, the Virtua Machine Management Service starts for a bit, then silently stops. Looking at the logs, none of the required services are running. Absolutely none of these things have had any impact on whether or not it runs. Additionally, I have done the MOFCOMP recompile and eliminated extra adapters I have tried just about everything I can think of to enable Hyper-V including installing/reinstalling it multiple times from both the Windows Features app, PowerShell, and DISM. The system is more than capable of running Hyper-V and it exceeds the minimum requirements including virtualization on the processors and BIOS. Previously, Hyper-V was perfectly functional and I used it to run Docker Engine and develop on this system. I recently updated my Windows 10 system to the 1809 October Update everything appears to work well and even a bit faster.