Skip to content

TechDirectArchive

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

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

An error occurred while attempting to start the selected VM

Posted on 18/04/202411/08/2026 Christian By Christian No Comments on An error occurred while attempting to start the selected VM
  1. Home
  2. Virtualization
  3. An error occurred while attempting to start the selected VM
Error message in Hyper-V Manager indicating a failure to start a selected virtual machine due to a missing virtual disk support provider.

A Synthetic SCSI Controller refers to a virtual storage controller used in virtualization environments found in hypervisors like VMware vSphere, Microsoft Hyper-V, or other virtualization platforms. This controller emulates a SCSI (Small Computer System Interface) controller in software rather than being a physical hardware device. In this article, we shall discuss how to resolve an error occurred while attempting to start the selected VM. Please see How to Fix Boot Failed UEFI SCSI Device on HyperV, and Video on how to Fix the Boot Failed UEFI SCSI Device on HyperV.

Synthetic SCSI Controllers are utilized within virtual machines (VMs) to provide virtualized storage interfaces. Synthetic SCSI Controllers play a crucial role in providing efficient and flexible storage solutions within virtualized environments, contributing to better resource utilization and performance for virtual machines.

Also, see the fix to “The logon attempt failed for the remote desktop connection“, and how to Install Hadoop on Linux.

Reason for this issue

This issue occurs when starting a virtual machine (VM) due to a problem with the Synthetic SCSI Controller. As you can see from the error message. This problem is with the ISO image attached but cannot be opened because the USB has been detached. Therefore, the fix for this issue is very simple.

Screenshot of Hyper-V Manager displaying an error message indicating that the virtual machine 'TechDC01' failed to restore due to an issue with the virtual disk support provider.

Also, see the fix to “The following error occurred attempting to rename the computer Account already exists“. How to fix “Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found“.

Resolution “An error occurred while attempting to start the selected VM”

To fix the error, please proceed with the steps below.

An error occurred while attempting to start the selected VM. VM failed to restore, Synthetic SCSI Controller, failed to restore a virtual disk support provider for the specified file was not found

To fix this issue, navigate to the VM running on HyperV, right-click on it and select settings as shown below.

Screenshot of a virtualization management interface displaying virtual machines, showing 'TechDC01' with options for 'Connect...', 'Settings...', and other actions in a side menu.

Note: If an ISO image was attached to the SCSI controller. But the USB required to access it is disconnected. You may need to remove the ISO image from the VM configuration. This can also be done through the VM settings or configuration files.

Kindly shutdown the VM as instructed below and proceed to the settings as suggested once again.

Settings window for virtual machine TechDC01, showing the configuration for the DVD Drive with an attached ISO file for Windows Server 2022 preview.

Specify media to none and click on OK.

Screenshot of the settings menu for a virtual machine named TechDC01, displaying options for configuring the DVD drive, including a selection for 'None' or an 'Image file', with buttons for 'OK', 'Cancel', and 'Apply' at the bottom.

As you can see, you will be able to start the VM once again and connect to it.

Screenshot of a virtual machine management interface showing two virtual machines, TDAVBR and TechDC01, both in a running state with CPU usage of 6%, and indicating their assigned memory and uptime.

I hope you found this fix very useful on how to fix “An error occurred while attempting to start the selected VM’. 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, Windows Server Tags:hyperV, HyperV VMs, Hypervisor, Microsoft Windows, Windows Server 2016

Post navigation

Previous Post: Setup iSCSI Target and Storage LUN on Synology DS923+ for VBR
Next Post: Perform Office Online Server Update via Windows Updates

Related Posts

  • windows update 03
    How to target WSUS clients with the registry keys Windows Server
  • Proxmox Installation
    Install Proxmox VE on a Beelink EQ12 Mini PC Virtualization
  • Repository Path in Veeam Scale Out Backup Repository e1779138897770
    Fix broken Repository Path in Veeam Scale-Out Backup Repository Backup
  • maxresdefault 1
    DriveLock Components: Important DriveLock components to master Windows Server
  • Fix this PC cannot run Windows 11
    Bypass unsupported CPU and Processor by upgrading to Windows 11 via Windows Update Virtualization
  • allthings.how how to download and install winget windows package manager windows 10 winget cli
    How to install Winget CLI on Windows Windows Server

More Related Articles

windows update 03 How to target WSUS clients with the registry keys Windows Server
Proxmox Installation Install Proxmox VE on a Beelink EQ12 Mini PC Virtualization
Repository Path in Veeam Scale Out Backup Repository e1779138897770 Fix broken Repository Path in Veeam Scale-Out Backup Repository Backup
maxresdefault 1 DriveLock Components: Important DriveLock components to master Windows Server
Fix this PC cannot run Windows 11 Bypass unsupported CPU and Processor by upgrading to Windows 11 via Windows Update Virtualization
allthings.how how to download and install winget windows package manager windows 10 winget cli How to install Winget CLI on Windows Windows Server

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

  • Ubuntu on Windows
    Install Ubuntu 20.04 LTS on Windows via WSL Linux
  • Storage Explorer
    How to Install Azure Storage Explorer on Windows AWS/Azure/OpenShift
  • Screenshot
    How to configure Synology Active Insights Network | Monitoring
  • Old Right click Context Menu
    How to Restore Old Right-click Context Menu in Windows 11 Windows
  • Feature image Error Code 0xC1900101 – 0x30018
    How to Fix Windows Update Error Code 0xC1900101 – 0x30018 Windows
  • How to Disable Integrated Graphics
    How to Disable Integrated Graphics on Windows Windows
  • Install FileZilla Client
    FileZilla Client on Mac: How to Transfer Files to WordPress via SFTP Mac
  • ycx
    How to use SysInternals Live Tools Windows Server

Subscribe to Blog via Email

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

Join 1,752 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.