Creating VM Crashes when SAN Policy : Offline Internal

On Windows To Go, creating a VM fails and crashes with no error message or log.
This appears due to the protective SAN Policy of Offline Internal.

Using diskpart to set san policy=OnlineAll allows a virtual machine to be created.
Setting san policy=OfflineInternal undoes this change, and the now created VM can work as intended without needing the san policy changing again.

This could be because virtual disk mounting respects this policy. The virtual disk would therefore be offline in disk manager when mounted with this san policy set and never receiving a drive letter for the copy operations.

One way to address this could be to check the disk is online as expected once mounted before attempting to assign a letter.
Another method could be to check this policy and set it temporarily to perform the operations. It would be polite to set it back, to respect the feature and avoid user's accidentally mounting drives unintentionally.

Reproduce VM creation on Windows To Go with san policy=OfflineInternal, then trace the virtual-disk mounting, online-state, drive-letter assignment, and copy operations. Done means creation no longer crashes or silently fails under the protective policy, while the policy is respected and the resulting VM works; verify the behavior with both OfflineInternal and OnlineAll.