# Experience Record: Migrating a BitLocker-Encrypted Windows Drive to a New Computer ![PXL_20240818_171148432.MP](https://hackmd.io/_uploads/Bk8I1hDiA.jpg) ## Background I decided to transfer my Windows hard drive from an old computer to a new one. The drive was encrypted with BitLocker, which I knew might introduce some challenges during the migration process. ## Initial Problem After connecting the hard drive to the new computer, I was prompted to enter the BitLocker password, as expected. However, after entering the password, Windows began the boot process (indicated by the spinning circle), but then the screen would go black, and I was asked to enter the BitLocker password again. This cycle continued without successfully booting into Windows. ## Discovery of Unrecognized Drive After several failed attempts, the system eventually directed me to the repair page, but with limited options available. I accessed the Command Prompt and used diskpart to check the disk status, only to find that the system couldn’t recognize the hard drive. I then tried using a Windows 11 Installation Media to see if I could upgrade the existing Windows 10 installation while keeping my files. However, I discovered that upgrading requires the process to be initiated from within Windows, not from a bootable media. Furthermore, even the clean install option within the installation media failed to recognize the hard drive. ## Known Issue with Intel Processors I found out that this issue was a known problem with 11th, 12th, and 13th generation Intel CPUs, where the system could not recognize NVMe drives without the Intel Volume Management Device (VMD) drivers. I downloaded the necessary drivers, booted into the Windows 11 Installation Media, and loaded the drivers during the installation process. Afterward, I returned to the "Repair your computer" option and accessed the Command Prompt. This time, I was prompted to enter the BitLocker password again, and after successfully unlocking it, diskpart was able to recognize the hard drive. ![PXL_20240819_141037801.MP](https://hackmd.io/_uploads/S1lJl2DiC.jpg) ![PXL_20240819_141238312](https://hackmd.io/_uploads/H1Qxl3DoC.jpg) ![PXL_20240819_140704380](https://hackmd.io/_uploads/BylK6y2Ds0.jpg) ![PXL_20240819_143440131.MP](https://hackmd.io/_uploads/Skv-g3ws0.jpg) ![PXL_20240819_143453675](https://hackmd.io/_uploads/r1Fflnwi0.jpg) ![PXL_20240819_143509526](https://hackmd.io/_uploads/ByA4l2DsC.jpg) ## Driver Installation to Resolve Boot Issues Given that this known issue was likely the reason my system couldn't boot properly, I decided to install the VMD drivers directly into my existing Windows 10 system. Using the dism command from the Windows 11 Installation Media's PE environment, I added the drivers to the offline Windows 10 installation. After doing this, I was able to boot into Windows 10 successfully. ## A Side Note Once I logged into Windows 10, I encountered another issue—Windows required an internet connection to log in with my Microsoft account, but the system lacked the necessary Wi-Fi drivers, and my computer didn’t have an Ethernet port. After considering my options, I cleverly connected my phone via USB and shared its internet connection with the computer, which allowed me to log in. Problem solved—feeling very smart about that workaround! ![PXL_20240819_142047317.MP](https://hackmd.io/_uploads/Skoel3Do0.jpg)