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

Manually running AVREMOVE uninstalls NOD32 but Protect Computers Wizard will not

I have manually updated my ProductCatalog.xml with the two following GUIDs:

{640BE6CD-9B4E-4FA4-98BC-E6975A30DC4F} Version="4.2.67.10 Signature 5976 English"

{08B857DF-E6F9-4283-853A-4F329CC09A4F} Version="4.2.40.0 Signature 5976 English" 

Removal works fine if I copy the CRT folder to a user's desktop and run AVREMOVE in a CMD prompt window. How does the Protect Computer Wizard work differently that is preventing this from working? 

I'm pretty psyched because this is the last thing I need to figure out before I run a deployment.

:10877


This thread was automatically locked due to age.
Parents
  • 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

    :11009

    ==

    When in doubt, Script it out.

Reply
  • 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

    :11009

    ==

    When in doubt, Script it out.

Children
No Data