Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Hyper-V Manager error when attempting to start a Virtual ALTO



This article describes the cause and solution for a Hyper-V Manager error that states "An error occurred while attempting to start the selected virtual machine(s)" when trying to start a Virtual ALTO on Hyper-V.


When store a Hyper-V virtual machine on a volume with the ReFS file system, the integrity bit of the virtual hard disk (VHD or VHDX) must be turned off.


There are two ways you can solve this problem. The first solution is move the Virtual ALTO VHDX to a volume that does not use the ReFS file system. Alternatively, you could use the PowerShell cmdlet Set-FileIntegrity to turn off the integrity bit of the Virtual ALTO VHDX. Assuming that the name of your Virtual ALTO is VirtualDevice.VHDX, run the following:

Get-Item VirtualDevice.VHDX | Get-FileIntegrity

This command will verify the status of the integrity bit. Once you've verified this, run the next command to turn off the integrity bit: 

Get-Item MyVirtualHardDisk.VHDX | Set-FileIntegrity -Enable $False

Once you've done this, you should be able to start your Virtual ALTO with no errors.

Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!