crashed my windows :((

[adrian-rt]

Hi all,

so I've installed docker for windows and now my computer crashes on reboot :(

Please see attached log file.

Many thanks for your help.

Yes, I've googled the problem, tried a lot of things for the last 4 hours and nothing worked:(

log.txt

Unable to start Docker for Windows service: 2 at Docker.WPF.BackendClient.CheckService() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\BackendClient.cs:line 329 at Docker.WPF.BackendClient.SendMessage(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\BackendClient.cs:line 152 at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 95 at Docker.Actions.<>cDisplayClass18_0.b0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 81 at Docker.WPF.TaskQueue.<>cDisplayClass19_0.<.ctor>b1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

[igorantun]

I'm having the same issue here. Windows won't boot unless I disable SVM on my BIOS, which, of course, makes me unable to use Docker. Disabling IOMMU didn't work.

It all worked just fine a couple weeks ago, so I have no idea why it isn't working right now.

I have a Gigabyte AB350M, and a Ryzen 5 1600.

[zezke]

I ran into the same issue after installing Docker for Windows. All repair attempts failed (system restore and reset) so I had to do a clean install. Even restoring the BIOS settings to what they were before didn't help. That is a lot of wasted time!

My motherboard is a Asus Prime X570 Pro and a Ryzen 3950X.

[igorantun]

@zezke Same here. Restoring and resetting Windows didn't work, as well as flashing the BIOS to the latest version. Only a clean install of Windows fixed the problem.

[dmitridb]

@zezke Yeah looking at the correlations here with your hardware this is clearly a problem not exactly with docker but docker relying on activating hyper-v under windows in order to actually work, so therefore they're probably waiting for Microsoft to fix the problem between that and AMD hardware. I tested this last summer just by installing windows fresh and activating hyper-v on my own hardware and watching it fail. Therefore they probably don't really have any power to fix the situation, and we won't see this open issue closed until whenever the hell that happens. Wonderful for an already obesely bloated contanerization solution isn't it? Anyways if you -really- need this crap for a soul destroying job where dumbass middle management thinks you need it or whatever I suggest trying it under linux and seeing if you have any luck

[fabriciomurta]

I don't agree with several points from you @dmitridb I would like to share:

• My setup is an Intel processor so, unless you were referring to motherboard's chipset, this issue is not specific to AMD.
• This must be a problem with Docker not microsoft, as I can neatly run docker under VirtualBox with no issues (other than having to sync files between host/guest, having double the trouble to work with the projects, etc). Docker probably use some virtualization code that could just be as compatible as VirtualBox but, for some reason, it simply isn't.
• If they really cared about the issue as you said, they would have posted at least once in this. The only tag this gets is a "stale" one from bot. So, I believe this is still open "just because". They probably deem the few people under this issue too few to raise concern. While I was dumped by docker in my Windows machine, I have at least two colleagues that installed and use it without issues.

I mean no offense to your point of view on the matter but I'm just frustrated about the lack of attention Docker gave to this issue. :(

It is important noting that docker is a linux native sandbox application; a linux jail; something supported on linux for years, just with a whale label and neat management tools. That's why it needs extra virtualization layer to run "straight" off Windows or Mac. Yes, this is the same as Sandboxie. Except Sandboxie is windows native (and won't work on other systems I think), and Docker got a lot of marketing.

[dmitridb]

@fabriciomurta important information you provided there. If you have time to bust stuff (haha) try activating hyper-v on a fresh install

[dmitridb]

@fabriciomurta curious what hardware specifically?

[fabriciomurta]

• Processor: Intel Core I7 4790K (yes, a little old, but still pretty fast in my opinion)
• Mainboard: Gigabyte Z97M-D3H; both chipset and south bridge Intel, BIOS is AMI

If that matters,

• Memory: 4x corsair 8Gb, PC10700 = 32Gb total
• GPU: EVGA GTX 1080 Ti

So, as you can see, this is pretty a lot intel-ish. If you look up at the log I shared March 2018, there are reported hyper-v issues from the service, as if its linux part couldn't initialize it.

Virtualbox has VT-x enabled. System reports VT-x is enabled (as below)

I read somewhere I wouldn't have been able to run 64-bit guest OS's in virtualbox if I hadn't VT-x enabled. But as you say, what's needed is Hyper-V. In fact, I have just looked that up, and I don't have Hyper-V platform items enabled if I go to "Turn windows features on and off.". And this makes sense with what I can read in docker service log I linked above.

Since I set up an Ubuntu virtual machine to run Docker things, I've abandoned the idea of trying to fix it in "native" windows.

I think I am still not over the trauma, but when I have some time (and guts), I will try that again with Hyper-V enabled. I may have removed this while I was trying to sort things out, so maybe if I just enable it, chances are my system will brick once again.

[dmitridb]

Yeah I would go ahead and run clonezilla or something on your system before testing that, but at this point it's probably just wasting time with unpaid labor for a company that doesn't have its act together. I just find it hilarious that enterprises have this as a first choice due to pure hype while this company isn't even profiting and will likely end up sold off to some company that forces vendor lock-in or other horrible typical stuff https://www.zdnet.com/article/docker-is-in-deep-trouble/ watch people get over docker in 1-3 years after something more KISS comes around and knocks it outta the park lol

[dmitridb]

http://techgenix.com/docker-acquired-by-mirantis/ I'm actually glad this happened instead of what I had just mentioned, even though I don't use this software when I can avoid it

[youngaj]

@youngaj which laptop model?

@touqeershafi I have a Dell XPS 15. I updated my BIOS a few months ago and Docker has been running smoothly ever since.

[dannypage]

Adding to the issues: I have a Razer Blade Stealth 13” 2017, with a Intel chip. Recently installed Docker and it had been working until I shut down the computer. Turned it on, had to repair, and Windows went backwards to set it up. Same thing tonight, except this time I am now locked at the boot screen and Windows won’t repair at all, so I’m gonna have to spend some time repairing my entire OS installation.

Extremely frustrating that this appears to be a 2+ year issue now with the possibility of completely borking the system without warning.

If there are any logs I can find after the repair, I’ll send it along, but want to add to the chorus that there is something very wrong that needs to be fixed.

[vasstavr]

I had the some problem. Fortunately, I had taken a system image backup recently (23 days before) and I managed to recover my system without clean install (no other solution suggested above worked). I think docker team must add an instruction for taking system image backup before installing docker, in the page "Install Docker Desktop on Windows"

[uladzimir-miadzinski]

today I faced with the same issue. after installing Docker 2.2.0 it broke my windows 10.

the only thing that I can see when my computer starts is motherboard start screen and nothing happen. computer can stay for half an hour with that view.... What should I do?

I have Intel Xeon e5 2640 processor https://ark.intel.com/content/www/ru/ru/ark/products/64591/intel-xeon-processor-e5-2640-15m-cache-2-50-ghz-7-20-gt-s-intel-qpi.html

it has all VT technologies as I think to support docker containers

in BIOS VT is enabled

---

update: Disabling Intel VT in Bios helped to run windows.

[thequy]

Something conflict between Hyper-V and SVM. Turn-off Hyper-V feature so you can enable SVM and start Windows without crash. Back to Docker Toolbox (a legacy version) if you still want to use it @_@

[uladzimir-miadzinski]

Something conflict between Hyper-V and SVM. Turn-off Hyper-V feature so you can enable SVM and start Windows without crash. Back to Docker Toolbox (a legacy version) if you still want to use it @_@

I turned off hyper-v, but I also want to use the latest docker 2+, and I think that docker team just close their eyes on this problem.

[dmitridb]

imma go on the record with this one. potential employers will judge me on this when they look at my github page. someone might give me crap for it.

docker is incredibly bad software and shouldn't have happened, your organization is at a productivity loss if they think they have to use this, and people should probably just take the 30 minutes learning curve on how to use lxc or something else instead :100:

[Grizzlly]

It's sad that this is still happening...

[fabanc]

I got the same issue. It was a breeze to get it working on Ubuntu, but I decided to give a try on a Windows 10 VM.... I have never been so glad to try something on Virtual Machine. It got the same issue, and the VM is a goner. I am really not impressed.

[rokx]

Just got my windows 10 crashed big time. UEFI boot straight to hell just after the install of Docker for Windows. Event the error screen was first time seen by my eyes. Fortunately was able to hold F8 right at pc power on and I came to the selecting boot mode menu. Started system in Safe mode and at booting it detected the system could not be updated,the pc restarted itself and everything went back to normal. When normal windows booted Docker said it could not start because the Hyper-V was not enabled or something like that.

Really surprised this could happen. Didn't have bad experience with docker until now.

[vkryvytskyy]

Docker also crashed my windows PC. RE-installation helped me to solve this, but i wouldn't use docker on my windows PC, unfortunately.

[wschindel2020]

How is it possible that I bricked my Windows 10 computer today on a 2 year old known issue? Your drivers are not compatible. Highly disappointed in Docker. Get your stuff together.

[sejori]

Yup. Bricked my PC too. I have been having to reconnect my CMOS battery for weeks now to get windows to boot. I knew I had installed Docker the day it started but put it down to the CMOS dying, thought it couldn't be Docker. After trying multiple fresh batteries it seems like it was Docker all along. Such a pain because I have done loads of work but will have to system restore.

PSA: Need Docker on Windows? Use Vagrant.

EDIT: I have since learned that this might not be entirely Docker's fault. Seems some dodgy AMD driver's weren't helping but Docker was the final nail in the coffin for me.

[szomx96]

Same here. I disabled virtualization in UEFI and then Windows started, but when I enable it back the issue still occurs (even though I uninstalled the Docker). Restoring Windows to the auto restoring point didn't help. I'm not going to use Docker on Windows anymore, but maybe someone knows what to do to enable virtualization again and avoid clean windows installation?

[dc-tec]

Same issue here on Windows 10 2004. After reboot stuck while logging in. Disabled virtualization in BIOS and was able to login without issues. Removed docker desktop and Hyper-v feature. Not doing this again, will be using a Ubuntu VM.

Edit: enabled virtualization in BIOS again after removing Docker Desktop. Am able to login without issues now.

[tsarchghs]

If your monitor didn't display post and bios, and you were left in the dark, a possible solution is to CTRL+ALT+DEL and create an explorer process.

<Will update after trying to disable hyper-v with powershell since I coudn't find out how to start a powershell process with admin permissions without GUI ("Run as administrator")>

Update: After creating "explorer" process, GUI works and you can disable Hyper-V with running powershell as administrator, this was not enough for it to work after restart so I also uninstalled docker and then everything went to normal.

Disappointed for having to deal with this from using the first installer on the official site. Thank god it wasn't my work pc.

[Jarinha99]

An issue with 2 years.... that's disgusting.

Also, thanks all the guys who helped everyone here, i had the same issue in my personal windows pc, let's back to Linux.

[avengerx]

It is now a feature, enjoy guys and gals! :P

[nikitashum]

After installation of latest docker on Windows home 2004 windows stops being able to boot. Only way to boot back was to delete windows update. Tried one more time, first installed latest windows update, reboot, installed latest docker for windows, windows fails to boot on reboot. Just hangs with black screen.

[Jarinha99]

Thanks for the new feature Docker :)

[davisjose19]

This feature seems to be working very well. All you need to do is install docker and reboot. Voila!!! Your pc is now hung/slow/kinda-dead.

Fixed it by booting into safe mode and removing docker. Seems to be working normal after that. P.S. Created a restore point.

[sorrow719]

On Ryzen 7 3700U this feature works well too :) But i found some strange behavior - once i able to boot my windows, but after i update my drivers - it's stop working (as expected). Thanks for suggestion about restore point, but it's not work in my case. Finally

[ThomasAunvik]

On Intel i7-10510U, this feature is excellent, i even tried a complete windows reinstall, and the feature again worked after minutes of install! Without this feature, i wouldnt have had to loose a whole day of work hours!

PS: After many attempts, i removed docker via recovery tool cli, and booted into safe mode, and it then worked.

[Izzud]

Bricked my windows twice this week now trying to install this program. Thanks, docker team :)

[r4zendev]

Whenever I try to start windows now it says there were some problems with booting. After removing docker via safe mode it is fixed. Very nice.

[gnorbsl]

Man two years old issue and it still bricks windows for users. Amazing QA.

[MarioGK]

Yeah having the same problem as well with a Ryzen 2700

[dmitridb]

lmao

[manishi2V]

I am using Windows 10 Professional and installed Docker on my machine, I got serveral errors just after restart. I found that all my desktop icons get lost, I restarted my laptop but still getting same issue. Even my keyboard was not working, I used mouse to uninstall Docker, restarted my machine and all working fine and all files re appear on my desktop. I again installed Docker for Windows using same setup exe and now Docker is also working fine. Just after a day, Visual Studio got crashed, even after repair, Visual studio not working on my machine. I again uninstalled Docker and then re try to open Visual studio, now Visual studio working fine. What kind of release has been provided by Docker? This is not a Software, this is a kind of Virus.

[rasyidcode]

I thought I am the only one having this issue

[pmantz]

I was facing the same issue after installing docker in my XenDesktop VM and I was able to fix it following this answer https://stackoverflow.com/a/62446334/539093

[Harduim]

Same here, docker desktop for windows bricked my Windows 10 VM.

[pedes]

Coming here to report the same issue, installed the latest version of docker today 22/11/2020, in an HP Pavilion with Windows 10 Home licensed from HP, then the installation/download process took a really long time, and all of the sudden when I restarted the machine I got the blue screen, so tried to reset the bootloader and Windows got back again (like using a backup from a few days ago).

But! I shut down the working windows, and restarted it again and now it doesn't work.

This is a HUGE problem between Windows and Docker. Bricked my laptop.

[dmitridb]

[... removed for context and brevity ...] I guess I've found the culprit. Based on @youngaj 's post I checked my BIOS and saw that the Hyper Threading was set to Auto instead of Enabled. I'm thinking that maybe it has something to do with my mobo/CPU not "spinning back up" properly when the demand hits. I'm going to try this for a few days to see what happens. Hopefully it's just a funky driver implementation that was intended to save power (or something like that).

Looks like it worked for me. Updating my BIOS to Enabled instead of Auto has worked wonders -- no more crashing! Of course, your solution will vary based on your manufacturer and motherboard, so -- if you plan to try this -- please refer to their respective support pages to figure out what/how to do this for your situation.

- Happy Hunting!

Hey friend, I think you got the wrong issue and might benefit others finding if this is related to a more relevant seperate issue. This one is the one where windows isn't bootable nor in some cases even recoverable after installing Docker on some hardware configurations.

[azarc3]

[... removed for context and brevity ...] I guess I've found the culprit. Based on @youngaj 's post I checked my BIOS and saw that the Hyper Threading was set to Auto instead of Enabled. I'm thinking that maybe it has something to do with my mobo/CPU not "spinning back up" properly when the demand hits. I'm going to try this for a few days to see what happens. Hopefully it's just a funky driver implementation that was intended to save power (or something like that).

Looks like it worked for me. Updating my BIOS to Enabled instead of Auto has worked wonders -- no more crashing! Of course, your solution will vary based on your manufacturer and motherboard, so -- if you plan to try this -- please refer to their respective support pages to figure out what/how to do this for your situation. - Happy Hunting!

Hey friend, I think you got the wrong issue and might benefit others finding if this is related to a more relevant seperate issue. This one is the one where windows isn't bootable nor in some cases even recoverable after installing Docker on some hardware configurations.

Thanks; moved/deleted.

[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