I hope you have found this article informative. Reg add “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization” /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d “1.0” /f Reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management” /v FeatureSettingsOverride /t REG_DWORD /d 0 /f HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\MinVmVersionForCpuBasedMitigationsīefore running the below commands, the values were 3 and 1 respectively. Since the file KernelBase.dll can be accessed by more than one program at a time, and the KernelBase. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\FeatureSettingsOverride The solution was to change 2 registry keys: I uninstalled all updates in January and February on the first server, but this made no difference.
#Event id 1000 kernelbase dll windows#
This led me to a topic referring to an issue with January 2018 windows updates. 18895, time stamp: 0x5a4b1cf7įaulting application path: C:\Windows\System32\vmwp.exeįaulting module path: C:\Windows\system32\KERNELBASE.dll 18895, time stamp: 0x5a4b1c19įaulting module name: KERNELBASE.dll, version. 18015, time stamp: 0x50b8479b Exception code: 0xe0434352 Fault offset: 0x0000000000009e5d Faulting process id: 0x1160 Faulting application start time: 0x01ce6dccc2c8252e Faulting application path: C:\Program Files\AppFabric 1.1 for Windows Server\DistributedCacheService. I eventually checked the application log and found this event:įaulting application name: vmwp.exe, version. Faulting module name: KERNELBASE.dll, version. In the Filter Current Log dialog box, enter 1000 (as shown in the following screenshot), and then select OK. In the Actions pane, select Filter Current Log. In the details pane, select Application under Windows Logs. My first stop was the Hyper-V VMMS log which contained the same error. To review the Application log, follow these steps: In Control Panel, open the Administrative Tools item. When attempting to start the virtual machine it would get to starting…4% and then give a pop-up error message “ failed to initialize”. I had a customer that I worked with that was not able to start any VM (virtual machine) across 3 Hyper-V servers he had deployed in his environment. I ran into an issue that took me quite a bit of time to resolve that I wanted to share with everyone.