The magic and flexibilty of using vhdx files (no need for a VM HYPER-V)

And also easy to clone to external devices if you want to run as WintoGO systems.

I really am amazed that this great system from Ms is so underused and mis understood -- but hey if it gets TOO useful ms might abandon it. !!! Hopefully not.






And an ENG version



Cheers
jimbo

You have a thing for VMs! I use VirtualBox to run Beta and Dev builds on but that's as far as it goes. For most non-savvy Windows users VMs are beyond the scope of what they need/want to know.

I'd love to use VMs but my laptop, although very recent, just is not fast/powerful enough, probably as it only has 4GB of RAM. But it's great for browsing.

The benefit of the VM here is that you might want to run multiple machines concurrently. I often run labs for testing things at work where maybe I need a domain controller, a storage server and 2 SQL cluster nodes to run a test. That's what I use VM's for.

I use a latest VMware Workstation with host and guest OS W10 Pro 22H2.
Allmost all my daily work is done in guest OS's, besides W10 I also have guests - W11 Pro and Ubuntu Mate. I must say a performance is highly acceptable.

I started this about 10 years ago. On main host OS I use minimum apps, only those that needs extra graphics power.

---
I have an average PC hardware, about 900e with 32GB RAM. I do not play games.

Not sure why you keep posting similar.

We have discusses pros and cons many times re. native boot vhdx and Hyper-V vhdx files.

Native boot vhdx files are convenient way of dual/multi booting but only one instance of Windows can run at a time.

Hyper-V is a different beast as you can run multiple instances, with much less risk of affecting host with virus infections etc.

Setup properly, you can native boot a vhdx file AND run it in a Hyper-V vm (not at same time of course).

The easiest way is to ensure VHDX file has an independent EFI to run in Hyper-V.