I though my ESX to Hyper-V conversion worked perfectly, until I realized two of my volumes were write protected.

Jimbob2026 · Sat Feb 14, 2026 7:42 am

Source was VM-Ware hosted Windows server 2019 std AD and APP server. Previous tech had been running shadow protect as backup. V2V appeared to work perfectly but I soon realized that two of my disks were write protected somehow. AI reckoned it was the Shadow Protect filter but AI assisted registry editing resulted in a bluescreen of death. 5 hours down the drain.

Has anyone else experienced this? Should I remove Shadow Protect before doing the conversion.

Sat Feb 14, 2026 7:53 am

Yes, it seems a good idea. Conversion might not run at all if the file is used by something else.

mr_vaughn · Fri May 01, 2026 6:26 am

You should NOT perform a Live running VM migration of Active Directory Domain Controllers. I have always powered mine off. This help prevent issues with how snapshots of AD occur and then replicate during the migration.

App servers it can vary and depends on the application on the source server. Database servers I power off. File servers I do live.

Fri May 01, 2026 7:30 am

Powering off the VM is a solid way. Yet, it is not necessary. Do it if you want to play it safe (the destination VM might start having a data gap the moment conversion is over).
Think of conversion as running a full backup. You get a backup, yet, its data "ages" the further you travel from the backup point.