Jump to content

Recommended Posts

Posted

The ExplorerInit is extremely slow:


<interval name="ExplorerInit" startTime="24885" endTime="103322" duration="78437">

AV tools often cause such issues. You use MSE which is very slow (in my experience). So try to switch to a different AV tool and run the optimization again.


Posted (edited)

The ExplorerInit is extremely slow:


<interval name="ExplorerInit" startTime="24885" endTime="103322" duration="78437">

AV tools often cause such issues. You use MSE which is very slow (in my experience). So try to switch to a different AV tool and run the optimization again.

Thanks Andre :-) What is MSE? What do you suggest I do? Uninstall 'MSE' and install something else? What would you suggest?

Edit. Microsoft Security essentials...duh! I get you. Any suggestions as to what? Is Malwarebytes alone sufficient as a substitute?

Edited by JC1975
Posted (edited)

Just uninstalled MSE. Didn't make the slightest difference. Is there anything else that could be causing the issue? Malwarebytes perhaps? Is there anything I can do in the registry to tweak the ExplorerInit settings?

Edit: Just disabled Malwarebytes and it took 30 seconds off the boot time down to 109 seconds. That's still a bit slow given how much ram and processor speed I have.....any further ideas as to how to get this time down?

Edited by JC1975
Posted

Run ProcessMonitor, select boot logging now run a new xbootmgr boot trace command (not the optimization). After a reboot, run ProcMon again, stop the boot logging and also save the new xbootmgr file. Compress both logs and upload them.

Posted (edited)

I can still see that MSE is running. Completely remove it.

I uninstalled it and it made no difference so I put it back on. I'll uninstall it and rerun the logs?

Edited by JC1975
Posted

Yes. Also provide the boot.etl for the same boot. this helps me to filter the ProcMon log.

Sorry to sound dense but can you elaborate on that? :wacko:

Posted

do what I told you in post #574.

Activate boot logging in ProcMon, and NOW run the xbootmgr command to do a normal boot trace:

After reboot, stop ProcMon and xbootmgr and provide the ETL and the PML files (zip them again to reduce the size)

Posted

do what I told you in post #574.

Activate boot logging in ProcMon, and NOW run the xbootmgr command to do a normal boot trace:

After reboot, stop ProcMon and xbootmgr and provide the ETL and the PML files (zip them again to reduce the size)

There you go Andre: http://tinyurl.com/co79w4b

Due to the size of the file I'm sharing via Tonido. Let me know if you have trouble getting the files.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...