Skip to content

TechDirectArchive

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

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

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

Posted on 10/06/202623/06/2026 Christian By Christian 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.

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
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

  • VMware Tech Showcase
    Great details on VMware Tech Showcase Virtualization
  • vcenter sign on
    CVE-2021-22048: VMware vCenter Server updates address a privilege escalation vulnerability Security | Vulnerability Scans and Assessment
  • hero windowsserver hyperv scaled
    Why does the legacy PXE not does work on Generation 2 VM Virtualization
  • OxscsIP
    Enable Virtualization in Windows: Fixing VirtualBox’s 32-bit Option Virtualization
  • VMware Error Fix
    How to fix “The process cannot access the file because another process has locked a portion of the file” Virtualization
  • Slide2 2
    Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization

More Related Articles

VMware Tech Showcase Great details on VMware Tech Showcase Virtualization
vcenter sign on CVE-2021-22048: VMware vCenter Server updates address a privilege escalation vulnerability Security | Vulnerability Scans and Assessment
hero windowsserver hyperv scaled Why does the legacy PXE not does work on Generation 2 VM Virtualization
OxscsIP Enable Virtualization in Windows: Fixing VirtualBox’s 32-bit Option Virtualization
VMware Error Fix How to fix “The process cannot access the file because another process has locked a portion of the file” Virtualization
Slide2 2 Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

veeaam100

Veeam Vanguard

  • Disable BitLocker
    How to Disable BitLocker on Windows 10 Windows
  • SSH Keys Generation
    How to Generate SSH keys in Windows 11 Windows
  • screenshot 2020 03 07 at 22.25.21
    How to export and import User Profile – FrontFace Lockdown Tool Windows
  • Create Windows Defender Firewall Rule
    Fix Windows defender blocked incoming connection on Windows Network | Monitoring
  • Windows Logo
    Restrict IP Address Range on Windows PC Windows
  • Norton backup
    How to set up Norton Cloud Backup on Windows Anti-Virus Solution
  • dotnet6783
    Various methods to Install .NET Framework in Windows Windows
  • Featured image wifipass
    Find saved Wi-Fi Passwords in Windows 10 and 11 Network | Monitoring

Subscribe to Blog via Email

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

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

Tags

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

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.