Our search turned up the following:
Our process is as follows:
- Open Task Manager
- Processes tab
- Click View and Select Columns
- Select and click OK:
- Click the Image Name column header to sort.
- Open Windows Explorer and browse to the Hyper-V folder where the VMs are stored.
- For smaller deploys we open the XML file with NotePad to discover the correct GUID associated with the VM.
- In our case it was VMWP.exe with GUID 52806B15-
- Terminate the process.
Once the VM’s process has been terminated we can address what was causing the stoppage, which in this case was an errant pass-through USB drive.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book
1 comment:
Although a good thought, this didn't work for me. The virtual machine in question still remains in a starting state.
Post a Comment