Well Ok so the share was on the array, but I changed the location to the nvme cache, so that new files would go on that, in the same share and that's what happened when I copied the vdisk into a new subfolder.
When I added to the VM, I did confirm before and after, it was using virtio with boot order of 1 -- this is something I did previously test, which sounds like what you are describing. I've also tried to use sata, scsi, ide, etc because yeah the first time the issue happened i thought that might be the case - or the wrong bios, but everything is correct, ive done this like 6 times now haha-- but I'm probably missing something still!
Here's the log when it boots into just the shell, not sure if this helps. I can repeat this on multiple vdisk types not just this Windows 10 VM, really bizarre behavior.
log.txt