SD Support
DE EN
Article

One article from the knowledge base, shown in full. You can read it without signing in, and nothing on this page is sent to the service desk or changes a ticket of yours.

Settings on this page

All articles
The button next to the article title takes you back to the article list, the same page as Knowledge base in the top bar. That list has a search box, a category filter and a language filter.
New ticket
In the top bar. Opens the form for raising a new ticket, with fields for your email address, a subject and your message.
Log in
In the top bar, for seeing your own tickets. Reading articles needs no account. Once you are signed in, the bar shows your email address and a Log out button instead.
EN / DE
Switches the language of the portal and keeps you on this article. The choice is remembered for your next visit. The article text itself does not change with it.
Light / Dark
Chooses the bright or the dark colour scheme. The portal starts dark. Your choice is stored in this browser only and applies to every page of the portal.

Reading the results

The article text
The whole article on one page, with its headings, lists, steps and links as they were written. Nothing is shortened and there is no next page to open.
Language of the article
Each article is written in one language, which may differ from the language you are reading the portal in. The article list shows your language by default and offers an All languages option.
Reading an article opens no ticket and notifies nobody. If it does not solve your problem, use New ticket and say which article you read and what you already tried.
 Log in

Hyper-V VM stuck in 'Starting', 'Stopping' or 'Saved-critical' state

All articles

Symptoms

  • VM shows a transitional state (Starting/Stopping/Restoring/Paused) indefinitely.
  • Cannot turn off, reset or connect to the VM from Hyper-V Manager.
  • Other VMs on the host may be fine.

Fix it yourself

  1. Check Hyper-V-VMMS and System event logs for related errors and note any recent host changes (updates, storage/network interruptions).
  2. Identify the stuck VM's worker process: 'Get-Process | Where-Object {$_.Name -like "vmwp"}' and match the PID to the VM.
  3. Forcefully end the stuck worker process: 'taskkill /PID /F' (this powers the VM off; unsaved data in the guest is lost).
  4. Restart the Virtual Machine Management Service (VMMS).
  5. Start the VM again and verify its state; check storage availability for its disk files first.
  6. If VMs remain stuck after the service restart, restart the Hyper-V host.
  7. For clustered VMs, also review cluster events (1069/1135/5120) that can leave VMs in critical states.

If that did not help

Attach Hyper-V-VMMS-Admin event log export, the VM's state and PID, cluster logs if clustered, and a procdump of the stuck vmwp/VMMS process if requested.