Jump to content
grahamperrin

2.0.15.12 Extended Plus 'unable To Install Updates' On A Machine That Was Fine Yesterday

Recommended Posts

Different from nearby http://forum.immunet.com/index.php?/topic/304-201512-code-19010-unable-to-install-updates-following-application-of-an-extended-plus-key-on-a-second-computer/ — the security layer on this computer includes Sophos Endpoint Security and Control — so I don't expect support on this one.

 

Yesterday, AFAIR logged on to XP as administrator 'centrimadmin' I applied a key then the resulting update/upgrade, including TETRA, succeeded.

 

Today, logged on to XP as administrator 'gjp22' (also a member of the SophosAdministrator group):

 

> Unable to install updates

 

I tried logging out, logging on as centrimadmin to apply updates but still, no go.


Sophos Anti-Virus is currently configured to alert (not quarantine), plus both of profos.sys and tufos.sys are explicitly authorised in all three areas (Suspicious files | Suspicious behaviour | Buffer overflow).

Share this post


Link to post
Share on other sites

When I used the Support Diagnostic Tool a .zip was created but again, ipsupporttool.exe crashed — that's http://forum.immunet.com/index.php?/topic/303-20152-extended-plus-ipsupporttoolexe-crashing/

 

If you'd like the zip sent to the e-mail address for support, just say.

Edited by Graham Perrin

Share this post


Link to post
Share on other sites

In a little more detail, with screen shots … 

 

Sophos Anti-Virus is currently configured to alert (not quarantine), plus both of profos.sys and tufos.sys are explicitly authorised in all three areas (Suspicious files | Suspicious behaviour | Buffer overflow).

 

http://www.wuala.com/%23%23ClamAV/009 shot 001 reminds me that when this machine first failed to update:

 

* it broadly coincided with installation of the high priority Microsoft Update to Sliverlight, AFAIR the completion of that one installation preceded the eventual failure of the update.

 

* the Sophos shield was missing from the system tray notification area, and I saw no alerts (probably because of the shield's absence)

 

* AFAIR I then found both profos.sys and tufos.sys not yet authorised in the Suspicious files and Buffer overflow areas; and only profos.sys (not tufos.sys) authorised in the Suspicious behaviour area — and so I in Sophos I relaxed the HIPS behaviour and completed the authorisations.


Screen shots 002 and 003 capture the failures whilst later logged in as centrimadmin, with both profos.sys and tufos.sys fully authorised in the three areas, and no new alerts, and nothing new in Sophos quarantine following the failures.

Share this post


Link to post
Share on other sites
Right now we do not have Proxy support as such.

 

That's probably the issue.

 

Neither http://support.immunet.com/tiki-searchresults.php?highlight=proxy&boolean=on&search=Go

nor http://support.immunet.com/tiki-searchresults.php?highlight=proxies&boolean=on&search=Go find anything so maybe you should add a note to the list of known issues,

http://support.immunet.com/tiki-read_article.php?articleId=20

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...