Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Virtualization » An error occurred while attempting to start the selected VM

An error occurred while attempting to start the selected VM

Posted on 18/04/202409/10/2024 Christian By Christian No Comments on An error occurred while attempting to start the selected VM

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.

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.

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.

Specify media to none and click on OK.

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

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.

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

  • oracle virtualbox
    Fix VirtualBox Virtual Machine Encountered a Non-Fatal problem Virtualization
  • image 64
    Windows Local Account Authorization and Access Control Windows
  • HybridCloudTrust
    WHFB Hybrid Cloud Kerberos Trust Model is now available AWS/Azure/OpenShift
  • hero activedirectory
    How to find disabled Active Directory User accounts Windows Server
  • Copy files between host and workstation
    Various ways to copy files from host to VMware Workstation VM Virtualization
  • screenshot 2020 04 27 at 17.34.38
    Remote Server Administration Tools: Install RSAT on Windows Windows Server

More Related Articles

oracle virtualbox Fix VirtualBox Virtual Machine Encountered a Non-Fatal problem Virtualization
image 64 Windows Local Account Authorization and Access Control Windows
HybridCloudTrust WHFB Hybrid Cloud Kerberos Trust Model is now available AWS/Azure/OpenShift
hero activedirectory How to find disabled Active Directory User accounts Windows Server
Copy files between host and workstation Various ways to copy files from host to VMware Workstation VM Virtualization
screenshot 2020 04 27 at 17.34.38 Remote Server Administration Tools: Install RSAT on Windows Windows Server

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

sysadmin top30a

  • Data drive is locked by BitLocker and not OS drive Fastboot Option
    Fast Boot Options: Fix specific Drive issue with BitLocker [MBAM] Windows
  • delete Apps from Launchpad on Mac
    How to delete Apps from Launchpad on Mac Mac
  • Feature image registry editing
    How to Disable and Enable Registry Access on Windows 11 Windows
  • banner
    How to install and configure FSRM in Microsoft Windows Server Windows Server
  • GitLab runner update and upgrade
    How to update Gitlab-runners on Windows Windows
  • openstack ola
    Openstack Deployment with Devstack Linux
  • Enable Nexted Virtualization on VirtualBox
    ESXi VMB 411 Halting: Virtualbox Nested VT-X/AMD-V greyed out Virtualization
  • Veeam backup for proxmox worker update failure
    What to know about “Failed to perform Veeam Worker Upgrade” Backup

Subscribe to Blog via Email

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

Join 1,823 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

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