I was able to solve the issue by uninstalling KB 4549949 (and adding it to the list of excluded updates). I can now run Android emulators and write code all day. And all night. Life is beautiful again.
--Ravi
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
There is an issue with Android Emulator with Visual Studio 2019 as well as Android Studio, that whenever trying to open the emulator the windows crashes and enters BSOD (Status : “clock watchdog timeout”).
This issue has started after a patch update for windows (KB4554354 (OS Build 17763.1132)).
Troubleshooting done so far,
Nothing works and we are out of help from any source.
We are sure that the patch update was the issue causing the problem.
Thanks,
Prabhakaran K
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I was able to solve the issue by uninstalling KB 4549949 (and adding it to the list of excluded updates). I can now run Android emulators and write code all day. And all night. Life is beautiful again.
--Ravi
This problem also occurs with the emulators that are part of Android Studio. I'm using the latest version of AStudio (3.6.3) and encounter the BSOD when starting an emulator from the AVD. Shortly after the emulator starts, my machine BSODs. The entry in the event log is:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DAYFORCE\rbhavnani SID (S-1-5-21-487255477-1631527022-351744442-1728) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
I'm running Win 10 Enterprise, Intel Xeon CPU E5-1560 v4, 24GB RAM.
I also use Xamarin (on VS 2017) to develop native Android apps, but I believe the issue is unrelated to Xamarin or Visual Studio, as it's easy to repro in an isolated manner by simply starting an emulator from the AVD.
Ravi B
I followed my <Event Viewer>.. found following Event sources as specified under “Hyper-V-Hypervisor”.
" The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and
the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot. "
Hence as suggested applied "bcdedit /set hypervisorschedulertype core" through command prompt and reboot.
After this windows crashing stopped at last and Emulator started working but looked slow.
using [Developer PowerShell] of Visual Studio Professional. Run Powershell as Administrator.
PS C:\Windows\system32>
Run the command: Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
************************************************************************
If it is enabled, you'll see the answer like this:
FeatureName : Microsoft-Hyper-V
DisplayName : Hyper-V Platform
Description : Provides the services that you can use to create and manage virtual machines and their resources.
RestartRequired : Possible
State : Enabled
Hi Kyle,
I have tried uninstalling the patch(KB4554354) and emulator has started working from Monday(20-Apr-2020).
But unfortunately the issue has started again from today morning after the couple of windows patches (KB4549949 & KB4549947) installed (automatic updates) yesterday night(21-Apr-2020).
The issue is there for both my teammate and me.
Thanks in advance for any help to resolve this issue.
Hi thanks for reaching out! I'm Kyle M. a Microsoft Independent Advisor and a Microsoft community member like you. I'm glad to help you
You can rollback and uninstall your recent update follow these Steps:
Let me know if you need anything else! Keep safe!
Regards,
Kyle M.