Windows 10: 13 min to desktop, can anyone help speed it up?

Fingers crossed I have uploaded the start up event log, if not then I will have to find out how to do it!
Anyway, as the title states today it took from 16:03:31 when I started to 16:16:43 to arrive at my desktop. Sometimes it is quicker but often as not this seems to be about normal.
The log shows many 'Errors' and I have tried to see if Google Help can point me to a way to correct the errors but to be honest the majority are way beyond my ability to understand, my thinking better 13min than no PC!!

Can someone have a look through and see if there is anything I can attempt that would help? I have tried sfc, CCleaner files and reg etc but no improvement.

I thought about a repair install so as not to lose any programs or files, I have downloaded the ISO file listed as Redstone1 with build 14393 693 Version 1607 which is as shown on my 'About' screen.
Would the repair install help with this or would I be making matters worse?

There a number of drives attached, mostly by USB which I use for backups and music files and wonder if checking the health of these is slowing up the start, and if so can I turn off the checking at start up?

Thanks for reading this far *Smile

Could not upload the evtx file so saved as a txt file, hope that's okay.

Alan.
Startup 08 03 17 txt.txt

:)

 

Can anyone help me with this..? :\ It says upgrade to windows 10 Home failed...and the windows 10 app says "Notify me when ready"..

Hello,

Thank you for your interest in Windows 10.

I would appreciate, if you can provide us the following information to help us understand the issue better?

• Are you getting any error code on your system when installation fails?

I would suggest you to follow steps provided by Andre Da Costa from the link given below and check.

Refer:

How to: A list of things to do if Windows 10
Setup fails.

How to: Troubleshoot common Setup and Stop Errors
during Windows 10 Installation

Hope this information is helpful. Please do let us know if you need further assistance with Windows, we’ll be glad to assist you.

 

Can anyone help me with this..? :\ It says upgrade to windows 10 Home failed...and the windows 10 app says "Notify me when ready"..

Can anyone help me with this..? :\ It says upgrade to windows 10 Home failed...and the windows 10 app says "Notify me when ready"..

 

Hi, start with two very basic simple steps:
1. Download and run CrystalDiskinfo and post the single Window result (Blue is good).
Use this to check each of your drives (listed across the top- click on each to see report on SMART params).

2. Assuming your PC's internal drive(s) is/are good:
Do a clean boot with no USB devices connected.
Clean Boot - Perform in Windows 10 to Troubleshoot Software Conflicts
(1st part only).

How long does this take?

If the boot time is significantly reduced, then try booting normally again, but again, without USB devices connected.

3. History.
For how long has it taken your PC this long to boot? Has there been a sudden increase in boot time? If so, can you think of nay change or update made around that time?

How long a boot time have you experienced when all seemed well?

4. What type of disk is your system disk? HDD? SSHD? SSD?

Comment:
An in-place upgrade repair install will leave all programs and most settings as they are.
If you have a problem related to
a. hardware
b. installed programs or drivers
c. external devices
it will not help.

If your system drive is fine and Windows is corrupted such that other repair techniques don't help, it can be useful.

You comment you have used sfc /scannow - can you confirm the report was that no problems were found?

Could you explain

please?

 

Thanks for your reply. I have run CrystalDiskInfo although Malwarebytes was not at all happy and kept blocking it. Anyway all drives were Blue as were all the results so looks like all drives are Good, odd thing was the drive it was installed on, in my case 'I', was not scanned or noted on the result as you will note . I have shown the result below:




I have now printed off the Clean Boot tutorial and that will be my next job, probably tomorrow. The printer decided it would not play ball so in the end I had to turn it off and try again, still no print so I shutdown the PC and the printer left for about 10 min then rebooted both, the PC booted up pretty quick, didn't time it but it was much faster.

Been getting worse since adding two WD Passport 1TB USB drives but that was some time ago; I guess around 2 months plus and the increase in boot time has been gradual, usually on 1st boot of the day like today and subsequent boots same day seem much quicker to get to the login screen.

All HDD disks in the PC, don't know the types in the Passport drives.

sfc/scannow found no errors

'Reg' is registry cleaner used in CCleaner.

I will have some more time tomorrow and will report here my results following your advice.

Thanks again.
Alan.

 

Hi trapper you can also use defraggler and it will also give a "health" readout. It should be able to read your I drive that crystaldisk couldn't see.

 

Having a look at what happens, and when, I think that a clean boot should at least help a bit.
If a clean boot doesn't help, download & install HDTune and perform a benchmark.
Make sure that you post a screenshot with the following details when the benchmark is finished.

 

Thanks for your suggestions, much appreciated.

I have completed the W10 Clean Boot as advised, all went well until the last part where System Configuration was ‘Not Responding’ so did not arrive at the option to restart now or later. After waiting about 5
Min then I hit the reboot button and breathed a sigh of relief as the PC rebooted to the desktop.

Here’s how it went:
I ‘Shutdown’ between each restart so the PC was dead each time.

I have taken the start time from the Event Log as Kernel General which give the time of starting.
I have taken the end time from the Event Log as Winlogon so times listed are between these.

Disconnected ALL external (USB) drives. All internal drives connected. Start to end time 56 seconds.

• With I: drive connected: Start to end time 1.93min
• With I: and M: WD Passport 2TB drive Start to end time 6.57min
• With I: But M: removed Start to end time 1.21min
• With I: and H: WD Passport (A)1TB Start to end time 1.71min
• With I:+H; and J: WD Passport (B) 1TB Start to end time 1.16min
• With I:+H:+J: and M: WD passport 2TB Start to end time 5.96min
• With I:+H:+J:+M: and K: HD LUX 3 1TB Start to end time 6.47min
• With I:+H:+J:+K but M: removed Start to end time 1.57min.

It would seem the problem is down to my 2TB WD Passport M: drive, having this connected drastically increases the boot time but not the 13min of the other morning!
Event log reports all drives as healthy with drive letters except one with this description:

Volume \\?\Volume{ef929e94-0000-0000-0000-901a7d000000} (\Device\HarddiskVolume2) is healthy. No action is needed. Is this the W10 reserved partition?

Both the Event Log and CrystalFileInfo reported the Passport M drive as healthy, so any idea what would cause this drive to slow up the start?

 

Do you use the same connection for each drive when testing?

 

Yes I do, the WD Passport 2TB has been in use for a few years, with either XP or Win 7 Pro. Do you suggest I swop them around?

 

You could do a couple of checks on it:
Crystal Diskmark
(to test data rate which is more likely to show something)
- and repeat that with the drive on a different connection/different cable...

and for the sake of it
Macrorit Diskscanner
although a surface check is unlikely to be the issue here.

 

Two scan results here, not sure what it all means though.
First scan on M: Drive connected on usual USB lead to PC.




Next scan on M: connected to a different USB lead to PC (Previously connected to H: Drive)



Some very different numbers.

Booted with the M: Drive connected to a different USB lead to the PC (Previously connected to H: Drive) the start to logon screen in Event Viewer now times at 2.05min. About 1/3 of the time on its usual lead as my previous post..
I have not swopped the USB connection points on the MB. I will try one of the other WD drives on the same lead as the M: Drive was on when the startup was slow to see if that makes any difference.
This is getting complicated!!

 

Getting closer. I don't know if you're using USB2 or 3- from your figures I guess USB2.

You can try a different disk on the same (apparently slower) USB connection and on a different one to get some figures to compare with those you've posted.

Now you can see a clear difference -a process of elimination should help you identify USB port/ cable / drive.

I would recommend you only have one USB disk connected at a time while you do this.

Note: clarity in terms: and a useful tip you may already know:
Booted with the M: Drive connected to a different USB lead to the PC (Previously connected to H: Drive)

This is rather difficult to interpret.Why?1. As you know, when a drive is connected to a PC it is normally allocated the next available letter. Without the user taking specific action, external drives are not allocated a fixed letter, nor are particular USB ports.
2. It is possible to effectively assign an external drive a fixed drive letter- provided the assigned drive letter is not in use when that drive is next connected. This is done in Disk Management by reallocating the drive to a specific letter- say W - far from any letters likely to be used by plugging in devices randomly. This is very useful for a backup drive which is connected and disconnected, for example.

Assuming you have not used the method in (2) I therefore interpret your statement as possibly meaning:
I booted with the suspect USB drive allocated the drive letter M connected using a different USB lead which had previously been used for the drive allocated drive letter H.
or
I booted with the suspect USB drive allocated the drive letter M connected using a different USB lead. The M drive had previously been connected to the USB port to which the drive allocated drive letter H had been connected.

 

One thing you can do is right click on taskbar and select task manager. Click on the startup tab. Please list all the enabled entries.

 

Correct.

Youv'e put that much clearer than I did *Wink. I have selected the drive letters so I know which is which when I come to backup swaps and do not want to get out of sync.

I have yet to try another USB drive connected to the original M lead connected to the original USB port at the rear of the PC.

This morning I booted with only the M drive connected to the original M lead connected to the original USB port at the rear of the PC. this returned a start up time of 1.51min, excellent!
Anyway I ran the CrystalMark on the M drive as above, result showed as below:




I then connected the M drive to a front USB port and connected with the lead from my WD Passport J drive. then ran CrystalMark again, result showed as below:




No idea what the above means, sorry....
Blows my theory about the M drive causing the problem, with a startup today of 1.51min!!

Task Manager startup as below.




Thank you for your help.