Go to ...

RSS Feed

September 18, 2020

Inexplicable, weird connection when testing Android emulators – Hypervisor, Boot records and Outlook

My Nokia Lumia 925 with Windows Phone 8.1 is the best, most reliable smart phone I have ever owned. Unfortunately, now I must find a replacement: Windows Phone and Windows Mobile are dying. In Finland, we have an old saying “I do not need manure, I am not a farmer.” In my case, this equates to “an iPhone is out of the question“. Thus, an Android device is my only alternative.

Trying to test how the Microsoft Launcher and apps work on Android, I installed a few Android emulators on my Windows 10 Insider Preview laptop. The problem is, most Android emulators like BlueStacks only work when the Hyper-V hypervisor is turned off. For a Hyper-V enthusiast, that is a game changer. Yet, I decided to test it anyway. I created a boot menu entry to start Windows 10 without a Hypervisor (see my tutorial on Ten Forums), just so I could run Android emulators.

BlueStacks is pretty good, but slow. Booting it up can take a few minutes. I’m sorry to report that it is full of ads, and you can’t install the latest Android versions on it. Anyway, I first went with BlueStacks, in my opinion the best of all Android emulators. I was (almost) satisfied, I could run an Android emulator, and test it. How it looks, how it feels, how do my Microsoft Office, OneDrive and other important apps (IMO) work on it.

Luckily, I found a solution to install the latest Android releases to a Hyper-V virtual machine. No more emulators, just pure Android. That’s a good topic for another post. In this post, I just want to tell you what minor issues the two boot entries had — namely, W10 with and without Hypervisor.

First, when I boot to W10 without Hypervisor, then restart to W10 with Hypervisor (Hyper-V enabled), the boot entry for W10 without Hypervisor will always be deleted. I must recreate it every time. Next, Office Outlook always freezes in “Loading Profile”, and cannot open.

This is strange. To summarize the preceding points: I have Hypervisor (and Hyper-V) enabled. When I need to boot to the same Windows 10 but without Hypervisor, to be able to run VMware, VirtualBox and Android emulators, it works perfectly. But, at the next boot, the option to boot to Windows 10 without Hypervisor is removed from the boot menu (!). In addition, Outlook always crashes, and freezes during the “Loading profile” stage.

This is not a big problem. I can work around both issues with some simple steps. I just need to add a new boot menu entry for the main OS without Hypervisor, and delete all *.ost and *.nst profile files in %localappdata%\Microsoft\Outlook\ folder. All Outlook mail profiles will be downloaded from the cloud when Outlook is launched next time, issue resolved.

Click to open enlarged in a new tab.

Anyway, that’s just a workaround. Testing some more, I finally found a way to install the latest Android operating systems on a Hyper-V virtual machine. No more rebooting to W10 without Hypervisor needed, all these minor issues gone.

Instructions to setup an Android virtual machine here: Hyper-V: Android Pie and Microsoft Launcher on a VM


Author: Kari Finn

A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site TenForums.com.

One Response “Inexplicable, weird connection when testing Android emulators – Hypervisor, Boot records and Outlook”

  1. Toni Fasth
    November 24, 2019 at 11:07

    It is very strange that your “hypervisor off” boot entry disappears for you after a reboot. For me it is persisting without any issues. I have 2 entries, one with Hypervisor on and one with off and a 2s delay to display the entries before my system boots into the default, which is Hypervisor on.

Leave a Reply

More Stories From 20H1