A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Unusually Long Time to Boot Windows 10



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old August 13th 15, 02:51 PM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10


Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill
Ads
  #2  
Old August 13th 15, 04:10 PM posted to alt.comp.os.windows-10
Paul
external usenet poster
 
Posts: 18,275
Default Unusually Long Time to Boot Windows 10

Bill wrote:
Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill


You can check "boottime" this way.

http://www.ghacks.net/2011/08/09/ana...ce-of-windows/

Or, use the Windows Performance Toolkit. Do *not* issue
a xbootmgr command, unless you've saved all your open files,
closed all the programs and so on. Xbootmgr can cause immediate
shutdown and reboot, to analyze the computer, and it may come
as a surprise the first time you try it. There is graphical output
available, so you can examine that to see if booting is finished
or not, and some application level thing is at work. Allow the
setup to trace stuff, before getting into a rush right after
boot, to collect your trace file. If your system is hosed for
four minutes normally, then "hands off keyboard" for four minutes
before stopping the trace by messing around with the Performance
Toolkit commands. I nearly truncated my boot trace when I ran one,
by being in a rush to get in there and look :-)

http://www.msfn.org/board/topic/1402...resume-issues/

Paul
  #3  
Old August 13th 15, 08:34 PM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10

OK, when I opened "Event Viewer", there were an incredible 1, 660
events but NONE of them with " a white X in a red circle"! Of the
1,660 events, they all were dated around the same date of my Windows
10 installation and they were either an explanation mark inside a
yellow diamond saying "Warning" or an explanation mark inside a red
circle saying "Error". The "Source" of these were either Service
Control Manager, TaskScheduler, Wininit, CAPI2, Device Setup Manager,
& Apps.

The Device Setup Manager may have been caused due to a problem I had
getting my Epson printer to work, but that is now OK.

Bill

On Thu, 13 Aug 2015 14:59:10 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 06:51:54 -0700, Bill wrote:


Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill


Two things to look at....

You could have one or more services which are hanging at start-up. You would examine your Event log to
determine if this is happening Once you have event viewer open, expand "custom views" and select
"Administrative". Now you want to look for white X's in red circles, those are errors, open those and report
back on what you are finding.

See: http://www.isunshare.com/windows-10/...indows-10.html


You can also try booting into safe mode and see how long that takes. See:

http://www.7tutorials.com/4-ways-boo...ode-windows-10

  #4  
Old August 13th 15, 09:14 PM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10

The most recent one is today ("!" in red circle) has:
"A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service."

Another dtd today ("!" inside yellow triange has:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\DispatchRecoveryTasks definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

Another dtd 7 Aug says:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\OCURActivate definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

I could go on!

Bill


On Thu, 13 Aug 2015 19:50:57 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 12:34:25 -0700, Bill wrote:

OK, when I opened "Event Viewer", there were an incredible 1, 660
events but NONE of them with " a white X in a red circle"! Of the
1,660 events, they all were dated around the same date of my Windows
10 installation and they were either an explanation mark inside a
yellow diamond saying "Warning" or an explanation mark inside a red
circle saying "Error". The "Source" of these were either Service
Control Manager, TaskScheduler, Wininit, CAPI2, Device Setup Manager,
& Apps.

The Device Setup Manager may have been caused due to a problem I had
getting my Epson printer to work, but that is now OK.

Bill

On Thu, 13 Aug 2015 14:59:10 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 06:51:54 -0700, Bill wrote:


Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill

Two things to look at....

You could have one or more services which are hanging at start-up. You would examine your Event log to
determine if this is happening Once you have event viewer open, expand "custom views" and select
"Administrative". Now you want to look for white X's in red circles, those are errors, open those and report
back on what you are finding.

See: http://www.isunshare.com/windows-10/...indows-10.html


You can also try booting into safe mode and see how long that takes. See:

http://www.7tutorials.com/4-ways-boo...ode-windows-10



Oops!!! I mistyped, you are looking for the exclamation mark in the red circle! My bad..... slapping right
hand with left hand.........

Start opening those errors and see if you can copy and paste the most common, recent ones here.

  #5  
Old August 13th 15, 09:20 PM posted to alt.comp.os.windows-10
Paul
external usenet poster
 
Posts: 18,275
Default Unusually Long Time to Boot Windows 10

Bill wrote:
The most recent one is today ("!" in red circle) has:
"A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service."

Another dtd today ("!" inside yellow triange has:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\DispatchRecoveryTasks definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

Another dtd 7 Aug says:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\OCURActivate definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

I could go on!

Bill


If you go from Win7 (Media Center) to Win10, the
Win10 installer doesn't remove all the Task Scheduler
stuff for the now-no-longer-running Media Center.

http://www.tenforums.com/performance...r-entries.html

Paul
  #6  
Old August 14th 15, 12:22 AM posted to alt.comp.os.windows-10
Mike Swift
external usenet poster
 
Posts: 175
Default Unusually Long Time to Boot Windows 10

In article , Bill
writes
Since upgrading to Windows 10, I've noticed that it takes 4+ minutes to load
(start button to "ready to work"). Anyone else experienced this? Never had
this problem with Windows 7!


My start up isn't too bad but a restart takes ages, strange.

Mike

--
Michael Swift We do not regard Englishmen as foreigners.
Kirkheaton We look on them only as rather mad Norwegians.
Yorkshire Halvard Lange
  #7  
Old August 14th 15, 01:05 AM posted to alt.comp.os.windows-10
Paul
external usenet poster
 
Posts: 18,275
Default Unusually Long Time to Boot Windows 10

Mike Swift wrote:
In article , Bill
writes
Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load
(start button to "ready to work"). Anyone else experienced this? Never
had
this problem with Windows 7!


My start up isn't too bad but a restart takes ages, strange.

Mike


Do you have things set to "Clean the pagefile" at
shutdown ?

If your pagefile is Mighty Big, this takes a Mighty Long Time.

Paul
  #8  
Old August 14th 15, 03:37 AM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10

Norman,

I'm attaching 3 of the Error items but there are many!

1. The Net.Tcp Listener Adapter service depends on the Net.Tcp Port
Sharing Service service which failed to start because of the following
error:
The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it.

2. Cryptographic Services failed while processing the OnIdentity()
call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft
Link-Layer Discovery Protocol.

System Error:
Access is denied.


3. A timeout was reached (30000 milliseconds) while waiting for the
Net.Pipe Listener Adapter service to connect.

Note that these examples mean absolutely nothing to me! Where they
came from or what they do is a mystery to me. And remember they are
just 3 examples but I've noticed that many are the same Error message!

BTW, I've clocked the startup time 4X and the average is about 3
minutes!

Bill


On Thu, 13 Aug 2015 21:49:02 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 13:14:38 -0700, Bill wrote:

The most recent one is today ("!" in red circle) has:
"A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service."

Another dtd today ("!" inside yellow triange has:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\DispatchRecoveryTasks definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

Another dtd 7 Aug says:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\OCURActivate definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

I could go on!

Bill


On Thu, 13 Aug 2015 19:50:57 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 12:34:25 -0700, Bill wrote:

OK, when I opened "Event Viewer", there were an incredible 1, 660
events but NONE of them with " a white X in a red circle"! Of the
1,660 events, they all were dated around the same date of my Windows
10 installation and they were either an explanation mark inside a
yellow diamond saying "Warning" or an explanation mark inside a red
circle saying "Error". The "Source" of these were either Service
Control Manager, TaskScheduler, Wininit, CAPI2, Device Setup Manager,
& Apps.

The Device Setup Manager may have been caused due to a problem I had
getting my Epson printer to work, but that is now OK.

Bill

On Thu, 13 Aug 2015 14:59:10 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 06:51:54 -0700, Bill wrote:


Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill

Two things to look at....

You could have one or more services which are hanging at start-up. You would examine your Event log to
determine if this is happening Once you have event viewer open, expand "custom views" and select
"Administrative". Now you want to look for white X's in red circles, those are errors, open those and report
back on what you are finding.

See: http://www.isunshare.com/windows-10/...indows-10.html


You can also try booting into safe mode and see how long that takes. See:

http://www.7tutorials.com/4-ways-boo...ode-windows-10


Oops!!! I mistyped, you are looking for the exclamation mark in the red circle! My bad..... slapping right
hand with left hand.........

Start opening those errors and see if you can copy and paste the most common, recent ones here.



Bill, I would restart your machine, let it fully start up, go back to the administrative log (under custom
view) and look only for Errors (not warnings) which have occurred during the most recent boot sequence.

Double click each of the errors and find the "Copy" command and post the full context of each error
(exclamation in red circle) as a reply. Odds are it is a combination of one or more of these errors which is
causing your slow boot process.

We can worry about the warnings later.

  #9  
Old August 14th 15, 03:52 AM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10

Paul,

I can't say that I've things set to "Clean the pagefile" at shutdown
since I don't know how to do it! I've looked at "Settings" but can't
find that subject. Please advise!

Bill

On Thu, 13 Aug 2015 20:05:16 -0400, Paul wrote:

Mike Swift wrote:
In article , Bill
writes
Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load
(start button to "ready to work"). Anyone else experienced this? Never
had
this problem with Windows 7!


My start up isn't too bad but a restart takes ages, strange.

Mike


Do you have things set to "Clean the pagefile" at
shutdown ?

If your pagefile is Mighty Big, this takes a Mighty Long Time.

Paul

  #10  
Old August 14th 15, 04:03 AM posted to alt.comp.os.windows-10
Paul
external usenet poster
 
Posts: 18,275
Default Unusually Long Time to Boot Windows 10

Bill wrote:
Paul,

I can't say that I've things set to "Clean the pagefile" at shutdown
since I don't know how to do it! I've looked at "Settings" but can't
find that subject. Please advise!


This article isn't for Win10, but have a look in regedit anyway,
and see if it is present in Windows 10.

https://support.microsoft.com/en-us/kb/314834

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
ClearPageFileAtShutdown DWORD === 1 means waste time clearing pagefile
0 means shut down quicker

Clearing the pagefile is for people who are extremely worried
about password security, and the possibility that a password
ended up in memory, got swapped out to pagefile, and the
pagefile still contains that value. A clever individual with
physical access to the machine, could copy the pagefile
for study at their leisure.

HTH,
Paul
  #11  
Old August 14th 15, 11:05 AM posted to alt.comp.os.windows-10
Mike Swift
external usenet poster
 
Posts: 175
Default Unusually Long Time to Boot Windows 10

In article , Paul writes

Do you have things set to "Clean the pagefile" at
shutdown ?

If your pagefile is Mighty Big, this takes a Mighty Long Time.


Probably not, I haven't seen that one, how would I set that please.

Oops, just seen your later reply, thanks.

Mike

--
Michael Swift We do not regard Englishmen as foreigners.
Kirkheaton We look on them only as rather mad Norwegians.
Yorkshire Halvard Lange
  #12  
Old August 14th 15, 02:29 PM posted to alt.comp.os.windows-10
Bill[_39_]
external usenet poster
 
Posts: 65
Default Unusually Long Time to Boot Windows 10

Norman,

Before I do anything, let me tell you that my installation went
smoothly except that it failed to recognize my Epson R320 printer and
I finally got that resolved. Other than that, no other issues!

As far as reverting back to Win7, the only real issue I have with
Win10 is the startup time and might just have to live with it pending
the outcome of your suggestions!

Bill

On Fri, 14 Aug 2015 12:46:22 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 19:37:33 -0700, Bill wrote:

Norman,

I'm attaching 3 of the Error items but there are many!

1. The Net.Tcp Listener Adapter service depends on the Net.Tcp Port
Sharing Service service which failed to start because of the following
error:
The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it.

2. Cryptographic Services failed while processing the OnIdentity()
call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft
Link-Layer Discovery Protocol.

System Error:
Access is denied.


3. A timeout was reached (30000 milliseconds) while waiting for the
Net.Pipe Listener Adapter service to connect.

Note that these examples mean absolutely nothing to me! Where they
came from or what they do is a mystery to me. And remember they are
just 3 examples but I've noticed that many are the same Error message!

BTW, I've clocked the startup time 4X and the average is about 3
minutes!

Bill


On Thu, 13 Aug 2015 21:49:02 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 13:14:38 -0700, Bill wrote:

The most recent one is today ("!" in red circle) has:
"A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service."

Another dtd today ("!" inside yellow triange has:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\DispatchRecoveryTasks definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

Another dtd 7 Aug says:
"Task Scheduler service found a misconfiguration in the NT
TASK\Microsoft\Windows\Media Center\OCURActivate definition.
Additional Data: Error Value: %SystemRoot%\ehome\ehPrivJob.exe."

I could go on!

Bill


On Thu, 13 Aug 2015 19:50:57 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 12:34:25 -0700, Bill wrote:

OK, when I opened "Event Viewer", there were an incredible 1, 660
events but NONE of them with " a white X in a red circle"! Of the
1,660 events, they all were dated around the same date of my Windows
10 installation and they were either an explanation mark inside a
yellow diamond saying "Warning" or an explanation mark inside a red
circle saying "Error". The "Source" of these were either Service
Control Manager, TaskScheduler, Wininit, CAPI2, Device Setup Manager,
& Apps.

The Device Setup Manager may have been caused due to a problem I had
getting my Epson printer to work, but that is now OK.

Bill

On Thu, 13 Aug 2015 14:59:10 +0000, Stormin' Norman
wrote:

On Thu, 13 Aug 2015 06:51:54 -0700, Bill wrote:


Since upgrading to Windows 10, I've noticed that it takes 4+ minutes
to load (start button to "ready to work"). Anyone else experienced
this? Never had this problem with Windows 7!

Bill

Two things to look at....

You could have one or more services which are hanging at start-up. You would examine your Event log to
determine if this is happening Once you have event viewer open, expand "custom views" and select
"Administrative". Now you want to look for white X's in red circles, those are errors, open those and report
back on what you are finding.

See: http://www.isunshare.com/windows-10/...indows-10.html


You can also try booting into safe mode and see how long that takes. See:

http://www.7tutorials.com/4-ways-boo...ode-windows-10


Oops!!! I mistyped, you are looking for the exclamation mark in the red circle! My bad..... slapping right
hand with left hand.........

Start opening those errors and see if you can copy and paste the most common, recent ones here.


Bill, I would restart your machine, let it fully start up, go back to the administrative log (under custom
view) and look only for Errors (not warnings) which have occurred during the most recent boot sequence.

Double click each of the errors and find the "Copy" command and post the full context of each error
(exclamation in red circle) as a reply. Odds are it is a combination of one or more of these errors which is
causing your slow boot process.

We can worry about the warnings later.


Bill, it sounds like you have some fairly extensive issues with your system.

When you open an event, there is an option that allows you to copy the full event which will include event id
numbers and source information.

That said, let's start by disabling two of the services mentioned in the errors you listed above.

Read "Option one" of this article:

http://www.tenforums.com/tutorials/4...a.html#option1

Then following the instructions, find the following two services in your service manager and set them to
"disabled " After doing so, reboot the system and see if there is any boot performance improvement.

DISABLE:

Net.Tcp Listener Adapter

Net.Tcp Port Sharing

I have to say, I think your "upgrade" went very poorly and I would personally consider reverting to your prior
operating system if that was working better.

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 01:41 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.