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

Windows XP Manual Protection - Setup.exe Installation failure

Good day folks,

I am in a workgroup environment trying to manually protect a Windows XP computer using the setup.exe from the Bootstrap Location.  Problem is that after double clickling setup.exe, the wizard does not appear.   Nothing happens.

I checked Event viewer and there are not notifications of errors.  Nothing happens in the Windows Task Manager when I double click the setup.exe file.  

I also tried it on a Windows 2000 machine with same results.

Other than what I foresee as suggestions to redownload the whole program and reinstall, is there something else to do to get this started?

Thanks for your help

C

:6741


This thread was automatically locked due to age.
  • Hi,

    What happens if you copy the CID from the server to the client and run setup.exe from the local copy?

    Jak

    :6743
  • Nothing happens.   Double click as many times and no wizard comes up.

    :6749
  • Did it get as far as creating the log file:

    "Sophos ES setup.log"

    in %temp% (the temp directory for the account running setup.exe)?

    Have you tried running Process Monitor and then running setup.exe to see exactly how far it gets when compared against a machine where it works ok?

    Does the setup.exe process load any dlls etc, does it fail to load others, any access denied entries or not founds you wouldn't expect?

    Thanks,

    Jak

    :6751
  • Hi JCWVHelpdesk

    There is a way to 'force' the install, but becuase this is very manual there are some configurations you HAVE TO DO afterwards.

    Navigate to the \\servername\SophosUpdate\CIDs\Sxxx\SAVSCFXP\sau folder

    Run the 'Sophos AutoUpdate.msi'

    This will install the shield only. It will not update as it uses the default configurations.

    Copy the following folder from a working machine to this machine:
    C:\program Files\Sophos\AutoUpdate\Config\*

    (If you dont do the above it will see the machine as NT and not XP)

    Right click on the shield and update and it should go through.

    I do not recommend doing this all the time, if it happens on one machine then its the machine,

    BUT if it is happening on all the new installs you need to see what configurations are running on all the machines.

    I would think this is related to IE. (Seen it two or three times)

    Either the security essentials or popup blocker (Might even be GPO if you are in a domain enviroment)

    :6893