Reputation: 311
Failed to start service: The service did not respond to the start or control request in a timely fashion
at CommunityInstaller.Service.Service.<StartAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CommunityInstaller.Service.Manager.<AddServiceAsync>d__7.MoveNext()
I'm getting this error during install - the previous install hung and then onwards it does not complete successfully. Any idea how to repair this or cleanup and restart?
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CommunityInstaller.ServiceAction.<DoAsync>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at CommunityInstaller.InstallWorkflow.<HandleD4WPackageAsync>d__29.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CommunityInstaller.InstallWorkflow.<ProcessAsync>d__24.MoveNext()
Upvotes: 19
Views: 56949
Reputation: 761
The problem is usually with Windows Management Instrumentation (WMI).
For me, docker started crashing and I uninstalled in (sadly unproperly). For 5 days I have struggled with this docker issue but this command worked like a charm for 4.23.0.
Running this command in cmd as Administrator fixes the problem :
CD C:\Windows\System32\WBEM && dir /b *.mof *.mfl | findstr /v /i uninstall > moflist.txt & for /F %s in (moflist.txt) do mofcomp %s
Upvotes: 0
Reputation: 4106
Delete the following folders and try again
Upvotes: 0
Reputation: 49
Docker components require a compatibility layer for running Linux binary executables natively on Windows 10 and Windows 11.( When you opt for "install required components for WSL2" ).Try installing WSL before installing docker on your system. To install WSL and Docker, follow these steps~
wsl --install
4. After completion, restart your computer 5. Try reinstalling docker
Before installing WSL, make sure your windows version is updated.
Refer this link to install WSL
Upvotes: 1
Reputation: 3274
I have faced a similar issue and needed to do the following:
Uninstall.
If there are any leftovers, you should:
After this, I was able to install it properly. Also, I have noticed in my case, this situation has become repetitive in every update.
P.S.:
The power idea proposed in the previous answers didn't work in my case. Somehow, the installation got corrupted and couldn't run. This has happened more than once after Docker tries to update.
Upvotes: 1
Reputation: 1585
I updated Windows 10 using Windows 10 Update Assistant, and the docker got installed.
(The update was from version 19042.1237 to 19043.1237)
Upvotes: 0
Reputation: 76
For me the issue was related to https://github.com/docker/for-win/issues/127
A different version of NLog from the windows GAC was interfering with the one that comes with the docker installation.
To resolve this the version in the GAC has to be deleted:
Upvotes: 2
Reputation: 16
I am late to answer but I am able to solve this issue using simple fix. This is valid if you have recently upgraded your Windows OS to latest version.
Upvotes: 0
Reputation: 2245
Since I saw some comments regarding overall installation issues, I have separated a link with the main issues faced while installing Docker Desktop for Windows 10
More discussions about other related access-denied issues below: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/kb4565503-installed-then-wsl-2-failed-to-start/25794c4f-0b20-465e-bbdb-a8af3d9e0e88?auth=1
A good alternative one: https://www.omgubuntu.co.uk/how-to-install-wsl2-on-windows-10
In case you are facing some CPU/memory consumption issue in Windows, these settings could help https://medium.com/@lewwybogus/how-to-stop-wsl2-from-hogging-all-your-ram-with-docker-d7846b9c5b37
Probably you will face this issue regarding disk space, in that case, take a look at this thread on Github https://github.com/microsoft/WSL/issues/4699
Upvotes: 0
Reputation: 484
I faced the same issue while installing Docker 3.5.0
Download failed: Could not find a part of the path ‘C:\Users\name\AppData\Local\Temp\rzsiezg3p2h’. at CommunityInstaller.InstallWorkflow.d__23.MoveNext()
I resolved it by following these steps.
Alternately you can try downloading and installing docker 3.4.0 directly.
Upvotes: 2
Reputation: 1
component communityinstaller.enablefeaturesaction failed: invalid namespace at communityinstaller.installworkflow.d_29.movenext() --- end of stack trace from previous location where exception was thrown --- at system.runtime.exceptionservices.exceptiondispatchinfo.throw() at system.runtime.compilerservices.taskawaiter.handlenonsuccessanddebuggernotification(task task) at communityinstaller.installworkflow.d_23.movenext()
If this is the issue while installing the Docker desktop in windows
Ans:- uncheck the first configuration from the image (i.e 'Install required Windows components for WSL 2')
Upvotes: 0
Reputation: 41
I tried everything (reboot, different versions 2.5, 3.0, 3.3, power, disabling real-time protection). Only increasing timeout helped me:
Upvotes: 2
Reputation: 1
To anyone getting this error:
Component CommunityInstaller.EnableFeaturesAction failed
The fix for me was enabling this service:
Windows Modules Installer
Note I used a tool [1] to do this, but I think you can also just use the normal Services App.
Upvotes: 3
Reputation: 582
Disabling the power service worked for me too.
Upvotes: 22
Reputation: 159
I had the same issue and seemed to start happening after the lasted window update.
I manage to solve the issue by stopping and disabling the "power" (Power management) window service. I did repeat the process two times and seemed to be a consistent issue, at least in my case. Be sure this service is not running, at least in my case it worked, hope this helps.
Some references: - https://github.com/docker/for-win/issues/6091
Upvotes: 4