Hey everyone,

Apologies upfront. The description I gave for Minroot and when to use it all apply, but the way to implement via PowerShell was incorrect. Configuring Minroot is a simple bcdedit command which works today on Windows Server 2022/2025. A restart is required for this change to take effect.

Here's an example:
If you have a server with 32C/64T and wanted to conservatively set Minroot to use 50% of the cores in the system, the bcdedit command is:

bcdedit /set hypervisorrootproc 32

Keep in mind that hypervisorrootproc is setting the number of virtual processors that the root partition can use for servicing I/O. If I wanted to be more aggressive, and limit the root partition to 25% of the cores in the system, the bcdedit command is:

bcdedit /set hypervisorrootproc 16

As I said in the session, Minroot isn't a general-purpose feature that you should configure on every server. For most scenarios, you don't need to alter Minroot, just let Hyper-V automatically manage CPU usage. However, for those edge cases where VM jitter must be kept to an absolute minimum (manufacturing is where we've seen this most), Minroot can be impactful. Thanks everyone!

The set-vmprocessor and get-vmprocessor cmdlets don't accept -vmname ManagementOS. At least not on my 2025 hyper-v host. Is there an updated powershell module or some other perquisite that I need?

Jeff-Woolsey​ First time I've heard of the minroot conversation.  Interesting stuff.  Would be great if there was somehow a decision tree, or guide to help admins determine if its for them (and see an improvement).   Just a note however, you mentioned not to use bcdedit, Microsoft has doc pages that makes it look like that's the correct way to set it.

There will be a certificate for the days?

Thanks for tuning in! We hope you enjoyed this session and Windows Server Summit 2026. We’ll continue to answer questions here in the chat through the end of the week. If you missed the live broadcast, don’t worry – you can watch it on demand.

In fact, you can catch any of this week’s great Windows Server Summit 2026 sessions on demand by visiting https://aka.ms/WindowsServerSummit.

Share your feedback on Windows Server Summit. Click the image below to take our very short survey - thank you! 👇

Welcome to The future of Hyper-V: what we're building and why and Windows Server Summit 2026! Have a question? Post here in the Comments so we can help. Let’s make this an active Q&A!