Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 3940 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

Standalone install doesn't work on Win 7 64 bit

Wigsy

I followed the best practice guide to create a web CID and installer package.  This all works perfectly well on a winxp pc but fails in 2 places on a Win 7 64bit pc.

The first issue is the batch file tries to copy the cutome config dir to %programfiles%\Sophos... but fails with access denied presumably this is Win 7's UAC getting in the way but I can't see a way around it using a batch file.

The second issue is that the setup.exe when used with the command switches doesn't do anything, I see the UAC prompt which I accept followed by the spining disk cursor for a few seconds, control passes back to the batch file and nothing else happens.  There are no error messages and nothing reported in the event log.

Has anyone else tried this or have any advice?

:5548


This thread was automatically locked due to age.
  • 0

    Hello Wigsy,

    you probably followed Best Practice: setting up home users (if not please state which one). While all the articles about creating standalone installers have been updated recently there are some errors and inconsistencies. Moreover there remain some questions which I will address in a new thread.

    Also please always specify the SAV version used.

    The first issue - haven't checked whether it is UAC because the batch file is plain wrong for both a Win7 (because there the \Config\ directory is under %ProgramData%) and 64bit (as Sophos is a 32bit application and therefore in %ProgramFiles(x86)%).

    The second issue - which switches did you use (see here for a description)? setup.exe normally returns after a few seconds when it has launched th AutoUpdate installer. The latter writes the Sophos ES setup.log to the user's %TEMP% directory. There should also be the avremove.log if you used -crt R. Check these for any errors.

    Christian

    :5555
  • 0

    Hi Christian,

    Thanks for the response, sorry I meant to say it's sec 9.5 that I'm trying to install.

    Yes, the best practice guide you linked to is the one (and I did find it a bit confusing but managed to work my way round that!)

    I can try creating a new batch file for x64 pc's - as this is for home users that access our network there'll no doubt be a few versions to contend with but that should it care of this problem.  The command line used is as in the guide but with out the firewall install option as I haven't had a chance to play with that yet:

    C:\SAVSCFXP\Setup.exe -mng no -crt R -ni -updp c:\savscfxp\

    When I have the test pc in front of me I'll check the logs and report back what's there if anything.

    Regards

    James.

    :5558
  • 0

    From avremove log...

    19 Oct 2010 19:22:33 Debug: Opening key SOFTWARE\Microsoft\Windows\CurrentVersion\Installer (64-bit)
    19 Oct 2010 19:22:33 Debug: Opening key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AVG9Uninstall
    19 Oct 2010 19:22:33 Debug: Key AVG9Uninstall was found
    19 Oct 2010 19:22:33 Debug: Product in key AVG9Uninstall not a Windows Installer package, treating as a standard uninstall
    19 Oct 2010 19:22:33 Info: Detected GriSoft AVG version 9.x

    From ES Setup (this is all ther is...)

    20/10/2010,17:13:34,Information,Verified that contents of CID C:\Users\Wigsy\AppData\Local\Temp\sophosa match the manifest file,
    20/10/2010,17:13:34,Information,Searching for third-party security software.,
    20/10/2010,17:13:35,Information,Return Code 13 from third-party security software removal tool.,
    20/10/2010,17:13:35,ERROR,Detected third-party security software. To remove it, run this installer again and select the removal option. If you have already done so, contact Sophos for additional assistance.,
     So it does look like it's not able to remove the 3rd party software, if I remember riight the -ni switch means no interface so presumably that's why I don't see a message?

    Regards

    James.

    :5569
  • 0

    ... the -ni switch means no interface so presumably that's why I don't see a message?

    Maybe (wonder what the -s switch is for), but you can easily check this omitting the -ni. But at least you now know why it failed, right? Looking at the Endpoint Security and Data Protection: removal tool article I see 8.0 as the latest version for AVG. The article contains no Last changed date, could it be that it is not up to date?

    Anyway, you should do as the ERROR message says: If you have already [selected the removal option] , contact Sophos for additional assistance.

    Christian

    :5574
Unfiltered HTML