Video Screencast Help

Slow Internet Explorer startup

Created: 19 Jan 2012 • Updated: 26 Jul 2012 | 5 comments
This issue has been solved. See solution.

Hi Community,

the first Internet Explorer (V.8) startup on a Windows Server 2008 R2 Remote Desktop Session Host is very slow for some users. "First startup" means: the users logon process is finished, he doubleclicks the IE icon and it lasts up to 2 minutes til IE is ready to use. After closing IE and restarting it the startup is fast as usual.

I've used Sysinternals procmon and got thousands of these read/write/query operations while IE startup.

iexplore.exe | WriteFile | C:\ProgramData\Symantec\SRTSP\SrtETmp\5B2905FB.TMP | SUCCESS

iexplore.exe |QueryStandardInformationFile | C:\ProgramData\Symantec\SRTSP\SrtETmp\5B2905FB.TMP | SUCCESS | AllocationSize: 983.040, EndOfFile: 32.767, NumberOfLinks: 1, DeletePending: False, Directory: False 

I assume there is a dependency between Internet Explorer and SEP (v. 11.0.6200.754, Auto-Protect active).

So the question is why does IE query the SEP folder "C:\ProgramData\Symantec\SRTSP\SrtETmp" that often?!

 """ Your hints are really appreciated.



Comments 5 CommentsJump to latest comment

NRaj's picture

This is probably SEP's autoprotect feature scanning IE before startup. But it is not logical that SEP scans it for 2 minutes only the first time.

Did you try to disable SEP and see if things are better?

Srikanth_Subra's picture

My users are alsong facing same their IE is not rsponding at startup

Thanks & Regards,


"Defeat the Defeat before the Defeat Defeats you"
(Swami Vivekananda)

andiko's picture


disabling SEP doesn't solve the problem. My workaround is to keep the users temporary internetfiles folder clean by deleting IEs cached temp inet files when IE is closed.



P_K_'s picture

Right, It doesn't look like a AV issue rather  a browser issue.

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

cus000's picture

hmmm weird..

what bitness are you having in your evinroment? 32 or 64?

How about IE7, did it got same issue?