{"action":"closed","issue":{"url":"https://api.github.com/repos/Microsoft/Virtualization-Documentation/issues/500","repository_url":"https://api.github.com/repos/Microsoft/Virtualization-Documentation","labels_url":"https://api.github.com/repos/Microsoft/Virtualization-Documentation/issues/500/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/Virtualization-Documentation/issues/500/comments","events_url":"https://api.github.com/repos/Microsoft/Virtualization-Documentation/issues/500/events","html_url":"https://github.com/Microsoft/Virtualization-Documentation/issues/500","id":192065944,"number":500,"title":"Win10 1607 14393.447 + Docker 1.14 hangs","user":{"login":"sterns","id":11664910,"avatar_url":"https://avatars.githubusercontent.com/u/11664910?v=3","gravatar_id":"","url":"https://api.github.com/users/sterns","html_url":"https://github.com/sterns","followers_url":"https://api.github.com/users/sterns/followers","following_url":"https://api.github.com/users/sterns/following{/other_user}","gists_url":"https://api.github.com/users/sterns/gists{/gist_id}","starred_url":"https://api.github.com/users/sterns/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sterns/subscriptions","organizations_url":"https://api.github.com/users/sterns/orgs","repos_url":"https://api.github.com/users/sterns/repos","events_url":"https://api.github.com/users/sterns/events{/privacy}","received_events_url":"https://api.github.com/users/sterns/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-11-28T17:24:44Z","updated_at":"2016-11-28T20:21:02Z","closed_at":"2016-11-28T20:21:02Z","body":"Hello,\r\njust like in issue 358, running `docker run -it microsoft/nanoserver cmd` in an elevated shell (PS or CMD) will just hang. Running `docker ps` in another elevated shell will hang, too. In the task manager, one CPU core is consumed to 100% (15% on a quad core with HT) by a process called _vmwp.exe_, while the rest of the system remains stable. \r\n\r\nAs the title says, I'm using Win10 Pro Version 1607 build 14393.447 and the docker build 1.14.0. \r\n\r\nUnlike some reports in issue 358, I don't get an error message in the console after 10 minutes. It just remains as is, without further information or feedback. \r\n\r\nI tried to remove docker from my system `dockerd --unregister-service`, deleted _C:\\ProgramData\\docker_ and deleted the docker application files in _C:\\Program Files\\docker_, rebooted and reinstalled everything again, but it didn't change anything on the behaviour. \r\n\r\nWindows Update won't give me anything new, so I assume the summary patch is included in my system already, though it's not listed in the update history. I made the update to 1607 rather late, so during the installation the installed patch level probably was already high enough. \r\n\r\nIs there anything else I can do or a place where I can find more logs to get a hint what's broken?"}}
{"actor":{"display_login":"sterns"}}