Though hyper-V and Windows Sandbox are great environments in my opinion (used it for many years). Enabling them can disable features from other software, since turning on the feature turns your OS to a hypervisor in itself. Some software such Ryzen Master to name one, don't like that and won't be able to start. If you use software that either can't run or can't stably run in a (virtualized) hypervisor environment I'd look into VirtualBox or one of the other competitors.
Especially since anything Windows, hyper-v included, are terribly documented many forget that it has the same native features as VirtualBox and VMware workstation. Sandbox should only be used as a testing area, and not as a VM testing environment. Sandbox only gives a clean sandbox environment that will delete itself upon closing. It's not a virtual machine environment, let alone customizable, like a real VM is.
Recently stepped over to VirtualBox, since some of the quality of life software I have come to use over the years aren't fully compatible with hyper-v enabled and won't run just a windows saying cant run with VBS enabled bla bla bla (Enabling Hyper-v turns your OS to a virtual hypervisor under the hood).