Windows 10: "PIN no longer available problem" in advanced raw disk VM setup

To give some context, my machine is setup with 2 physical NVME disks, one with Windows 11 installed and the other with Linux installed the particular distro should not matter in this situation. This multiboot setup is useful in order to have both OS available for use at raw level performance. However, it is nice to occasionally be able to run both OS at the same time. My solution to this is using Virtualbox on both OS, whereby the host OS can spin up the guest OS by running the guest OS in a VM and accessing the NVME disk through a Virtualbox raw disk image, which essentially is a virtual ha

:)

 

Migrating On Prem VM to Azure

Hi Experts, We have a requirement of moving out VMs as is in Azure from Current On-Prem and the process we are following is

1. Create a RAW image from an on-prem VM.
   
2. Convert the RAW image to VHD.
   
3. Move the VHD file to Azure Storage.
   
4. Convert the Disks to managed disks.
   
5. Mount the OS disk to the C drive and other disks respectively.
   

Issue - Once we mount the OS disk we are not able to RDP to the machine we have followed the steps suggested in the below links and as usual there are millions of documents and none point in the right direction unfrotunately.

Links followed to figure out options to get this done -

Prepare a Windows VHD to upload to Azure - Azure Virtual Machines | Microsoft Docs - Microsoft documentation.

Attach an existing OS disk to a VM - Azure Virtual Machines - Microsoft documentation.

Upload a VHD to Azure and create a virtual machine - Stephanie Kahlam - Some helpful people created this and

We have tried options

1. Created image from managed disk and tried to initiate the VM and got exception as below
   Provisioning failed.
   OS Provisioning for VM 'demo-1' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:
   * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
   * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/.
   
   
   and the suggested solution 1 to use CreateOption=Attach creates the VM but does not allow us to RDP to the machine so we are assuming it's not booting up. The other option suggested in the hyperlink is to create image using SysPrep which is not an option for us as we are performing a lift and shift.
   

I would like to get some guidance from experts on to the right process to follow.

 

Save RAW drive - Don't want data


Open Admin command prompt, then type:

1. diskpart
2. list disk ======> Take note of disk # of the RAW drive
3. select disk # ======> is the number in step 2
4. clean
5. exit

Open Disk Management and initialize it, Create Simple, format.

 

Disk listed as RAW

After windows 10 pro update, my boot drive disappeared. I started with installation disc and went into recovery command prompt. With “Diskpart” I viewed the disks on my pc and my boot disk was listed as RAW, after exiting diskpart, I run chkdsk /f on that
drive and it was readable again, however, after restart the drive went back to RAW.
I tried this several times and after every reboot the drive goes back to RAW.

How can I fix this permanently?