This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 24%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECG%3C/text%3E%3C/svg%3E)
I am attempting to migrate a Windows 2008 R2 64 bit on premises vCenter guest to Azure. The replication completes but the VM won't boot in azure. When using the serial console and booting into safe mode with command prompt, I can see that it hangs loading classpnp.sys. I understand that 2008 r2 on premises is out of support but I also know that MS supports their migration to Azure and also supports extended update services in Azure until end of 2023. I have successfully migrated other 2008 r2 vms to azure and successfully subscribed them to eus and applied security patches. The VM that won't boot is running the same windows version and has same version of classpnp.sys.
I've tried using repair but it didn't help. I tried runnning both chkdsk and sfc on the on premises machine but that didn't help. I tried booting without driver signature verification and also tried last known good.
Any ideas for how to troubleshoot \ resolve a boot issue on azure vm that was migrated from on prem vcenter 2008 r2 guest?
I will suggest to check this old thread as it provides option to rename the classpnp.sys to Old and restart in the safe mode, worth giving a try .If that does not work I will recommend to raise a support case with Microsoft not sure if it will be supported with engineer assistance.https://social.technet.microsoft.com/Forums/en-US/566cdd43-ce91-4e64-93e0-8d09d8fc1ea0/windows-7-fails-to-go-into-safe-mode-stuck-at-classpnpsys?forum=w7itprogeneral
Thank you JimmySalian. I should have mentioned that I deleted the vm, attached the os disk to another vm and overwrote the classpnp.sys and build new vm and tried booting normally and with verification of driver signature disabled. No luck.
@c2 go2 Did you get a chance to see the suggestions posted by others?
@c2 go2 We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 35%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJN%3C/text%3E%3C/svg%3E)
I just ran into this same problem, only with HyperV locally running (Azure must be using the same thing), and no joy. If you migrated from VirtualBox, you may be out of luck (thousands of posts on unsuccessful migrations from VB) and the only solution is to create a fresh W2K8R2 system from HyperV (installation all the way), then do a restore from a backup. I'm pretty confident that VBox makes some sort of driver change that has nothing to do with the extensions (you can uninstall VBox extensions and still the problem persists). I'm still doing experiments, myself, and, if I can get a successful migration of this (old) OS to HyperV, I'm convinced it will work on Azure.
I will post an answer here, if I ever have one that doesn't involve recreating a brand new VM with an old OS.
@JD N Thanks for sharing your experience.
Hi, c2go - it could be Trusted Launch, try creating the VM as Standard security mode.
Change the Security Type to: Standard.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello there,
If a Windows Server 2008 R2 virtual machine (VM) that has been migrated to Azure hangs on the "classpnp.sys" driver, you can try the following troubleshooting steps:
Enable Boot Logging: Restart the VM and press F8 during boot to access the Advanced Boot Options menu. Select "Enable Boot Logging" to create a log file that records the drivers being loaded during startup. This log file can provide valuable information for troubleshooting.
Safe Mode: Try booting the VM in Safe Mode. Restart the VM and press F8 during boot to access the Advanced Boot Options menu. Select "Safe Mode" to load Windows with minimal drivers and services. If the VM boots successfully in Safe Mode, it indicates that a third-party driver or service might be causing the issue.
Analyze Boot Logging: After enabling boot logging (as mentioned in step 1), boot the VM normally and let it hang on the "classpnp.sys" driver. Restart the VM in Safe Mode and access the log file created during boot logging. Analyze the log file to identify any other drivers that are causing conflicts or errors. This analysis can help pinpoint the problematic driver.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer--