Windows 8.1 upgrade prevented by WSA ?

Discussion in 'Prevx Releases' started by sturgess, Oct 17, 2013.

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

    sturgess Registered Member

    Joined:
    Aug 24, 2011
    Posts:
    158
    Hi, attempted Windows 8.1 upgrade, Windows was unable to complete installation despite numerous attempts. I decided to completely restore Windows 8 and try again, the restore will soon be completed so using another machine I have logged into my Webroot account to disable WSA in order to be able to use it again and discovered my machine has been marked as infected "APPLAUNCH. EXE Uncategorized Malware" the times coincide with the upgrade problem, any thoughts ?
     
  2. fax

    fax Registered Member

    Joined:
    May 30, 2005
    Posts:
    3,726
    Location:
    localhost
    Worked perfectly fine here... no issues whatsoever :thumb:
    Is it a localised 8.1? Or US/EN
     
  3. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    Could you write into our support inbox and have them take a look at your logs? I imagine something isn't whitelisted from your installation.

    Thanks!
     
  4. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    4,449
    Location:
    North Carolina, USA
    Hello,

    My Windows 8.1 upgrade went fine or at least I think it did. Afterwards I found out WRSA quarantined that same file the OP spoke of (applaunch.exe). The thing is I do not know if it was quarantined during the upgrade process thus causing some of the upgrade to fail, or if it was found and quarantined after the upgrade had completed. I went ahead and restored the file but it would be nice to know whether something is now messed up with my upgrade or not.
     
  5. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    4,449
    Location:
    North Carolina, USA
    Hello,

    Here is the information from the threat log:

    Automated Cleanup Engine
    Starting Cleanup at 17/10/2013 - 13:10:28 GMT

    Starting Routine> Removing c:\$windows.~bt\sources\sxs\x86_netfx-applaunch_exe_b03f5f7f11d50a3a_6.3.9600.16384_none_e043f7972eff33f5\applaunch.exe...#(PX5: 29509765981DC8C9DC3A0069CAB0DC0048DAB55E - MD5: BFABF5C5027671A4FA266DF3DE334D6F)...
    Deleting File> c:\$Windows.~BT\Sources\sxs\x86_netfx-applaunch_exe_b03f5f7f11d50a3a_6.3.9600.16384_none_e043f7972eff33f5\applaunch.exe
     
  6. Mango555

    Mango555 Registered Member

    Joined:
    Apr 7, 2010
    Posts:
    26
    Location:
    Florida, USA
    The upgrade to 8.1 failed on my 2 laptops with error code 0X80070057!:'(

    After reading this thread I disabled WSA and voila! Installation was successful on both computers:D
     
  7. SweX

    SweX Registered Member

    Joined:
    Apr 21, 2007
    Posts:
    6,429
    It's not just that a few people dislike Win8......clearly WSA does it too :)
     
  8. Triple Helix

    Triple Helix Webroot Product Advisor

    Joined:
    Nov 20, 2004
    Posts:
    12,011
    Location:
    Ontario, Canada
    And I installed 8.1 on 2 VM's 32bit & 64bit without issues but that was when they released the RTM and still WSA 2013.

    TH
     
  9. sturgess

    sturgess Registered Member

    Joined:
    Aug 24, 2011
    Posts:
    158
    HI, have done as you suggested.
    Regards.
     
  10. volvic

    volvic Registered Member

    Joined:
    Aug 17, 2009
    Posts:
    220
    Has this been resolved?
    2 days have now passed.
     
  11. sturgess

    sturgess Registered Member

    Joined:
    Aug 24, 2011
    Posts:
    158
    Hi, having already removed WSA after previous failed attempts to upgrade to Windows 8.1, I then had no problems upgrading. I now have WSA back on my machine and all is well. The support suggested disabling WSA if I thought it was at fault as they were unable to find anything out of place in the logs I had submitted. I think in my case it was indeed WSA causing the problem, but with only a few folk posting it would appear not to be a problem for most.
     
Thread Status:
Not open for further replies.