Jimm69
Content Type
Profiles
Forums
Events
Posts posted by Jimm69
-
-
ok, run the optimization which I linked in my first post. This optimizes the Prefetcher and this improve the boot speed. This is all you can do.
I have an SSD, and that document says not to use it on a SSD.
0 -
The ProcMon logs show the system time... how do I sync the system time with the elapsed time?
activate the column "Relative Time". I looked at the interval and found nothing useful. You shoukd reduce the amount of loaded tools and try other AV tool, your symantec is also slow.
I loaded a tool called Soluto and it seems to have helped the winlogon process. I removed what it claims was 2s of tool loading time, and now it says my "system ready" time was 50s after all the services had loaded in the desktop. Not much I can do with Symantec, it was a corporate decision based upon centralized management and the bean counters. I always knew it would be increased overhead.
0 -
set the starttype of Superfetch to automatic
you must enable bootlogging in Process Monitor and run the xbootmgr trace again. After the reboot stop the ProcMon trace, open the ETL and find the time where the profile is loaded. Go into ProcMon and exclude all events before/after the profile loading occurs and look what happens there. So you may find out what is slow in loading the profiles.
I set Superfetch to automatic and restarted, then downloaded and ran Sysinternal's Process Monitor, enabled boot logging, and set the timing to 100ms. I re-ran the boot trace and let the capture timer run the full amount of time. It then gave me a warning about who to let see the file, then it said waiting for prefetcher, and then it later said something along the lines it gave up waiting for the prefetcher after 300s. I re-ran ProcMon and it asked me if I wanted to save the data, and it created 5 files.
In the ETL, the Subscriber "Profiles" says subs. started at 28.038, but that's elapsed time. The ProcMon logs show the system time... how do I sync the system time with the elapsed time?
New archive is here, 130MB: http://www.mediafire.com/?ibbed2calfk7gi3
0 -
Superfetch: It could have been in some guide which I absentmindedly trusted
I've looked in my registry and both Enable Prefetch & Enable Superfetch have a value of 3. The Superfetch service is set to manual. It depends upon DCOM Server Process Launcher (which is Automatic/Started), RPC Endpoint Mapper (Automatic/Started), and File Information FS MiniFilter aka FltMgr, which is not shown in my list of services.NIC's: I use the Wifi at home but usually not in the office. I try to always have it disabled by a physical switch when I'm using the gigabit connection. The slow login seems to occur regardless of whether I'm connected to any network. Is there a method to further trace the winlogon process?
0 -
upload it to mediafire.com
0 -
Your Windows takes 82s to boot to the desktop and 90s to boot completely.
the largest delay occurs while loading the profile. I need the ETL file to see more. Is the PC part of a domain?
It is a domain member. The ETL file compressed with Zip/RAR/7Zip is 81MB/63MB/45MB. Where can I upload the 7zip archive?
0 -
Hi Andre,
My system load is pretty fast, ~25s to the logon prompt, but another 40s to reach the desktop. Does this summary boot log give you any more specifics other than it being winlogon/profile causing a long delay? If not, what other information can I provide to isolate the issue? Thanks!!!
Jim
0
I've looked in my registry and both Enable Prefetch & Enable Superfetch have a value of 3. The Superfetch service is set to manual. It depends upon DCOM Server Process Launcher (which is Automatic/Started), RPC Endpoint Mapper (Automatic/Started), and File Information FS MiniFilter aka FltMgr, which is not shown in my list of services.
Trace Windows 7 boot/shutdown/hibernate/standby/resume issues
in Windows 7
Posted
I'm inferring you're referring to rotational hard drives and not SSD's, based upon the recommendation to disable it in a SSD system?