Share via

Windows Server 2022 VM Migrated from VMWare to Azure Local with Azure Migrate BSOD on boot.

Richard Beyer 61 Reputation points
2025-11-23T13:03:01.6333333+00:00

I have attempted to migrate a Windows Server 2022 VM from VMWare 6.7 to Azure local on a Dell AX-760 cluster, Azure Local version 12.2511.1002.5. The VM is assigned :

  • 4 CPUs
  • 24 GB
  • 3 hard disks
  • one NIC, type E1000E, with 2 static IP addresses.
  • SCSI hard disk controller is set to LSI Logic SAS.

The VM has been prepared with the PowerShell script for static IP address and the Diskpart Policy=OnlineAll.

Upon completion of the migration, the VM boot loops with a BSOD. The error displayed alternates between "PAGE_FAULT_IN_NONPAGED_AREA" and "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". Secure boot is not enabled for this VM.

The same issue happens if I try to boot into safe mode and system repair does not help either.

I have migrated other Windows server 2016 and 2019 VMs successfully but this is the first Windows Server 2022 I have migrated.

Thank you,

Richard Beyer

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
0 comments
Answer accepted by question author
  1. Adam Zachary 2,025 Reputation points
    2025-11-23T23:38:34.2666667+00:00

    I’ve seen this exact problem with Windows Server 2022 specifically, and it isn’t Azure Migrate itself.

    Server 2022 on VMware often boots with LSI Logic SAS or E1000/E1000E, but Azure Local does not support those drivers once the VM is converted.

    When the OS loads and cannot find the expected storage or NIC driver, it throws PAGE_FAULT_IN_NONPAGED_AREA or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on boot.

    What fixed it for me:

    Switch the SCSI controller in VMware to VMware Paravirtual (PVSCSI) before running the migration. Server 2022 requires the correct storage driver during the image conversion.

    Change the NIC type to VMXNET3, then reinstall VMware Tools so the correct drivers load.

    Shut down, prepare again (static IP script + diskpart OnlineAll), then re-run the migration.

    Once I switched the storage and NIC controller types, the Server 2022 VM booted normally in Azure Local with no BSOD.

    Windows Server 2016 and 2019 work with LSI Logic SAS more often, but Server 2022 is much stricter with driver compatibility during Azure Local conversions.

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Suchitra Suregaunkar 3,545 Reputation points Microsoft External Staff Moderator
    2025-11-24T02:22:49.25+00:00

    Hello Richard Beyer,

    Thank you for posting your query on Microsoft Q&A platform.

    As suggested by Adam this is not an Azure Local platform defect. The crash occurs because Windows Server 2022 enforces stricter driver requirements during boot.

    • VMware VMs often use LSI Logic SAS (SCSI) and E1000/E1000E (NIC).
    • After conversion to Hyper‑V, these drivers are missing, causing kernel faults.
    • Windows Server 2022 is more sensitive to unsupported storage/NIC drivers compared to 2016/2019.

    As a resolution, please try below workaround:

    1. Update VMware VM Hardware Before Migration:
    • Change SCSI Controller to VMware Paravirtual (PVSCSI).
    • Change NIC Type to VMXNET3.
    • Reinstall VMware Tools so the correct drivers load.

    Shut down the VM and re‑run migration prep:

    • Apply static IP script.
    • Run diskpart → automount enable and attributes disk clear readonly (Policy=OnlineAll).
    1. Configure Target VM on Azure Local:
    • Create the VM as Generation 2 (UEFI).
    • Enable Secure Boot → Template: Microsoft UEFI Certificate Authority.
    • Attach the migrated VHDX to SCSI Controller.
    • Use Hyper‑V Network Adapter (not Legacy).
    1. Remove VMware Components Post‑Migration:
    • Boot into Safe Mode if needed.
    • Uninstall VMware Tools: 
        Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*VMware*" } | ForEach-Object { $_.Uninstall() }
    • Remove hidden VMware devices: 
        set
    • Delete any leftover VMware NIC/SCSI drivers.

    Repair System Integrity: Run Below command 

    
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

    PVSCSI and VMXNET3 ensure the OS uses modern drivers that Azure Migrate or conversion tools can map correctly to Hyper‑V equivalents.

    Gen‑2 with UEFI/Secure Boot aligns with Windows Server 2022 security requirements.

    Removing VMware components prevents driver conflicts during boot.

    References:

    https://learn.microsoft.com/en-us/azure/azure-local/migrate/migration-azure-migrate-vmware-overview?view=azloc-2511

    https://learn.microsoft.com/en-us/azure/azure-local/migrate/migrate-vmware-requirements?view=azloc-2511

    https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/migrate-vmware-to-hyper-v

    https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V

    Thanks,

    Suchitra.

    1 person found this answer helpful.
    0 comments
  2. Richard Beyer 61 Reputation points
    2025-11-23T13:23:34.8366667+00:00

    I have tried the AI generated suggestion to set Dynamic memory. I set it to 4 GB minimum and 96 GB max with the same BSOD result. The system has plenty of capacity.

    0 comments
  3. Richard Beyer 61 Reputation points
    2025-11-24T01:11:47.6633333+00:00

    Thanks, Adam. I'm giving the PVSCSI a try. After changing the controller, the VM went through several BSODs before it finally booted. I'm holding off on the NIC to see if the disk controller fixes it. However, the VMWare VM is showing as shutdown in the Azure Migrate system at this time. I did a restart of both migration appliances and I'll wait until tomorrow to see if it shows available again.

    I'll give an update in the morning (EST)

    0 comments
  4. Richard Beyer 61 Reputation points
    2025-11-24T12:48:41.5733333+00:00

    Thank you to both Adam and Suchitra. Your solutions did the trick and the migrated VM is functioning.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.