I see no technical reason to constrain the windows native boot capability with a single boot vhdx early mounted
A registry key must exist or a BCD kernel parameter to mount additional VHDX
There is no one interested in documenting this broadly, but I suppose here is the right place to find someone who has the clue and knows the key.
For example, I see the following use case:
I have my parent volume deduplicated, having system+boot VHDX placed into an excluded directory, it works for me like a charm.
I consider it would be helpful to move most of the windows boot volume contents
out of this tiny file into one or more additional VHDX outside of the dedup excluded folders
Any thoughts
Thanks in advance
Edited by LevT, 23 April 2020 - 11:31 PM.