New
#11
You can do both. But if you feel you can confidently figure it out. Of course it would help us see what might be causing the issue as well.
Ok, I already did it but I think it's trolling me... I did a boot trace and it powered down and booted up faster, I rebooted normally but it took ages again. I did a shutdown trace this time and again, it powered down almost immediately and booted up a bit faster.
I looked at the graphs but I'm not sure how to tell if something's out of place, I'll upload some graphs that I think might help... If that's not enough I'll try to upload the ETL file somewhere (any recommendations?).
Well from the first image I see clr_optmization taking a lot of time. From my search that involves the .net framework. Do you have the latest version of .netframework. You can see that in your programs and features.
I have these two:
-Microsoft .NET Framework 4 Client Profile v4.0.30319
-Microsoft .NET Framework 4 Extended v4.0.30319
I'm not sure if those are the latest though. I checked Windows Update and there aren't any updates available :P.
Also that wpdbusenum stop has something to do with Windows Media Player syncing to a usb flash drive over 4GB. You can disable that under msconfig->Services->Portable Device Enumerator Service.
Also take a look at this and see if this helps.
What is mscorsvw.exe and why is it eating up my CPU? What is this new CLR Optimization Service? - David Notario's WebLog - Site Home - MSDN Blogs
Also when you boot can you load up the taskmanager and see if anything is using a high cpu count?
And in this thread on #8 do you notice this at all.
How to disable mscorsvw.exe from startup
The thing is that once my Desktop shows, everything works just fine, my programs load as usual and with no delay and if I check my task manager it doesn't show anything weird, the problem is going from Welcome Screen to Desktop (and just the first time after boot-up I might add).
I checked that thread but I don't even have mscorsvw.exe in my task manager. Still tried the ngen.exe command but it said "All compilation targets are up to date".