Restart Boot Takes a long time More than 5 mins

[Geoff S]

When I restart the Initial (BIOS) Screen comes on Instantly. then I see the 4 Blue windows and the circle of dots going round and round and then after about 5 mins another picture screen comes on. I then have to hit Enter and only then does the login screen come on. It then goes into Win 10. I have the latest updates installed.

[Train]

I have a silly Dell Optiplex 755 that does something simuliar. But seemed to take forever to boot to Windows.
Installed a SSD now I have the 20 seconds of BIOS and 15 seconds later Window or AntiX is booted up.

Post the make and model of that computer.

From a 5200 rpm hdd [3 minute boot up] to a SSD [15 seconds] is quite a difference. And talked a client into updating from 512 MB of ram to 2 GB and from a 4200 rpm hdd to a 7200 rpm hdd. A PATA rig.
Talk about a happy guy!!!

[Midknyte]

Did you check Event Viewer for errors? There may be services trying to run in the background.

Was this an upgrade or a clean install? If it was an upgrade, check for updated drivers.

[Geoff S]

I have a HP Compaq 8200 Elite SFF with an Intel I5 2400 CPU @ 3.1GHz with 4GB of memory, a HD with 423GB free of 465GB. This was an upgrade from Win7, I have not checked the Event viewer or updated the drivers. I would certainly buy a SSD if you think that would speed things up. How would I copy Everything from my Old HDD to the new SSD and make that my primary boot drive.

[Train]

You should have a 7200 rpm SATA hdd.
http://h20564.www2.hp.com/hpsc/doc/p...r_na-c02781693
Check event viewer first for red X items.

Drivers and hold off for a bit.
http://h20564.www2.hp.com/hpsc/swd/p...ts.oid=5037932

[Midknyte]

This was an upgrade from Win7, I have not checked the Event viewer or updated the drivers.

Definitely do both. If there are services hanging in the background, you can try setting them to manual or automatic (delayed start).

I've seen weird stuff happen with upgrades. One was an HP that sat at a black screen for about a minute after the initial "Welcome" screen. Turns out it was the AMD/ATI video drivers. I'd update the video and chipset drivers first.

[Geoff S]

The event viewer does show Red errors, how do I correct them. How do I set services running in the background to manual or Automatic.
How do I upgrade drivers?

[Train]

Drivers, use the windows 8 drivers from my link in Post #5

BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html

And post what if finds.

[Midknyte]

The event viewer does show Red errors, how do I correct them.

You need to look at the specific error code and message. Each error is different. If you post them, we might be able to help.

For services, you need to open Services from Control Panel > Administrative Tools
You'd need to right-click on the service, click Properties, then change the Startup type

[Geoff S]

Downloaded drivers from the Website on Post # 5, but when I tried to install them, was told that the driver ver. I had now was more reacent than the one I was trying to install.
How do I post the Event viewer?

[Geoff S]

What I would like to do is clear the entire log, (how do I do this?). Then reboot the PC and then post a copy of the log of the event viewer just during the start up. Would like this forum to look at the log and tell me what to fix.

[Geoff S]

I cleared the event log and rebooted I am going to attach a Print screen of the event log
event.gif

[Midknyte]

We can't do much just looking at the list. You need to open the events with the red mark. There should be a "Copy" button. You can paste the error message text after that.
Or post a screenshot of the bad event.

I don't see Windows 10 drivers listed on the HP site. You'd need to determine the make/model of your video card and chipset, and then find Win10 drivers. You can try Speccy to get that info.
https://www.piriform.com/speccy

[Geoff S]

Here are the error messages in Red

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 12/27/2016 12:32:57 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: GEOFFS-I5-WIN10\sriwa
Computer: Geoffs-I5-Win10
Description:
The server {37998346-3765-45B1-8C66-AA88CA6B20B8} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-12-27T17:32:57.974003300Z" />
<EventRecordID>6130</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="5776" />
<Channel>System</Channel>
<Computer>Geoffs-I5-Win10</Computer>
<Security UserID="S-1-5-21-1644789618-2606114323-4026453079-1001" />
</System>
<EventData>
<Data Name="param1">{37998346-3765-45B1-8C66-AA88CA6B20B8}</Data>
</EventData>
</Event>
-----------------------------------------------------------------------------------------------
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 12/27/2016 12:28:27 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: Geoffs-I5-Win10
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-12-27T17:28:27.730669700Z" />
<EventRecordID>6122</EventRecordID>
<Correlation />
<Execution ProcessID="912" ThreadID="976" />
<Channel>System</Channel>
<Computer>Geoffs-I5-Win10</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}</Data>
<Data Name="param5">{F72671A9-012C-4725-9D2F-2A4D32D65169}</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
-----------------------------------------------------------------------------------------
-Log Name: System
Source: MEIx64
Date: 12/27/2016 12:26:45 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Geoffs-I5-Win10
Description:
Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x00040185, FWSTS1: 0x10440006).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MEIx64" />
<EventID Qualifiers="49159">3</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-12-27T17:26:45.949101800Z" />
<EventRecordID>6083</EventRecordID>
<Channel>System</Channel>
<Computer>Geoffs-I5-Win10</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0x00040185</Data>
<Data>0x10440006</Data>
<Binary>000000000300280000000000030007C0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>--------------------------------------------------------------------------------------------

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 12/27/2016 12:24:06 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: GEOFFS-I5-WIN10\sriwa
Computer: Geoffs-I5-Win10
Description:
The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-12-27T17:24:06.296634800Z" />
<EventRecordID>6054</EventRecordID>
<Correlation />
<Execution ProcessID="904" ThreadID="9780" />
<Channel>System</Channel>
<Computer>Geoffs-I5-Win10</Computer>
<Security UserID="S-1-5-21-1644789618-2606114323-4026453079-1001" />
</System>
<EventData>
<Data Name="param1">{9BA05972-F6A8-11CF-A442-00A0C90A8F39}</Data>
</EventData>
</Event>
----------------------------------------------------------------------------------------------------------------------------

[Midknyte]

For the first and second errors looks like DCOM problems. You need to determine which app is calling DCOM.
https://www.microsoft.com/technet/su...DCOM&LCID=1033
https://www.microsoft.com/technet/su...16&EvtSrc=DCOM

Unless you are actually using the Intel Management Engine Interface, I would just disable the device in Device Manager.
https://answers.microsoft.com/en-us/...2-849daadb885c