Windows 10: New system build, new long boot times

So this one I've done a lot of searching on and I haven't found an answer that's worked for me, yet.

Last week I got a new motherboard, processor, and RAM. I installed the new components followed by a fresh install of Windows 10, got it activated, everything seemed good...

Except my boot times. I noticed it during the installation process as well. My POST is normal. As soon as I get to the set of rotating dots, indicating that Windows is booting, it takes several minutes to get to login screen.

My boot drive is a set of Samsung 250GB 950 EVOs running in RAID 0 using the Intel Rapid Storage function on this board. I think it might be related to this, but again, with all the searching I've done I still can't find an answer.

Is there a way to see what's actually happening during the boot process to indicate where the hang occurs?

---




:)

 

Windows 10 update 2 slow boot two pc

I did a clean install on two different notebooks. New HP Envy and old Toshiba Satellite.
Build 10586 boots twice as long. This is VERY upsetting! When you upgrade a system, you expect a mess on your hard drive, registry and etc., and all of this is messing with your boot times and performance.
I get that, BUT this should not happen on a clean install! Get this: my upgraded messy system with a previous build booted up in 6 seconds, it's top of the line HP. Now, with a CLEAN install of the latest build, the same HP boots up in 15 seconds. UEFI settings
were not touched. Drivers are the same. No software loaded yet. This build simply boots twice as long with that double Boot Logo showing up. The same behavior on Toshiba laptop. What is going on?! (((

 

error message when trying to send emails

when trying to send an email from my laptop it gives error message: no email attached, add email or create an association in default programs in settings, how and where do I go to do this.

Samsung laptop

windows 10

HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

Hi BobbyMartin and welcome to Ten Forums!

Why are you running RAID 0? Makes no sense to me. Set it as normal Sata drive and enjoy! It isn't worth some extra sustainable transfer speed over problems you may get into.

Just pick one EVO 850 drive and put system on it.

 

That's one solution, maybe. I haven't tested what the boot speed would be if I were installed on a single drive. This, however, isn't the solution to the issue that I'm looking for.

 

Hi, if you Shift + click Restart and navigate to Startup Settings and then make the appropriate choice, you can get a verbose log of startup activity.

Presumably you're using AHCI for your SSDs, but that alone wouldn't account for the time you're reporting of course.

Also: see event viewer, event id 100.

I have an additional suggestion for tracking boot time. It is via Event 100 in Event viewer. Drill down this chain:
Eventvwr
-->Applications and Service Logs
-->Microsoft
-->Windows
-->Diagnostics - performance
-->Operational
-->Event ID 100<--
Then double click on Event 100 which gives you this small window indicating the boot time.



Then click on the 'Details' tab which gives you all this additional information from which you should be able to determine the process which takes the most time during boot.
From
How to diagnose slow booting or logon in Windows? - Super User

And there's xperf:
Analyzing a Slow Boot with Windows Performance Recorder Helge Klein

 

Woo! Take a look.

Windows has started up:
Boot Duration : 202422ms
IsDegradation : false
Incident Time (UTC) : ‎2016‎-‎04‎-‎29T00:23:41.620299100Z

- EventData BootTsVersion 2 BootStartTime 2016-04-29T00:23:41.620299100Z BootEndTime 2016-04-29T00:28:34.082671900Z SystemBootInstance 8 UserBootInstance 6 BootTime 202422 MainPathBootTime 189022 BootKernelInitTime 14 BootDriverInitTime 102 BootDevicesInitTime 1022 BootPrefetchInitTime 0 BootPrefetchBytes 0 BootAutoChkTime 0 BootSmssInitTime 185732 BootCriticalServicesInitTime 262 BootUserProfileProcessingTime 1283 BootMachineProfileProcessingTime 16 BootExplorerInitTime 446 BootNumStartupApps 26 BootPostBootTime 13400 BootIsRebootAfterInstall false BootRootCauseStepImprovementBits 16384 BootRootCauseGradualImprovementBits 0 BootRootCauseStepDegradationBits 0 BootRootCauseGradualDegradationBits 0 BootIsDegradation false BootIsStepDegradation false BootIsGradualDegradation false BootImprovementDelta 0 BootDegradationDelta 0 BootIsRootCauseIdentified true OSLoaderDuration 462 BootPNPInitStartTimeMS 14 BootPNPInitDuration 1216 OtherKernelInitDuration 126 SystemPNPInitStartTimeMS 1325 SystemPNPInitDuration 59 SessionInitStartTimeMS 1402 Session0InitDuration 1439 Session1InitDuration 774 SessionInitOtherDuration 183518 WinLogonStartTimeMS 187135 OtherLogonInitActivityDuration 141 UserLogonWaitDuration 12775

 

Hi, for comparison my figures (12s or so to lock screen, nominal 36s or so according to Wise:
Mine Yours
BootSmssInitTime
4578 185732

BootNumStartupApps
60 26

BootPostBootTime
48500 13400

BootRootCauseStepImprovementBits
0 16384

BootIsRootCauseIdentified
false true

SessionInitOtherDuration
3783 183518

WinLogonStartTimeMS
6593 187135

I've just picked out the significant differences.

I'm afraid interpreting that is either up to you, or anyone who can join this thread and is familiar with these... I've never done so..

For info ref. Critical, Warning etc:
Diagnostics-Performance log Event 100 - Critical, Error, or Warning - when and why?

 

Time to lock screen is about 3m18s.

 

I was reading online about a similar issue to yours ....this other person when he set backups on other drives would cause the bootup time to be more than 2mins .....reformatting the backup drives seemed top solve the issue ....however ....don't go doing this without putting your backups somewhere else. Think it was related to VSS. Try unplugging all the extra drives leaving just the OS. If your boot increases then I guess you have the same/similar issue.

 

Doesn't look like that's a solution either. In the link below you'll find the bootlog. Maybe someone can make more sense of it that I can.

Online Notepad - Anotepad.com

 

Only other thing I can suggest at present is install windows performance toolkit from windows ADK and run this line xbootmgr -trace boot -prepSystem -verboseReadyBoot , it will even ive you a better idea of what the problem is in the trace logs. I used the tool on my win 10 system and reduced my boot time by 52 seconds. If readyboot stops repopulating after using this tool then copy contents of readyboot to a temp folder, copy rest of contents to another temp folder delete prefetch folder and reboot, then replace all the optimized files back to prefetch. Its unlikely you will have to do this ...its just my folder lost its permissions after i defragged.

 

Unfortunately it looks as if this will remain unresolved for now.

 

If you really want to stick with RAID setup, then check your bios settings. All that is related to hardware.

I'm sure, that you checked internet for similar problems (and there are plenty) for you Motherboard. I would like to point out two of them:

DRCT Direct key should be set to disabled, if you don't have appropriate case. Discussed here.

and one other suggestion:

 

Already had DRCT turned off. Just went ahead and tried all these settings with no change at all in the boot up time, unfortunately.