diff --git a/android/Vagrant.README.md b/android/Vagrant.README.md
index 3b6c3372a4..b48edf3fe8 100644
--- a/android/Vagrant.README.md
+++ b/android/Vagrant.README.md
@@ -4,6 +4,7 @@ Provide a turn-key VM for Android development
 
 ## Requirements
 
+### On Linux, MacOS or Windows with VirtualBox
 * [Vagrant](https://www.vagrantup.com/downloads.html)
 * [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 * [VirtualBox Extension Pack](https://www.virtualbox.org/wiki/Downloads) for USB 3.0 support.
@@ -13,7 +14,15 @@ Provide a turn-key VM for Android development
   * 4 GB RAM (2 used by VM)
 * Download volume (once): ~3.5 GB
 
-## HOWTO
+### On Windows with Hyper-V
+* [Hyper-V](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
+* Host:
+  * 4 CPU cores (2 used by VM)
+  * ~18 GB disk space
+  * 4 GB RAM (2 used by VM)
+* Download volume (once): ~3.5 GB
+
+### HOWTO
 
 1. On your host: open a terminal
    1. Clone the [BOINC repo](https://github.com/BOINC/boinc) and `cd <BOINC_REPO>/android` or just dowload the [Vagrantfile from GitHub](https://github.com/BOINC/boinc/blob/master/android/Vagrantfile)
@@ -35,7 +44,8 @@ Provide a turn-key VM for Android development
 1. Hook up your Android device via USB (and remember to attach it to VirtualBox)
 1. Happy hacking :-)
 
-## Known limitations
+### Known limitations
 
 * The Android Virtual Device Manager might not work properly as it needs virtualization
   which isn't possible within a virtual machine (at least not using VirtualBox).
+* On Windows it seems the VirtualBox manage GPU acceleration a little better on Ubuntu 18.04, than Hyper-V, despite the fact that Windows added [Enhanced Session Mode to Ubuntu 18.04](https://blogs.technet.microsoft.com/virtualization/2018/02/28/sneak-peek-taking-a-spin-with-enhanced-linux-vms/).