WSA causing Windows to start slowly

Discussion in 'Prevx Releases' started by STV0726, Dec 27, 2011.

Thread Status:
Not open for further replies.
  1. STV0726

    STV0726 Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    900
    Sometimes when I boot up my Windows 7 64bit computer, the log in "welcome" process lags. This started as soon as I installed Webroot SecureAnywhere Essentials, and after reading the CNET review, I figured it was WSA causing it. According to the CNET review, WSA was very good in all performance areas other than the way it affected system startup, if I recall.

    During a routine check-up of my system to address another issue I was having with a different program, I noticed Windows flagged Webroot SecureAnywhere as being a startup problem.

    I wanted to bring this to your attention...

    WSA Slow Start Issue.JPG

    Thanks.
     
  2. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    That's very interesting - could you write into our support inbox and send in a scan log so that we can take a look? That should let us get to the bottom of it.

    Thanks!
     
  3. STV0726

    STV0726 Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    900
    Sure, but I still must ask one thing:

    I am still not certain on how to send in a scan log or upload ANY file for that matter using Webroot's support page. I have looked all over and there is NO link to attach a file as there is on the Prevx support page.

    I don't know why I am having so much difficulty with this... :doubt:
     
  4. Techfox1976

    Techfox1976 Registered Member

    Joined:
    Jul 22, 2010
    Posts:
    749
    When support needs more data, they use download.webroot.com / wsalogs.exe (reconstruct into a URL if you like), which gathers and uploads automatically, but they still need a support ticket to know why you sent the logs. The thing even has a way to send arbitrary files from what I understand.

    Best to just ask support I think.
     
    Last edited: Dec 28, 2011
  5. Triple Helix

    Triple Helix Specialist

    Joined:
    Nov 20, 2004
    Posts:
    12,647
    Location:
    Ontario, Canada
    There is no automatic log uploads and only WSA support will send the link to download wsalogs.exe utility if they need more info from you!

    TH
     
    Last edited: Dec 28, 2011
  6. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    If you can save a scan log and then send us the lines of which ones refer to:

    Monitoring process

    that would be the best way for us to find the slowdown.

    Thanks! :)
     
  7. Doraemon

    Doraemon Registered Member

    Joined:
    Aug 5, 2009
    Posts:
    202
    I'm having this same issue since I installed WSAC back in December. It didn't happen in the beginning, it started a couple of weeks since the first install. I resolved it by uninstalling/reinstalling but this week I got an automatic update to version 8.0.1.82 and the problem reappeared.

    I see that there's a file "WRLog" under c:\ProgramData\WRData. Is this the scan log you need? If so, do I have to post it here or attach it to a post or send it to a particular website?

    Thanks! :D
     
  8. Triple Helix

    Triple Helix Specialist

    Joined:
    Nov 20, 2004
    Posts:
    12,647
    Location:
    Ontario, Canada
    Please do a scan and then save a scan log by Right clicking on the Tray Icon and select "Save a Scan Log" and copy a paste the lines of which ones refer to: Monitoring process that would be the best way for us to find the slowdown in the Support Ticket. http://www.webrootanywhere.com/support

    HTH,

    TH

    Example:

    Tue 10-01-2012 15:49:41.0310 Monitoring process C:\Windows\System32\LogonUI.exe [715F03B4C7223349768013EA95D9E5B7]. Type: 3 (1846)
    Tue 10-01-2012 15:49:41.0310 Monitoring process C:\Windows\System32\LogonUI.exe [715F03B4C7223349768013EA95D9E5B7]. Type: 4 (1846)
    Tue 10-01-2012 15:49:41.0310 Monitoring process C:\Windows\System32\LogonUI.exe [715F03B4C7223349768013EA95D9E5B7]. Type: 5 (1846)
    Tue 10-01-2012 15:49:41.0310 Monitoring process C:\Windows\System32\LogonUI.exe [715F03B4C7223349768013EA95D9E5B7]. Type: 7 (1846)
    Tue 10-01-2012 15:49:42.0262 Monitoring process C:\Windows\system32\DllHost.exe [A8EDB86FC2A4D6D1285E4C70384AC35A]. Type: 3 (1884)
    Tue 10-01-2012 15:49:42.0262 Monitoring process C:\Windows\system32\DllHost.exe [A8EDB86FC2A4D6D1285E4C70384AC35A]. Type: 4 (1884)
    Tue 10-01-2012 15:49:42.0262 Monitoring process C:\Windows\system32\DllHost.exe [A8EDB86FC2A4D6D1285E4C70384AC35A]. Type: 5 (1884)
    Tue 10-01-2012 15:49:42.0262 Monitoring process C:\Windows\system32\DllHost.exe [A8EDB86FC2A4D6D1285E4C70384AC35A]. Type: 7 (1884)
    Tue 10-01-2012 15:49:42.0278 Monitoring process C:\Windows\system32\DllHost.exe [A8EDB86FC2A4D6D1285E4C70384AC35A]. Type: 8 (1884)
    Tue 10-01-2012 15:49:42.0356 Monitoring process C:\Windows\system32\atbroker.exe [23566F9723771108D2E6CD768AC27407]. Type: 3 (1891)
    Tue 10-01-2012 15:49:42.0356 Monitoring process C:\Windows\system32\atbroker.exe [23566F9723771108D2E6CD768AC27407]. Type: 4 (1891)
    Tue 10-01-2012 15:49:42.0356 Monitoring process C:\Windows\system32\atbroker.exe [23566F9723771108D2E6CD768AC27407]. Type: 5 (1891)
    Tue 10-01-2012 15:49:42.0356 Monitoring process C:\Windows\system32\atbroker.exe [23566F9723771108D2E6CD768AC27407]. Type: 7 (1891)
    Tue 10-01-2012 15:49:42.0356 Monitoring process C:\Windows\system32\atbroker.exe [23566F9723771108D2E6CD768AC27407]. Type: 8 (1891)
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.