Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Contact
  • Reviews
  • Toggle search form

Fix an error occurred while attempting to start selected VM on Hyper-V

Posted on 10/06/202610/06/2026 IT Expert By IT Expert No Comments on Fix an error occurred while attempting to start selected VM on Hyper-V
  1. Home
  2. Virtualization
  3. Fix an error occurred while attempting to start selected VM on Hyper-V
VM Failed To Start On Hyper V

When working with Hyper‑V and suddenly encounter an error similar to the one we will be discussing here, you are not alone. In this blog post, we shall discuss “Fix an error occurred while attempting to start the selected VM on Hyper-V”. This is a common issue when starting a virtual machine (VM) especially after moving files, deleting ISOs, or changing storage paths. Please see Failed to Upgrade VIHR Component: Failed to open deployer Service Management Port, and The Backup Was Safe: The Data Center Was not: A Real-World Lesson About Hidden Data Center Risks and Governance Failures.

A Virtual DVD Drive in Hyper-V is a synthetic device used to mount ISO images. It behaves like a physical CD/DVD drive and is commonly used for:

  • Operating system installation
  • Driver injection
  • Boot ISO environments (WinPE, recovery tools)

However, unlike virtual hard disks (VHD/VHDX), ISO files are not embedded in the VM configuration. They are external dependencies. If the ISO path becomes invalid, Hyper-V treats this as a critical configuration error during startup.

Why was the error “VM failed to Start”?

As you can see from the image below, the attachment: E:\All-Images…\windows_server_2025_x64_dvd.iso failed to open because the file was not found. This is because, the drive was deattached from the server.

This leads to the virtual machine failure and its unable to start because Hyper-V attempts to mount an ISO file that no longer exists. Since the ISO file is unavailable, Hyper-V cannot resolve the virtual media device, resulting in a boot failure.

Synthentic Iscsi Controller
ISO image referenced in VM configuration is missing or inaccessible

Because Hyper-V performs a device validation check before VM startup. This leads to a failing Component “The Virtual DVD Drive (SCSI Controller)” as shown above.

Please see Prevent Automatic Driver Updates in Windows and Xen-Orchestra, how to Switch from IP Addresses to DNS for Backup Infrastructure in VBR, and How to remove a Repository from Veeam Backup and Replication.

Solution

The fix involves removing the invalid ISO reference from the virtual DVD drive configuration. This ensures the VM no longer depends on missing external media.

To do this, open Hyper-V VM Settings from the Hyper-V Manager, right-click the affected VM (TechDC01), and select Settings.

Hyper V Settings

Locate the DVD Drive Configuration by navigating through the hardware tree: SCSI Controller and then click on “DVD Drive”.

To remove the Invalid ISO Attachment. Under Media configuration, click on “None”. This will detache the broken ISO reference.

Do not forget to apply the configuration changes by clicking on Apply and OK or OK on the fly as shown below. This will update the VM configuration metadata.

Remove Iso
By detaching or correcting the DVD drive configuration, the VM returns to a healthy boot state immediately.

Nex, start the VM, the VM should now boot successfully.

I hope you found this guide very useful on “Fix an error occurred while attempting to start the selected VM on Hyper-V”. Please feel free to leave a comment below.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:Fix an error occurred while attempting to start selected VM on Hyper-V, fix Hyper-V VM boot issue, Hyper V, Hyper-V, Hyper-V error occurred while attempting to start VM, Hyper-V host unable to start VM, Hyper-V virtual machine failed to power on, Hyper-V virtual machine not starting, Hyper-V virtual machine startup error, Hyper-V VM failed to start, Hyper-V VM startup failure, resolve Hyper-V virtual machine errors, selected VM cannot start Hyper-V, troubleshoot Hyper-V startup error

Post navigation

Previous Post: Failed to Upgrade VIHR Component: Failed to open deployer Service Management Port
Next Post: Secure Boot 2023 Compliance Across WinPE, MDT, WDS, and ADK: Boot Chain Alignment and PXE Validation [Final Part]

Related Posts

  • preometheus
    Monitoring Synology with Prometheus and Grafana Reviews
  • VMware Tech Showcase
    Great details on VMware Tech Showcase Virtualization
  • Entire VM restore
    Restore VM to Original location using Veeam Entire VM restore Backup
  • Map and disconnect Virtual Disk in VMware Workstation
    Map and disconnect Virtual Disk in VMware Workstation Virtualization
  • Azure Local New Policy fix
    How to Resolve New WDAC Policy Issues in Azure Stack Virtualization
  • SCSI Controoler HyperV issue failed to start VM
    Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found Virtualization

More Related Articles

preometheus Monitoring Synology with Prometheus and Grafana Reviews
VMware Tech Showcase Great details on VMware Tech Showcase Virtualization
Entire VM restore Restore VM to Original location using Veeam Entire VM restore Backup
Map and disconnect Virtual Disk in VMware Workstation Map and disconnect Virtual Disk in VMware Workstation Virtualization
Azure Local New Policy fix How to Resolve New WDAC Policy Issues in Azure Stack Virtualization
SCSI Controoler HyperV issue failed to start VM Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • 1 8y62mmvjlr 5uovgoq6zmq
    How to download and install DriveLock on Windows Security | Vulnerability Scans and Assessment
  • understanding azure active directory and enterprise mobility security ems 16 638
    Methods for Integrating Azure Active Directory with on-Premise Active Directory AWS/Azure/OpenShift
  • settings app not working featured 800x400 1
    How to save and stop modification to Microsoft Management Console Windows
  • Actualidad 211741393 129861581 1050x760
    Edge GPO settings: All Group Policies available to configure Microsoft Edge Settings Windows Server
  • How to install and configure a Standalone DNS Server
    How to Install and Configure a Standalone DNS Server Windows Server
  • officeonlineserver
    How to set up and Configure Office Online Server Microsoft Exchange/Office/365
  • 1 kajkbmlyehn0inifwrh 8w
    How to install Kerberos packages with Cygwin on Windows Windows Server
  • Featured post
    Installing Windows Subsystem for Android (WSA) Windows

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,796 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.