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

[adrian-rt]

hey,

some help here please? I can't boot my windows system at all!

[adrian-rt]

hellooooooooooooooooo!!!!

This thing crashed my windows, how can I boot my windows system back again?!?!

How can you release software with a major bug like that??? I don't get it........

[adrian-rt]

from the windows logfile:

Root cause found:

Unspecified changes to system configuration might have caused the problem.

Repair action: Result: Failed. Error code = 0x32 Time taken = 500 ms

Repair action: System files integrity check and repair Result: Failed. Error code = 0x490 Time taken = 445625 ms

---

---

Session details

System Disk = \Device\Harddisk0 Windows directory = F:\WINDOWS AutoChk Run = 0 Number of root causes = 0

Test Performed:

Name: Check for updates Result: Completed successfully. Error code = 0x0 Time taken = 0 ms

What configuration changes did Docker do to my system that stops it from booting properly? SrtTrail.txt SrtTrail.log

[adrian-rt]

HEEEEEEEEEEEEEEEEEEEEEEEELP!!!!!

[jasonbivins]

Hi @am06

We are working with Microsoft to determine the issue. We believe it's due to Hyper-V, but haven't found the root cause. Are you able to boot Windows at all?

https://github.com/docker/for-win/issues/913

[adrian-rt]

Hi @jasonbivins ,

many thanks for the answer, please keep me posted !

just in safe mode for the last week or so :(

[jasonbivins]

Try disabling Hyper-V to see if it helps get you back into normal mode

in powershell Disable-WindowsOptionalFeature -FeatureName microsoft-hyper-v -online

[adrian-rt]

didn't work.

[adrian-rt]

any other ideas?

[adrian-rt]

an update please?

[adrian-rt]

how do you guys release software without even doing basic QA???

[adrian-rt]

any news here??

IT's almost 3 weeks now!!!! is anybody at least working on this???

[jasonbivins]

Hi @am06 Can you try to do a clean boot into Windows ? https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

Once you're able to get into Windows properly, we can look into Logs to see what Docker is doing behind the scenes

[adrian-rt]

will try that soon. I'm travelling atm.

Can I check those logs from safe mode? what's the location?

[jasonbivins]

You should be able to look into them from Safe mode - check C:\ProgramData\Docker There should be more clues there if the issue is Docker related.

[adrian-rt]

even after clean boot, the problem still happened.

I do not have a C:\ProgramData\Docker folder.

[fabriciomurta]

I just had my windows bricked by docker here too... heck. attempting system restore.

[fabriciomurta]

I get nothing useful from service.txt:

Version: 17.12.0-ce-win47 (15139)
Channel: stable
Sha1: 9c692cd5b38166289573183371647d915f300292
Started on: 2018/03/07 02:14:17.060
Resources: C:\Program Files\Docker\Docker\Resources
OS: Windows 10 Pro
Edition: Professional
Id: 1709
Build: 16299
BuildLabName: 16299.15.amd64fre.rs3_release.170928-1534
File: C:\ProgramData\Docker\service.txt
CommandLine: "C:\Program Files\Docker\Docker\com.docker.service"
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[02:14:17.172][DockerService  ][Info   ] Starting service
[02:14:17.215][BackendServer  ][Info   ] Started
[18:07:22.114][NamedPipeServer][Info   ] Version()
[18:07:22.114][NamedPipeServer][Info   ] Version done in 00:00:00.
[18:07:22.130][NamedPipeServer][Info   ] Start(Docker.Core.Settings, Docker.Core.DaemonOptions)
[18:07:22.130][PowerMode      ][Info   ] Stop
[18:07:22.130][HyperV         ][Info   ] Stop
[18:07:22.146][PowerShell     ][Info   ] Run script with parameters: -Stop True...
[18:07:22.161][PowerShell     ][Info   ] Creating a Runspace Pool...
[18:07:22.902][PowerShell     ][Info   ] Runspace Pool created (Min=1, Max=2)
[18:07:23.532][HyperV         ][Info   ] Script started at 18:07:23.484
[18:07:23.620][Moby           ][Info   ] Stop
[18:07:23.623][Linux          ][Error  ] Failed to start: Unable to stop: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.
at <ScriptBlock>, <No file>: line 80. Let's retry
[18:07:23.636][Installer      ][Info   ] Checking for features: Hyper-V, Containers
[18:07:23.637][PowerShell     ][Info   ] Run script...
[18:07:25.217][PowerShell     ][Info   ] Run script...
[18:07:26.021][PowerShell     ][Info   ] Run script...
[18:07:26.998][PowerShell     ][Info   ] Run script...
[18:07:27.832][Installer      ][Warning] Need to install feature(s): Hyper-V, Containers
[18:07:40.017][NamedPipeServer][Info   ] Version()
[18:07:40.017][NamedPipeServer][Info   ] Version done in 00:00:00.
[18:07:40.017][NamedPipeServer][Info   ] InstallFeatures(Docker.Core.Features.Feature[])
[18:07:40.018][PowerShell     ][Info   ] Run script...
[18:07:54.095][PowerShell     ][Info   ] Run script...

It does not look like it logs anything as the reboots fails, it just logged once I clicked 'sign out' (18:07), should have logged something else on the next boot attempts, which would be spaced by minutes.

[Farscaper]

Why me as well? You try to be cutting edge and you cut your own throat instead.

[fabriciomurta]

I could get my system back at booting state but now it always hangs for a while (maybe up to a minute) while booting up. what used to take, ~15 seconds to boot up now it is up to 1m30s. lucky me I don't reboot often.

[Farscaper]

Any way to remove Docker from the command line if I can get that far?

[fabriciomurta]

Unfortunately, I can't say that. You probably can if you can call system restore to revert the registry to some point. The problem is that the pesky installer fiddles with stuff about Hyper-X, some hardware-related features that breaks the whole system. Probably it attaches DLLs at boot time, I couldn't figure out what was it. And it does it all without generating a system restore point either.

In my case, I had recently upgraded Visual Studio 2017, which generated a recent restore point. But The updated visual studio were all broken when I restored (which was a point before VS2017 was upgraded). I needed then to fully perform an uninstall, cleanup anything left, and then reinstall Visual Studio 2017.

Yet, the delay during boot up was still there. Probably if I boot up with logging I could get the point it stops and identify which driver it attempts to load that incurs in the delay...

I have seen some suggestions with registry keys and bios settings around that didn't help me (tried before the system restore point).

You can get down to system restore just by trying to boot, and rebooting three times or so, in which Windows 10 kicks in the setting options. I believe I couldn't boot even in safe mode back then, but system restore ran nicely.

[Farscaper]

Currently trying a month old C: drive image backup from O&O Disk Image. Fingers crossed.

[fabriciomurta]

Just an update... Needed to reboot the machine today. It takes nine minutes to boot. If I look at event viewer after boot I can see it logs nothing at that time it kept stuck. It simply does nothing for 9 minutes. Numlock on and keyboard does not respond to any commands.

Unfortunately it seems windows 10 does not output that realtime driver loading screen that used to work on previous windows versions, even if I disable UEFI boot up logo.

[docker-robott]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

[fabriciomurta]

I refuse to try and brick my system again, not trying to install it here just to see all broken. So forget about it if you will, I won't be installing docker for windows here again. I ended up using an ubuntu virtual machine with docker off it.

[aswin1758]

Issue is not fixed. I tried installing docker for windows yesterday and it bricked my system. Docker requested the reboot after installation and the system went straight to repair mode at reboot.

[stoked10]

Exact same issue with latest windows, 1803 I think. Once it reboots after docker install the boot screen hangs and eventually BSODs. I created a system restore point right before installing but that fails too. The only thing that worked was doing an OS reset which keeps your files but wipes every application not installed with the vanilla OS. Which is an absolute ridiculous pain.

I echo an earlier comment on how this installer was actually released and add why is that installer still available 10 months after the issue was discovered?!?

This issue is now 10 months old, anything??

[sebialex]

I too had a similar experience a few months back. Windows 10. Basically after installing docker and enabling Hyper-V, the system would completely freeze about 5-10 seconds after login. Had to disable virtualization in bios, which allowed me to boot and not crash, disabled Hyper-V and uninstalled docker. Great /s. Back to Ubuntu VM.

[nakti]

I don't know if it's the similar issue.... When I installed Docker for windows a few days ago and enabled Hyper-V and containers, my system couldn't boot: a few times immediate crash after Windows logo appearing, then unsuccessful automatic repairs. I've messed so much with windows files, that I had to reinstall windows completely. Yesterday I installed Docker on the clean system, and it crashed again on reboot. Virtualization in BIOS was turned off. I've restored to restore point, manually enabled Hyper-V in the PowerShell, then installed Docker and it didn't crash the system, but it doesn't work because it needs virtualisation enabled. When I enable it, Windows won't start...

Any new info on these issues?

[ghost]

The only way it worked for me was to install the first release of win10 1709 (without any update), disable updates, then install docker.

[BriannaBromell]

My computer won't boot after Docker install and HyperV restart --Full fix (you need to end HyperV, which means no 'docker for windows'. You will be using Docker-Toolbox @ https://docs.docker.com/toolbox/overview/

What went wrong? Your system does not support Hyper-V and panics now that it is a thing.

1. In bios disable virtualization to allow windows to boot without using safemode. (possibly F10 on boot)
2. Open Windowskey+x, Power shell (admin) or elevated CMD prompt.
3. Disable HyperV in accordance with https://stackoverflow.com/questions/30496116/how-to-disable-hyper-v-in-command-line ( I ran several of the suggestions to be sure as I do not understand it in detail) This will "fix" your computer but break docker.
4. Uninstall docker
5. In bios, enable virtualization.
6. Download and setup Docker-Toolbox in accordance with https://docs.docker.com/toolbox/overview/#ready-to-get-started

[youngaj]

Is there any resolution to this problem? I finally got my Windows version to update to 1809 but now I can't run docker for windows anymore which was a key component of the application I'm trying to build.

Any new direction would be greatly appreciated.

[ka-br]

Same issue here today on latest version of Windows10 and Docker. Would love some guidance on a potential fix or if there is any additional information we can provide to help diagnose the problem.

[ghost]

Hello,

There are multiple similar issues, I had this kind of problems for about one year and I did a lot of debugging. My guess is that the main issue was related to Hyper-V rather than docker.

I updated to 1903 and fortunately all good now, no more issues.

[dmitridb]

Well that bricked my brand new system I just spent quite the amount of time setting up. Great use of my time there, thanks docker team and microsoft for having it together, golf claps all around

I'm sure it will work fine on linux but this really leaves me feeling like 'why the hell do people think docker is useful' because every time i've encountered it there's something insane like this. Really, bricking my computer, what a cherry on top of everything else wrong I've seen happen with this. What next, is docker going to like shoot my dog or something

[dmitridb]

OK enough with the snarkyness. While I go hunt some mini screwdrivers to put a working linux installation on a drive into the empty bay I have ready in this laptop I was hoping to keep on windows, and before I go clean install my way out of this waste of time, is there any specific diagnostic information you would find in useful in fixing this from me?

It's an hp probook 455 with an amd ryzen 7 2700u pro in there, made sure SMD was enabled in BIOS, maybe there's something else I can check?

[dmitridb]

lmao I can't even reset my PC while saving my files even if I try, this is great isn't it

https://imgur.com/a/GQxlx1Z

if I wasn't already a regular linux desktop user and like did stuff that actually needed windows or was addicted to video games or whatever, I guess I would be really angry... but really this is just hilarious to me, it confirms a lot of biases about all this software

I really don't have time to waste on giving a bug report for this if a full wipe and restore doesn't work and I just end up running linux as my main OS again

[fabriciomurta]

I was able to get back to booting my windows without re-installing everything by running over system restore... it screwed my visual studio set up that I just updated before trying this (names here) piece of (more names here) by doubling all menus and so on, which then I could fix with the "repair" option in add/remove. But as I said when I fixed it, boot up takes a lot more time. And differently than what I said, some times ti takes up to 10 minutes to boot up. I just go grab a coffee when I boot up. As I don't reboot often (like, every 6 months or so), it does not hurt me that much. Again, it is the worst experience I ever got with any software running under windows.

Now I use docker off a ubuntu guest OS in VirtualBox. Works like a charm there. there.

[dmitridb]

I hope you see the insanity of having to need to do this in the first place what with all the virtualization-within-virtualization overhead as if this is a really bad, nerdy version of the movie 'inception'

[fabriciomurta]

well docker does run a linux-ish virtual machine, so in a ubuntu virtual machine, I just run the "jail" part of docker, no "paranormavirtualization" so not really virtualization-within-virtualization as you suggested

[dmitridb]

That is correct, so to be more clear on what I am talking about, its more like a stacking of different types of overhead incurred, productivity and time wasted etc included

I really have yet to see gains in either of those every time I'm required to use this tool in the past vs. LXC wrapped in some basic scripts or whatever

Oh well considering it wrecked my windows install to the point of not even being able to wipe and recover, wasting an entire afternoon, guess I have some reason to be bitter haha

Sent from ProtonMail mobile

-------- Original Message -------- On Jun 17, 2019, 5:10 PM, Fabrício Zimmerer Murta wrote:

well docker does run a linux-ish virtual machine, so in a ubuntu virtual machine, I just run the "jail" part of docker, no "paranormavirtualization" so not really virtualization-within-virtualization as you suggested

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[dmitridb]

OK I have twice now narrowed it down to what seems to be hyper-v conflicting with installing drivers for the amd ryzen 2700u pro / vega 10 graphics chip -- in case this information comes in useful for anyone else who has to deal with this issue, i have reinstalled windows and have watched it do exactly as described twice now

I dunno what microsoft has in order to report this kind of problem, maybe someone else does, but well here's my experience

[BennyLeeJT]

omg guys, installing dockers just BRICKED my laptop running Windows 1809 and Intel HD onboard graphics. It loads into the user account login page and then BSOD. The windows stop code is "WHEA UNCORRECTABLE ERROR".

I initially could get into safemode from UEFI. I uninstalled dockers from safemode and restarted. it still didn't work, same BSOD error msg. i tried go into safe mode and disable Hyper-V, still didn't work. Because after unchecking that feature, I need to restart to let it take effect and I can't boot into windows without that BSOD and stop code. So the uninstalling of Hyper-V feature will undo by itself and be re-enabled. Then I tried system restore to the night before dockers installation. Well what do you know? it got worse! now booting goes straight Automatic Startup Repair and then it will show "failed", I can't boot into safe mode anymore. now the windows BSOD stop code is "CRITICAL PROCESS DIED".

All other options failed. Can't reset whether i choose to save my files or not. Other than trying to reinstall windows. I am not sure what to do now. I echo-ed what the original poster said : "How can you release software with a major bug like that??? I don't get it........"

################### update, somehow UEFI is unable to detect my USB thumb drive to boot windows installation, hence I tried several times on different thumb drives and tried reformatting FAT32 and NTFS and was not able to boot from USB, even changing the boot order and clicking to run EFI USB from UEFI. Note that by default secure boot is disabled and support for legacy is enabled. In the end I managed to open the setup.exe from USB thumb drive by opening from command prompt at UEFI and reinstalled windows on the only partition I have.

I went back to my Windows.old folder and into my user account and i found out my Desktop and my default Documents folder, were wiped clean. not sure if it is the system restore attempt that did that. I am not installing dockers in windows again. Docker Team, you wasted at least 7 hours of my time and 2 hours of my friends' time trying to undo Dockers installation. You guys need to show some love to Windows users with quality testing and bug fixing on this simple installation issues.

[touqeershafi]

This docker just crashes my dell g7 on windows 10 when i installed it and now I've to reset it!

[youngaj]

Updating my bios resolved this problem for me

Sent from my iPhone

On Oct 28, 2019, at 1:48 PM, Touqeer notifications@github.com wrote:

This docker just crashes my dell g7 on windows 10 when i installed it and now I've to reset it!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[touqeershafi]

@youngaj which laptop model?

[KimLangholz]

I had to disable SVM in BIOS in order to get Windows to load after installing Docker... That means however, that I'm unable to run Android Emulator... Haven't been able to get it to work with SVM enabled yet.

[KimLangholz]

Update. If I disabled IOMMU in BIOS, I was able to both enable SVM and Hyper-X. Been running smoothly for two days now.

[kg-2]

To get my laptop to boot I had to press f2, f8, f12 (not sure which one worked) and then select the hard drive when it asked me what to boot from. Then I uninstalled docker and disabled windows hyper-v to get my computer to return to normal.