MagicAndre1981

I think the storport.sys is used by the AHCI driver.

my last post is gone. The latest trace shows HDD issues ("Depth queue at Init" is over 100) which explains the storport.sys issues you see.

my last post is gone (for what ever reason). The trace is corrupted/incomplete and you should run a new boot trace.

do you had to recover the DB? I see all posts from yesterday evening are gone.

the .etl file shows 1 spike caused by the NDIS.sys: Total = 130696 for module ndis.sys Elapsed Time, > 256 usecs AND <= 512 usecs, 56, or 0.04% Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.00% Total, 130696 Also disable all effects in the sound options, becasue the AudioEng.exe causes some CPU usage (CAudioProcessor::ProcessEachAPO)

yes, this sucks. I use this tool to get it back: http://www.quppa.net/wunotify

have you run the optimization? Changing an AV tool is a huge change and now you should train Windows a bit.

run the xperf commands and upload the generated .ETL file.

yeah, I already talked to the dev who made the code change. They wan't change this. You should now use the functions from VersionHelpers.h (part of Win8.1 SDK).

get a clean win 7 Sp1 ISO from a digital river link (google for it) and add the Dell drivers to it. So now you have a clean Windows.

the first delays happen at the first boot stage. Windows hangs several seconds while the attached drives are enumerated: - <phase name="bootStart" startTime="42" endTime="7951" duration="7909"> <pnpObject name="PCIIDE\IDEChannel\5+1270fc08+0+0" type="Device" activity="Enum" startTime="2893" endTime="6407" duration="3514" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" /> <pnpObject name="PCIIDE\IDEChannel\5+1270fc08+0+1" type="Device" activity="Enum" startTime="2894" endTime="6407" duration="3513" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> <pnpObject name="PCIIDE\IDEChannel\4+223a9b9c+0+0" type="Device" activity="Enum" startTime="258" endTime="2766" duration="2508" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 0" /> <pnpObject name="PCIIDE\IDEChannel\4+223a9b9c+0+1" type="Device" activity="Enum" startTime="259" endTime="2766" duration="2507" prePendTime="0" description="IDE Channel" friendlyName="ATA Channel 1" /> look at the duration of 2.5 - 2.5s. The next delay happens while starting this service: <serviceTransition name="MPExtended Service" group="" transition="start" totalTransitionTimeDelta="40516" firstCheckpointTimeDelta="20927" processingTimeDelta="19589" container="MPExtended.ServiceHosts.CoreService.exe (480)" startedAt="24492" firstCheckpointedAt="45419" endedAt="65008" /> What is this MPExtended Service? Also MySQL and TVService are slow to start. Yes, the largest delay happens when Windows loads all startup tools. But I can see that the HDD is the bootleneck. Look at the disk graph and you see that the disk is busy. The Queue Depth is 149!!!!!!!!!! at the Init of some disk operations. Try a different AV tool, Avast seams to hit the disk very hard. You should buy a SSD to fix the HDD bottleneck if you see the disk activity with other AV tools, too.

no, Win8.1 is no Sp, it was designed as the new Windows, but because of the terrible market share MS switched their mind and releases it as an Update for Windows 8. You must add <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> to the manifest to get the API working. http://msdn.microsoft.com/en-us/library/dn302074%28v=vs.85%29.aspx

Apply the rollup, run the optimization and be happy.

now it works: this is no bug, this is by design.

never use Defraggler. Only use the buildin tool.

as I wrote in the first post the DRIVERS flag can cause a BSOD, but MS refuses to fix it. To cancel logging run xbootmgr -remove.

the Update Rollup is safe to use.

link doesn't work.

works fine so far

@ bpalone be have a 8.1 topic: post it there.

oh, I forgot your topic. This is bad. Run RU (registry usage) from Sysinternals to see which key is soo large: http://technet.microsoft.com/en-us/sysinternals/dn194428.aspx ru -ct -v HKEY_LOCAL_MACHINE\SOFTWARE > D:\reg2.csv now open the CSV and look which keys are the largest in size.

I think they shut it down to reduce piracy. I saw several users who bought a "cheap" Windows key from a untrusted shop and this were Technet keys which MS blocked later.

but making changes to a RC requires a new build to test. Only when you tested it and it worked, recompile the source (without any functional change) and only adjust the versionnumbers and remove RC/Beta strings.

release a RC4 so that we can test this version. if users have no serious issues you can release the Final next week.