MagicAndre1981

nice, I'll try it later this week

stop all 3rd party tools ad capture a new trace which shows those spikes,

I can't see any spikes: Total = 109885Elapsed Time, > 0 usecs AND <= 1 usecs, 12005, or 10.93%Elapsed Time, > 1 usecs AND <= 2 usecs, 4941, or 4.50%Elapsed Time, > 2 usecs AND <= 4 usecs, 4586, or 4.17%Elapsed Time, > 4 usecs AND <= 8 usecs, 59124, or 53.81%Elapsed Time, > 8 usecs AND <= 16 usecs, 15803, or 14.38%Elapsed Time, > 16 usecs AND <= 32 usecs, 12228, or 11.13%Elapsed Time, > 32 usecs AND <= 64 usecs, 1164, or 1.06%Elapsed Time, > 64 usecs AND <= 128 usecs, 28, or 0.03%Elapsed Time, > 128 usecs AND <= 256 usecs, 6, or 0.01%Total, 109885128 till 256µs is fine. the CPU usage spikes you have come from the sidebar.exe. Try to connect it not to an USB3 port or update the USB3.0 driver (IUSB3XHC.SYS) and see if this helps

updates for R2 of course don't work for 2008, but R2 and the original 2008 have the same support. MS wanted to kill support for R2 in 2018, but this caused trouble with customers so they extended 2008 support to 2020.

MS may listen to users and add startmenu back in 8.2 and allow those new apps to be run in Windowed mode: http://winsupersite.com/windows-8/further-changes-coming-windows-threshold After firing Sinosfky Windows may go back to the right direction.

Vista has still support till 2017 and maybe till 2020, because the Server 2008 gets support like 2008R2 (Server of Win7). If MS doesn't check for clients in the Update you can install the security fixes in Vista too.

share the dumps, maybe I can see anything.

the boot will be faster, but I can't say how long Windows will boot.

your HDD is the bootleneck. it is busy all the time. Depth queue of 185 is a disaster. Everything over 10 is bad! Replace the Samsung Spinpoint M8 HN-M500MBB with a Samsung SSD 840 Evo or Pro to get a large boost.

make sure the driver was updated correctly. look at the file dates of syntp.sys if it has a newer date.

in 8.1 you use DISM with /ResetBase to remove old files, but this is really a 8.1 feature only.

using vLite breaks WinSxS because vLite doesn't really uninstall the packages, it deletes the files and registry settings. Don't use vLite any longer.

Update the synaptic touchpad driver and looks if this fixes it: ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)An attempt was made to execute non-executable memory. The guilty driveris on the stack trace (and is typically the current instruction pointer).When possible, the guilty driver's name (Unicode string) is printed onthe bugcheck screen and saved in KiBugCheckDriver.Arguments:Arg1: fffffa800dc814d0, Virtual address for the attempted execute.Arg2: 80000004528009e3, PTE contents.Arg3: fffff88002e06560, (reserved)Arg4: 0000000000000003, (reserved)Debugging Details:------------------CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTBUGCHECK_STR: 0xFCPROCESS_NAME: SystemCURRENT_IRQL: 2STACK_TEXT: nt!KeBugCheckExnt! ?? ::FNODOBFM::`string'nt! ?? ::FNODOBFM::`string'nt!MmAccessFaultnt!KiPageFault0x0Wdf01000!imp_WdfRequestCreateSynTPIMAGE_NAME: SynTP.sysFAILURE_BUCKET_ID: 0xFC_SynTP+210cd Image path: \SystemRoot\system32\DRIVERS\SynTP.sys Image name: SynTP.sys Timestamp: Wed Apr 24 02:34:23 2013 (5177288F) CheckSum: 00080F88

no, the WinSxS folder will grow and increase the ISO/WIM size a lot.

@RJARRRPCGP wth do you talk about? @abhijeetv2 starting some services takes a longer time: serviceTransition name="SharedAccess" group="" transition="start" totalTransitionTimeDelta="19297" serviceTransition name="DeviceAssociationService" group="" transition="start" totalTransitionTimeDelta="11325"<serviceTransition name="UmRdpService" group="" transition="start" totalTransitionTimeDelta="14144" Run this command and upload the compressed (as 7z or RAR) ETL: xbootmgr -trace boot -traceFlags BASE+LATENCY+DISPATCHER+FILE_IO+FILENAME+POWER -stackwalk profile+CSwitch+ReadyThread -resultPath C:\TEMP

booting to the UI takes 70s and the system is fully booted in over 500s : - <timing bootDoneViaExplorer="79057" bootDoneViaPostBoot="511157" The delay from the UI comes from the driver ArcCtrl: <phase name="systemStart" startTime="3271" endTime="55397" duration="52126"> <pnpObject name="ArcCtrl" type="Driver" activity="Load" startTime="3927" endTime="55391" duration="51464" prePendTime="51464" /> Most of th time is spend after the UI is launched: <interval name="PostExplorerPeriod" startTime="79057" endTime="511157" duration="432100">Remove as much tools as possible from automatic startup at logon.

yes AV suites can cause this. But this is hard to see from the trace.

thanks for the fixed version. *bump* Any comments if you consider to add this?

capture a xperf trace and upload the file, so that I can take a look what uses the CPU: http://www.msfn.org/board/index.php?showtopic=140264

thanks for the new RC. I'll test it later today

add a pid.txt with the key to the ISO

why was msfn down earlier today?

nice to hear this

yes RP = Release Preview.

I use always hibernation and only reboot after the patchday. So Windows resumes very fast all the time.