You can use Performance Monitor however to monitor the “System\ % Registry Quota In Use” counter. There really is no good answer for this outside of installing the hotfixes noted above, and keeping a close eye out on your registry hives.
Additionally, there is a known issue with SQL Server 2012 SP1 that can cause the registry to hit the 2GB limit and put the machine in a no-boot state. This hotfix does not “fix” the issue, but prevents it from occurring in the first place. , which refers to the “.\Printers\DevModes2” key bloat. Some of the ones we have seen are related to There are many reasons that cause registry hives/keys to bloat. What happens if I see this problem on another OS version?Īre there any tools I can use to troubleshoot this issue? How do I fix this issue once the hotfix is installed? How do I prevent this issue in the first place? With that, the following questions may come to mind: You can boot and be logged in with a temp profile and not be able to install any software due to the RQL. You can boot and not be able to log in due to the RQL (Registry Quota Limit). When you get into this state, you may experience one of the following issues: This problem occurs because of the 2 GB size limit of the registry hives in 圆4-based version of Windows. The registry hives for the computer are larger than 2 gigabyte (GB).
You have a computer that is running the 圆4-based version of Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012. Hello AskPerf! Pushing up a blog today to discuss the registry bloat issue that has been recently addressed in the following KB:Ĭomputer cannot be restarted if the registry hives are larger than 2 GB First published on TECHNET on Oct 22, 2014
0 kommentar(er)
