Manually running AVREMOVE uninstalls NOD32 but Protect Computers Wizard will not

hey hey ash!

are you making changes to the crt folder within the Sophos CID?  If so, this is the propper way to make changes.  You should create a folder under SAVSCFXP called remover (lower case)

In this SAVSCFXP\remover folder you should have the contents of the CRT.  WITH the CRT.cfg and ProductCatalog.xml file in the root of the remover folder...

As making modifications to the crt folder will eventually result in those changes being nuked on some major updates.  Making a remover folder (of which setup.exe enumerates during bootstrap and looks for avremovew.exe to run) will not be changed on updates.

Y'know, I think I may have gotten it working. I did have a remover folder and it appeared to be setup properly. It seems as if I needed to overwrite the ProductCatalog file within the data.zip in order for it to have finally worked.

I wrote out how I think this process works. Can you tell me if this is how it works or explain how it does work?

     -If the remover folder exists then crt is bypassed?

     -If ProductCatalog is in the remover dir then the file in the zip is bypassed? Same story with the crt.cfg file?

officially, if you have a remover folder, you should extract the productCatalog.xml and CRT.cfg file from the data.zip compressed file, into the root of the remover folder.

The ProductCatalog.xml file can be renamed and then referenced in the CRT.cfg file - along with specifying how product Suites are tackled, etc...

As such, the proces is:

if the CRT is called by selection of the 'Third Part Competitiive...' checkbox in the Console during protect computers wizard, then avremovew.exe will be executed from the crt folder.  IF the remover foldr is present, the crt folder is ignored and the avremovew.exe file in that folder is called.

Which will then also automatically look for a CRT.cfg file and enu,erate which product catalog it should be using.

Either way, when ever the CRT executes, there should always be a log file generated called 'AVRemove.log' which typically resides in %temp%.

Cheers