<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	 xmlns:media="http://search.yahoo.com/mrss/" 
	>
<channel>
	<title>
	Comments on: Fix Windows Services will not start in Windows 11	</title>
	<atom:link href="https://www.thewindowsclub.com/windows-services-will-start/feed" rel="self" type="application/rss+xml" />
	<link>https://www.thewindowsclub.com/windows-services-will-start</link>
	<description>TheWindowsClub covers authentic Windows 11, Windows 10 tips, tutorials, how-to&#039;s, features, freeware. Created by Anand Khanse, MVP.</description>
	<lastBuildDate>Sat, 26 Apr 2025 18:00:28 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: David Stroud		</title>
		<link>https://www.thewindowsclub.com/windows-services-will-start#comment-63899</link>

		<dc:creator><![CDATA[David Stroud]]></dc:creator>
		<pubDate>Fri, 18 May 2018 18:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thewindowsclub.com/?p=89565#comment-63899</guid>

					<description><![CDATA[I get the message saying the same thing trying to run the service.msc as well. It started last night, and I just logon to my computer, and waiting did not fixed the issue.]]></description>
			<content:encoded><![CDATA[<p>I get the message saying the same thing trying to run the service.msc as well. It started last night, and I just logon to my computer, and waiting did not fixed the issue.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jessica Harper		</title>
		<link>https://www.thewindowsclub.com/windows-services-will-start#comment-63816</link>

		<dc:creator><![CDATA[Jessica Harper]]></dc:creator>
		<pubDate>Sat, 12 May 2018 20:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thewindowsclub.com/?p=89565#comment-63816</guid>

					<description><![CDATA[I know how to access windows services to enable or disable. I can&#039;t get onto my administrator account in order to do so. It also doesn&#039;t work in safe mode. I don&#039;t know what to do. Please help!]]></description>
			<content:encoded><![CDATA[<p>I know how to access windows services to enable or disable. I can&#8217;t get onto my administrator account in order to do so. It also doesn&#8217;t work in safe mode. I don&#8217;t know what to do. Please help!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Noremacam		</title>
		<link>https://www.thewindowsclub.com/windows-services-will-start#comment-53301</link>

		<dc:creator><![CDATA[Noremacam]]></dc:creator>
		<pubDate>Fri, 17 Jun 2016 17:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thewindowsclub.com/?p=89565#comment-53301</guid>

					<description><![CDATA[I found a Windows 10 specific issue where most .Net based services
 would fail on startup, but could be started later manually just fine. 
For some reason, services that are written in .NET take longer to start 
in Windows 10. By default, if a service takes longer than 30 seconds to 
start without responding, the service is terminated by Windows.

I was able to change that behavior to 60 seconds in the registry. Go to:

HKLMSYSTEMCurrentControlSetControl

If it doesn&#039;t already exist, create a DWORD (32-bit) key called 
&quot;ServicesPipeTimeout&quot;(minus quotes). Set its value to 60000(in decimal).
 This correlates to 60 seconds in milliseconds. 

This fixed the issue for us on multiple machines. Let me know if this
 helps. Unfortunately, I still do not know why .NET services take so 
long to start that they get terminated. However, I feel this is a 
Microsoft bug, and not necessarily anything us users are doing wrong...]]></description>
			<content:encoded><![CDATA[<p>I found a Windows 10 specific issue where most .Net based services<br />
 would fail on startup, but could be started later manually just fine.<br />
For some reason, services that are written in .NET take longer to start<br />
in Windows 10. By default, if a service takes longer than 30 seconds to<br />
start without responding, the service is terminated by Windows.</p>
<p>I was able to change that behavior to 60 seconds in the registry. Go to:</p>
<p>HKLMSYSTEMCurrentControlSetControl</p>
<p>If it doesn&#8217;t already exist, create a DWORD (32-bit) key called<br />
&#8220;ServicesPipeTimeout&#8221;(minus quotes). Set its value to 60000(in decimal).<br />
 This correlates to 60 seconds in milliseconds. </p>
<p>This fixed the issue for us on multiple machines. Let me know if this<br />
 helps. Unfortunately, I still do not know why .NET services take so<br />
long to start that they get terminated. However, I feel this is a<br />
Microsoft bug, and not necessarily anything us users are doing wrong&#8230;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
