Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'SKASULKA-L' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running. at New-Switch, <No file>: line 121

[ShawnKasulka]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 143A8D40-325F-4E44-A216-7DB26EE8491B/20190517132524

Expected behavior

Actual behavior

Information

• Windows Version:
• Docker for Windows Version:

Steps to reproduce the behavior

1. ...
2. ...

[mikeparker]

Duplicate of #1221

• Your Hyper-V configuration is broken. This may be caused by a windows update.
• See Docker for Windows (and Hyper-V) not working after update to Windows 10 1709 #1221 (comment) for the 'control flow guard' fix

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked