Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 4321 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to install Sophos (XP)

Machine

Hey guys, i cant install Sophos on my Windows XP pc. I see it running through the task manager, and then it disappears.

I dont see any errros though. I have tried restarting multiple times and even left it on for 40minutes with no results


What do you suggest?

:13345


This thread was automatically locked due to age.
Parents
  • 0

    HI,

    When you say the process quits, which is that, the setup.exe or msiexec or one of the services of the installation, e.g. savservice.exe?

    If you install using the standalone installer, that will install SAV first as the user launching the installer, it will then install AutoUpdate.  So for the initial install, the msi logs and custom action logs will be in the intalling users temp, i.e. %temp%.

    If however you are using the setup.exe from a central installation directory (CID), either as a typical deployment (deploy from SEC or just run setup.exe from the CID) or you have re-packaged the central installation directory as a packaged installer, Setup.exe will install AutoUpdate first as the installing user, so logs go to the users temp directory,  i.e.%temp%.  The shield will appear at this stage. Sophos AutoUpdate will then download and install the packages such as a SAV and SCF, AutoUpdate will install these so the logs will go to Windows temp, i.e. \windows\temp\.

    If SAV is the problem package, there will be 2 logs, a msi log and a custom action log:

    Sophos Anti-Virus Install Log_<timestamp>.txt
    Sophos Anti-Virus CustomActions Log_<timestamp>.txt

    Between these two logs it will be possible to know why the installation of SAV failed.  Likewise, if the failing product is SCF, the logs will also be in this directory.

    Feel free to post, the MSI log and custom action log.  You may need to use some online site to host the logs and post just a link here as they are typically quite big.

    Regards

    Jak 

    :13653
Reply
  • 0

    HI,

    When you say the process quits, which is that, the setup.exe or msiexec or one of the services of the installation, e.g. savservice.exe?

    If you install using the standalone installer, that will install SAV first as the user launching the installer, it will then install AutoUpdate.  So for the initial install, the msi logs and custom action logs will be in the intalling users temp, i.e. %temp%.

    If however you are using the setup.exe from a central installation directory (CID), either as a typical deployment (deploy from SEC or just run setup.exe from the CID) or you have re-packaged the central installation directory as a packaged installer, Setup.exe will install AutoUpdate first as the installing user, so logs go to the users temp directory,  i.e.%temp%.  The shield will appear at this stage. Sophos AutoUpdate will then download and install the packages such as a SAV and SCF, AutoUpdate will install these so the logs will go to Windows temp, i.e. \windows\temp\.

    If SAV is the problem package, there will be 2 logs, a msi log and a custom action log:

    Sophos Anti-Virus Install Log_<timestamp>.txt
    Sophos Anti-Virus CustomActions Log_<timestamp>.txt

    Between these two logs it will be possible to know why the installation of SAV failed.  Likewise, if the failing product is SCF, the logs will also be in this directory.

    Feel free to post, the MSI log and custom action log.  You may need to use some online site to host the logs and post just a link here as they are typically quite big.

    Regards

    Jak 

    :13653
Children
No Data