#This command shows the individual rules and the network connection profiles that are explicitly enabled and disabled for Network Discovery.
Get-NetFirewallRule -DisplayGroup 'Network Discovery'|select Name,DisplayName,Enabled,Profile|ft -a
#Enable Network Discovery for Private and Domain network profiles
#Enable the Network Discovery service for the Private and Domain network profiles by applying the preconfigured Windows Firewall group rule called Network Discoveryby typing this:
#Open Elevated PowerShell Prompt Here From Right-Click Context Menu Instead Of Command Prompt Here As Administrator In Windows 10
#Run these commands to enable an elevated Elevated PowerShell Prompt Here also known as PowerShell Here as Administrator when right clicking on a folder in Windows Explorer. These commands all work in both PowerShell and PowerShell Direct.
#HKCR: does not work in this example and you do not need to mount first. This method accesses the registry directly. Many instructions say to use New-PSDrive to mount HKCR: first and use that convention to access it to do many things but none of that is needed.
#Get-PSDrive will show you what is mounted.
Get-PSDrive
#▲As you can see there is no HKCR:
#Moving on…
#If done properly launching Elevated PowerShell Prompt Here will trigger a UAC prompt. This is normal and good. Create all the keys and values by typing the following commands in order:
New-Item Registry::HKEY_CLASSES_ROOT\Directory\shell\runas -Verbose -Force|ft -a
#This works when right-clicking only on folders in Windows Explorer and not drives or drive letters.
#Create the User’s file folder (from the Desktop Experience feature) on the Desktop of all new and current users
#Run this to create the User’s file folder (from the Desktop ExperienceFeature) on the Desktop of all new and current users. After that you will always have a folder nearby to single right-click on to launch an Elevated PowerShell Prompt Here session.
# Since HKLM is mounted already I can use the short path to manipulate the registry entries.
should appear on your Desktop after using F5 to refresh or on log off /reboot. Use the commands above to right-click and launch an elevated PowerShell prompt starting with the selected folder as a starting point.
#Enable The Hyper-V Role in Windows 10 Professional, Enterprise Or Education Using PowerShell
#If this is the first time, and if if this will be the only time enabling the Hyper-V role in Windows 10, then this PowerShellcommand is all you need. If you need to switch the Hyper-V services on/off to avoid interference with other hypervisors and without removing the Hyper-V role then download Hyper-V Switch.
#Continue reading if you are having issues or are using a conflicting hypervisor or emulator and getting the dreaded Blue Screen of Death.
#Having Issues Enabling Hyper-V Role In Windows 10 Professional, Enterprise Or Education?
Check Requirements
Windows 10 Enterprise, Professional, or Education
64-bit Processor with Second Level Address Translation (SLAT)
CPU support for VM Monitor Mode Extension (VT-c on Intel CPU’s)
Minimum of 4 GB memory
NOTE: The Hyper-V role cannot be installed on Windows 10 Home.
OK so beyond those requirements lies a different issue many are facing with the advent of Android based virtual machines and emulators.
BlueStacks Android Emulator and Andy Android Emulator both crash on load every time, when the Hyper-V role is active. It looks like both used to work together before the Anniversary Edition update broke the support of Hyper-V and other emulators running at the same time. Here is the bulletin from BlueStacks regarding this issue.
I want my computer to run everything and work right all the time, so I tried to install x86Android Android Emulator in Hyper-V as an alternative. Once I finally was able to get an older version to work; I found the touchscreen support / controls were unsuitable for my needs. The controls were pure garbage. I may revisit that scenario and try for a more complete configuration but BlueStacks Android Emulator is just so much more user friendly on every level. For now, I switch back and forth between a Hyper-V and a BlueStacks setup.
Here is what I found to switch Hyper-V on and off. Previously, I was removing the Hyper-V role and adding it again when needed, but a caveat of doing that is the Hyper-V Virtual Switch Manager settings are lost in the process. The settings need to be recreated and reattached to each virtual machine, every time the role is reinstalled. You end up with a lot of orphaned network adapters.
!!!Hyper-V Switch To The Rescue!!!
Calm down. This utility doesn’t allow Hyper-V to run simultaneously with VMWare, VirtualBox or BlueStacks, but this great tool I found at least saves a reboot (it takes two reboots if you add and remove the Hyper-Vrole). Also, I don’t have to reconfigure Virtual Switch Manager every time I do it. This program automates a bcdedit process to disable Hyper-V without removing the Hyper-Vrole as part of the process.
Use Hyper-V Switch to toggle Hyper-V support on and off when using other emulators like VirtualBox or Andy Android Emulator to keep it fast and simple. I saved it to my Desktop and edited the executable file to Run as Administrator just to be sure it has the rights needed. You can also single right-click on the executable file or shortcut and then single left-click on Run as Administrator every time.
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V#Type y and press Enter
Manually Enable Hyper-V From The GUI
Windows Key-R to bring up the Run box.
Type optionalfeatures.exe and single left-click OK to execute (just means to run) optionalfeatures.exe. This method actually allows for more control of the Hyper-V installation since you can deselect unneeded features. For example, some people may not have any need for the Hyper-V Module for Windows PowerShellmodule if they don’t use PowerShell or PowerShell Directto administer any virtual machines.
Single left-click to select the Hyper-V option. Single left-click the Plus sign to expand if you need to select or deselect any of the default features. I use all the Hyper-V features so PowerShell for this installation works just fine for me. The end goal is to avoid moving my mouse as much as possible.