Windows 10: Change Display Scaling Zoom Level of Hyper-V Virtual Machine

How to: Change Display Scaling Zoom Level of Hyper-V Virtual Machine

How to Change Display Scaling Zoom Level of Hyper-V Virtual Machine in Windows 10


Information The Windows 10 Pro, Enterprise, and Education editions include the Hyper-V virtualization technology. Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems can be used and managed just as if they were physical computer systems, however they exist in virtualized and isolated environment. Special software called a hypervisor manages access between the virtual systems and the physical hardware resources. Virtualization enables quick deployment of computer systems, a way to quickly restore systems to a previously known good state, and the ability to migrate systems between physical hosts.

Starting with scaling and set it to 100, 125, 150 or 200 – whichever matches your preference.

This tutorial will show you how to change the Zoom Level of a Hyper-V virtual machine to override its default display scaling (DPI) in Windows 10.



Note Starting with Windows 10 build 14965, Microsoft fixed an issue where depending on the zoom level selected, the VM window might not be created large enough to avoid scrollbars, despite their being enough space for it. Microsoft also updated the logic so that when you pick a particular zoom level, that zoom level preference will be preserved for the next VM connection. Along the way, Microsoft fixed an issue where the title bar of a maximized VM window would be occluded when taskbar had been set to on top.



Here's How:

1. While you have a Hyper-V virtual machine running, click/tap on View in the menu bar, click/tap on Zoom Level, and select 100%, 125%, 150%, or 200% for the display scaling you want for the virtual machine.






That's it,
Shawn


Related Tutorials

• How to Setup and Use Hyper-V in Windows 10 for OS Virtualization
• How to Change your DPI Scaling Level for Displays in Windows 10

:)

 

Hyper-V Virtual Machine not recognised

The folder where your VM is do you see a .vhd file?

Here is a great article step by step on how to import VM into hyper-v.

https://social.technet.microsoft.com/wiki/conte...

 

Hyper V Import Virtual Machine

There is separate default folders for Virtual Machines and Virtual Hard Disks

C:\ProgramData\Microsoft\Windows\Hyper-V

This folder contains all settings for each Virtual machines.

Have you changed that folder?

C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks

This folder contains only virtual disks. On your case it's changed to E:\HyperV\...

When you want import VM you need to search it from that first location.

You can check this location from Hyper-V settings.

If you can't import existing VM's you can create 3 new Virtual Machines.

When creating those select option Use existing Virtual Disk and point disks from E:\HyperV\...

 

Hyper-V, VM, Virtual Machine

You will have to ensure the Virtual Machine is running and connected to the Internet.

This means the physical host, the machine itself must be connected.

Review:

Configure Remote Desktop connection to Hyper-V Virtual Machine ...

 

Hyper V not connecting to virtual machine

Hi.

Regarding Hyper V firstly check all steps and requirements from here:

https://docs.microsoft.com/en-us/virtualization...

And here

https://docs.microsoft.com/en-us/virtualization...

For more details about how to set up it better to use another community:

https://social.technet.microsoft.com/Forums/en-...

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?