Beruflich Dokumente
Kultur Dokumente
Server & Tools Blogs > Server & Management Blogs > Virtualization Blog
Sign in
Virtualization Blog
Information and announcements from Program Managers, Product Managers, Developers and Testers
in the Microsoft Virtualization team.
Share 3 23 1
For those of you who run emulators in Visual Studio, you may be familiar with an annoying error:
It periodically pops up even when task manager reports enough available memory this is especially true for
machines with less than 8GB RAM. Most of the time, its because there genuinely isnt enough memory
available but sometimes its because of HyperVs root memory reserve discussed in KB2911380.
This blog will tell you what the root memory reserve is, why it exists, and why you shouldnt need it on
Windows 10 starting in build 15002 original announcement here. I also wrote a mini script to clear the
registry key that controls root memory reserve if you think it may be set on your system.
1 InvokeWebRequestUrihttps://raw.githubusercontent.com/Microsoft/VirtualizationDocumentation/live
2
3 .\clearMemoryReserveregkey.ps1
4
5 rmclearMemoryReserveregkey.ps1
https://blogs.technet.microsoft.com/virtualization/2017/01/27/nomoreoutofmemoryerrorsforwindowsphoneemulatorsinwindows10unlessyoure 1/4
6/15/2017 NomoreoutofmemoryerrorsforWindowsPhoneemulatorsinWindows10(unlessyourereallyoutofmemory)|VirtualizationBlog
We change HyperV host memory management periodically based on feedback and new technology things
like dynamic memory and changes in clustering. The root memory reserve is only one piece of that equation
and even calculating that piece has several factors. Modifying it is not supported but there is still a registry
key available for times when the default isnt appropriate for one reason or another.
KB2962295 basically describes measuring, monitoring, and modifying the root reserve.
1 $rootReserveKey="MemoryReserve"
2 $rootReserveKeyPath="HKLM:Software\Microsoft\WindowsNT\CurrentVersion\Virtualization"
3
4 #Andhere'showyouremoveit:)
5 RemoveItemPropertyPath$rootReserveKeyPathName$rootReserveKey
However, while the default memory management settings on server are now different from HyperV on
Windows, if root reserve is set on Windows 10 HyperV will respect it you wont see any of the memory
management changes we made. Which is why now is the time to clear that custom root memory reserve.
Cheers,
Sarah
ScottGu's Blog
https://blogs.technet.microsoft.com/virtualization/2017/01/27/nomoreoutofmemoryerrorsforwindowsphoneemulatorsinwindows10unlessyoure 2/4
6/15/2017 NomoreoutofmemoryerrorsforWindowsPhoneemulatorsinWindows10(unlessyourereallyoutofmemory)|VirtualizationBlog
Recent Posts
Windows Server 2016 Adds Native Overlay Network Driver, enabling mixed Linux + Windows Docker Swarm
Mode Clusters April 18, 2017
Whats new in HyperV for the Windows 10 Creators Update? April 13, 2017
Tags
Application Virtualization Azure Site Recovery Citrix Cloud Computing Community cross
platform management Disaster Recovery Dynamic Memory ESX events guest blog post High
Archives
April 2017 4
March 2017 1
February 2017 5
January 2017 5
December 2016 1
October 2016 5
All of 2017 15
All of 2016 17
https://blogs.technet.microsoft.com/virtualization/2017/01/27/nomoreoutofmemoryerrorsforwindowsphoneemulatorsinwindows10unlessyoure 3/4
6/15/2017 NomoreoutofmemoryerrorsforWindowsPhoneemulatorsinWindows10(unlessyourereallyoutofmemory)|VirtualizationBlog
All of 2015 18
All of 2014 36
All of 2013 30
All of 2012 23
All of 2011 41
All of 2010 58
All of 2009 97
All of 2008 80
All of 2007 13
All of 2006 3
https://blogs.technet.microsoft.com/virtualization/2017/01/27/nomoreoutofmemoryerrorsforwindowsphoneemulatorsinwindows10unlessyoure 4/4