Revision History ================ 04/07/09 v12.0.120.

4 Defect 1593573, 1593519, 1592638, 1592619 Remove files left over after uninstall . These changes are for defects 1593573, 1593519, 1592638, 1592619 04/03/09 v12.0.120.4 Defect 1591707 Removal failed for SAV 10.1.8. Uninstall needed SPBBCEvt.dll regi stered Defect 1588132 Using -silent switch with RunCleanWipe.bat causes MSI to put up a modal dialog. 04/03/09 v12.0.119.3 Defect 1591707 Removal failed for SAV 10.1.8. Uninstall needed SPBBCEvt.dll regi stered Defect 1588132 Using -silent switch with RunCleanWipe.bat causes MSI to put up a modal dialog. 03/31/09 v12.0.119.2 Defect 1558368, 1586667 Fix uninstall on 64-bit SEP. Display name has a space af ter it 03/27/09 v12.0.119.1 Defect 1557768, 1558248, 1586667 SEP has new name in Add/Remove uninstall entry 02/27/09 v12.0.92.151 Defect 1529121 CleanWipe with DC SPC fails, unable to reinstall - Added Symantec Protection Center as a SEPM set of files to be uninstal led 12/11/08 v12.0.22.1 Defect 1433691 LiveUpdate folder not removed on certain conditions (e.g. when un der the sep directory) 11/17/08 v11.0.4000.3 Defect 1453735 Cleanwipe did not remove SEPM on 2008 SBS On 2008 SBS must open a Command prompt as administrator and execu te RunCleanWipe.bat in app directory 9/30/08 v11.0.4000.2 Defect 1418587 Suppress all reboots when user requests last reboot to be suppres sed. 9/25/08 v11.0.4000.1 Fix for Defect: 1402404 - CleanWipe Enhancement Request: Add Version Information to the Tool Here is the place where the version information can be found: 1. Exe's file name 2. Title of dialogs in interactive launch of CleanWipe application 3. SAVCleanWipe.log: generated Log file when running the tool 4. Version.txt in extracted CleanWipe folder Fix for Defect: 1268146 - More items on Windows 64 2008: HKLM\Software\Symantec is removed on 64-bit system Fix for Defect: 1412731 - Cleanwipe hangs after 1st reboot 9/24/08 Add latest IISCOnfig.vbs for IIS 7 handling *******************************************************

8/28/08 Branch from Trunk (CZ) to the MR4 (Ruby) branch ******************************************************* 8/13/08 Defects: 1268146 More items on Windows 64 2008 Note that on 64-bit systems HKLM\Software\Symantec may be left behind, empty. Ca n't fix that at the moment as we don't have the source code for the tool we have to change. That's a post-MR3 fix. 8/8/08 Defects: 1268146, 1365953 - Clean up items on Windows 64 2008, Remove OD BC DSN 6/25/08 Fix for Defect: 1293725 - Prevent Blue Screen of Death when removing drivers. This modifies the way that the SymTDI driver is removed. 5/30/08 Fix for Defect: 1208824 - CleanWipe updated to not remove MFC and ATL 7.1 DLL's. 4/25/08 Fix for Defects: 1196298 and 1196264 - These were just tweeks to the text on the prompt dialogs at the beginning of running CleanWipe. Fix for Defect: 1232994 - CleanWipe code for removing the SEPM Website now check s to see if IIS is installed. If not installed the website removal code is skip ped. 12/20/07 Fix for Defect 1187548 - Clean Wipe crashes during operation on Win 2K. The problem is SSC, Reporting Agents, and SAV all from 10.1 installed on 2K Adva nced Server SP4. The RunCleanWipe.bat file is terminating abruptly right after you answer Yes to removing the found applications. The only thing that I could find was that the Reporting Agents name stored in SAVProduct2 variable was Repor ting Agents (Symantec Corporation). This probably the paren's in this name are causing some trouble. I have changed FindApp.bat to use the shortened name "Rep orting Agents" and the problem goes away. I also made a minor fix in RunCleanWi pe because for all the cases of more than 2 apps found we were only logging the first 2 apps found in the logfile. 11/30/07 Fix for Defect 1166771 - Norton Ghost 2003 no longer functional after using the CleanWipe tool to uninstall SEP, SEPM, or SNAC. There were 2 problems: 1. CleanWipe was incorrectly removing the registry value for: HKLM\SOFTWARE\ Installed Apps\Norton Ghost 2. The esugreg.exe code was used to determine the LiveUpdate install path ge tting the "InstallLocation" from the registry. The Problem is that sometimes this path stored in the registry has spaces in the name but the whole string is not surrounded by quote characters. The fix was to add -fq switch to esugreg.exe and use it to force quotes o n the returned value. 11/28/07 Fix for Defect 1168897 - CleanWipe: 64-bit SEPM unable to reinstall after CleanW ipe. This was a problem in enummsi2.exe which was causing FindApp.bat to fail to lo cate the SEPM uninstaller. This code needed to look in both locations: SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall

Fix for Defect 1170606 - CleanWipe causes Symantec LiveState Recovery not to be able to LiveUpdate. The problem is that LiveState Recovery has a menu option to launch LiveUpdate but CleanWipe was removing LiveUpdate. The fix is two fold: 1. In the UI when we question the user about removing LiveUpdate we provide one of the following questions depending on if CleanWipe is running any MSI Appl ication uninstalls: If LiveUpdate remains after uninstalling Symantec products do you want t o uninstall LiveUpdate? (Recommended) Do you want to uninstall LiveUpdate? (Recommended) 2. The UninstallLiveUpdate.exe code was changed such that we only force Quit e Mode ( /Q switch ) if CleanWipe is running silently. This means that the Live Update uninstaller will prompt the user in the case that any applications are st ill registered with LiveUpdate. This gives the user an additional chance to pre vent LiveUpdate from being uninstalled. The UninstallLiveUpdate.exe also returns an exit code which RunCleanWipe.bat uses to determine if the uninstall did happ en so it can conditionally do additional removal stuff related to LiveUpdate. Fix for Defect 1166584 - VirusDefs folder is removed when using the CleanWipe to ol to uninstall SEP, SEPM, or SNAC. The problem is that the SEP, SEPM, SNAC uninstallers that CleanWipe detects an d runs will remove the VirusDefs folder in the case that those applications are the only registered applications. We cannot prevent that. What we have done is change the prompt for removing the folder to be conditional depending on if Clea nWipe is running any MSI Application uninstalls: Uninstall Virus Defs" -msg "If Virus Defs remain after uninstalling Syma ntec products do you want to uninstall the Virus Defs? (Recommended) Do you want to uninstall the Virus Defs? (Recommended) Two additional fixes for this build of CleanWipe: 1. The opening screen for CleanWipe now has disclaimer text cautioning about w hat CleanWipe removes. This text looks like the following: Note: The following cautions apply to the use of CleanWipe: - CleanWipe removes all of the listed applications. You cannot select individual applications to remove. - CleanWipe may also remove LiveUpdate. - CleanWipe may also remove Virus Definitions. - If you have other Symantec applications on the computer that d epend on any of the applications listed above, those applications may not functi on properly. You need to reinstall the missing applications after you run Clean Wipe. 2. Silent mode for CleanWipe has been fixed and is documented in the readme.t xt that accompanies CleanWipe. 11/08/07 Fix for Defect 1159132 - The Symantec Shared folder is removed when using the Cl

eanWipe tool to uninstall SEP, SEPM, or SNAC. The following were addressed: 1. Removed code deleting from %CommonProgramFiles%\Symantec Shared\SPManifes ts\ in %CommonProgramFiles%\Symantec Shared\SPManifests\ 2. Removed code in DeletePostReboot.bat that was attempting complete removal of the Common Files\Symantec Shared folders. 3. Fixed logic in RunCleanWipe.bat to remember menu choices in post reboot r estarts of CleanWipe 4. Adjusted cleanwipe.bat to run properly if called from CleanWipe.exe or fr om the cmdline. ( suggested by Edward Elliott ) 5. Adjusted calls to regedit.exe to deal with %systemroot% not being mapped into the system path. ( suggested by Edward Elliott ) 11/06/07 Fix for Defects: 1159159 - After running the CleanWipe tool to uninstall SEP the RASMAN registr y values are not restored with the default paths. 1157913 - Cleanwipe needs Batch File Tweak for Core 32/64 bit and GUI 32/64 bi t. 10/23/07 Fix for Defects: 1130065 - CleanWipe does not remove SPA files/registry 1130000 - CleanWipe does not remove all SAV files 1130059 - SEPM install rolls back after using CleanWipe 1130016 - Errors during SEP client install after running CleanWipe All of above defects are variations of the same general problem. A prior Sym antec component is installed. Then a SEP 11.0 component installer is run, and t he msiexec process for this installer is killed at some random point. Resulting system is CleanWipe'd. Then the SEP 11.0 component installer is run again. The goal is not that CleanWipe will entirely clean the system of Symantec Bits. Ra ther the goal is that any Symantec Bits left on the system after CleanWipe will not prevent the success of running any SEP 11.0 install. Defect 1129989 - Reboot after running CleanWipe produces several event viewer wa rnings. This defect was reviewed as follows: Running CleanWipe may result in MsiInstaller items being logged in the Win dows Event Viewer Application log with the following descriptive text: "Failed to connect to server. Error 0x800401F0." These Event Viewer log entries are harmless and can be ignored. An item was added to the CleanWipe Readme.txt file to document these log entri es. 9/05/07 *Fix for Defect 1121597 - Hamlet wildcard file deletes using *.* are dangerous a nd should be removed from the code. 7/26/07 *Fix for Defect 990463 which is the inability to remove combination of SEP + SEP M. The esugmsi2.exe utility was added to parse output from esugmsi.exe to parse results down to one found application. 7/06/07 *Fix for Defect 1041623 which is CleanWipe removal of the combination of SSC, SA

V, and SEPM. 6/13/07 * Changes to opening screen, CleanWipeOpen.txt, per Brad Kingsbury. * Fix for Defects 1061874+1060937 - The problem is not detecting the Symantec En dpoint Protection (SEP) uninstaller due to the name change from Symantec AntiVir us Advanced Protection. * Upon resume from restart, write different heading to SavCleanWipe.log file. * Fixed the persistance of XXX_Folder environment variables detected in initial run and persisted to each resumption after reboots. This fixes cases of orphane d files example SPM 5.1 migrated to SEPM and then CleanWiped . 5/14/07 Fix for Defect 1043810 - CleanWipe: SAV + SPA causes windows crash/blue-screen w hen running CleanWipe This was fixed by changing CleanWipe logic to always force a reboot after runn ing any MSI uninstall. Fix for Defect 1027420 - CleanWipe: unable to remove both SAV 10,1 Server and SE A 5.1 FindApp.bat now detects SEA + SAV combination. 5/07/07 Fix for Defect 1027516 - CleanWipe: migration 10.1SCS Server to 11 SES Client, p ost uninstall SES, leave files behind Also the following minor changes: *Fixes previous change to LiveUpdate uninstall. We now create UninstallLiveUpd ate.exe and run that. *Eliminited more unwanted outputs on the cleanwipe cmdline window. 5/06/07 Fix for Defect 1027531 - CleanWipe: SES reinstall fails post cleanWipe SES that migrated from SAV Client 9.0 & SPA 5.1 Also the following minor changes: *Uninstaller for SAV 9.0 version is forcing a reboot. This reboot is now handl ed properly by CleanWipe *SAV 9.0 CleanWipe installs LiveUpdate with an uninstall string in the registr y that has the long path to the executable but this string is not quoted. This was causing running the batch file to uninstall LiveUpdate to not work. This is also fixed. *DeletePostReboot.bat modified so that it doesn't access environment variables that are not set. *Eliminited unwanted outputs on the cleanwipe cmdline window. 4/24/07 Fix for Defect 1019422 - CleanWipe: unable to remove SSC 10.0 from the system ha s SAV server and SSC 10.0. 4/16/07 Fix for Defect 1021455 - CleanWipe: fails to unregister SAV 10.1 from Add/Remove when original install source is deleted.This change streamlines the EnumMSI.bat code registry search for MSI related keys that can be deleted. The change utilizes a more focused registry se arch rather than whole registry searches. In addition we have had to change the cleanwipe.bat fi le that is launched by the FilZip after the self-extracting executable is expanded. This code now d etects running on 64 bit operating system and prevents continuation into RunCleanWipe.bat. You

will have to do this in 2 steps now on 64 bit machines. This is because the packed exe is a 32 bit app and when expanded was running RunCleanWipe.bat where the EnumMSI.bat code would generate a proper .reg file for keys to be deleted and but launching this file in regedit was not deleting t he specified keys. The solution we determined is that RunCleanWipe.bat must be run as a separate st ep from the extraction of the code from the executable file when running CleanWipe on a 64 b it system. 4/12/07 Partial Fix for Defect 1014106 - Cleanwipe taking in excess of 4 hours and not r emoving SAVAP This change allows CleanWipe to call the LiveUpdate uninstaller silently by appe nding the "/Q" cmdline switch. We do this because CleanWipe has already asked fo r permission to uninstall LiveUpdate and we don't want to see the popup from Liv eUpdate saying that there are still applications registered with live update. 4/4/07 Fixed Defect 1018390 - CleanWipe: leave SPM shortcut in Start Menu post uninstal ling SPM 5.1 Fixed Defect 1018397 - CleanWipe: install SEPM post uninstalling SPM 5.1, get er ror 2343, install fails Fixed Defect 1018429 - CleanWipe: post complete removing product, CleanWipe shou ld prompt user with removal Perforce changelist: 2548894 Notes: 1. SPM 5.1 uninstaller in CleanWipe was fixed 2. CleanWipe now puts up a MessageBox with status as final step of successful c ompletion. 3/20/07 Fixed Defect 974526 - CleanWipe: leaves behind files. Fixed Defect 990463 - CleanWipe: unable to remove both SAV and SESM. Perforce changelist: 2513510 3/19/07 Fixed Defect: 1006083 - Reinstall blocked after using CleanWipe to remove produc t migration. Fixed Defect: 1005122 - Cleanwipe: SESM IIS website not removed 3/6/07 Fixed Defect: 991287 - An infinite recursion in the search function of ESUGREG.E XE that was seen on Vista x64 was fixed. ================ 2/14/07 Initial Hamlet release posted to \\nsx\incoming\Hamlet\CleanWipe This version of CleanWipe has been tested by Carl Forsander for the following Ap plications: SAVCorp ( ClockWork) SAVCorp ( Hamlet ) SEPM ( Hamlet ) SNAC ( Hamlet ) SEP 5.1 SPA 5.1 SPM 5.1

The testing was done on VMWare images of XP Professional, XP Professional x64 Ed ition, and Vista. Please Contact Carl Forsander for any issues with CleanWipe. ================ 2/20/07 Fixed problem with ESUGUnEn2.exe launching a MessageBox showing that it cannot f ind RegDeleteKeyExW in advapi32.dll. All calles to this method now use LoadLibra ry/GetProcAddress mechanism as this API is only needed / available on 64Bit OS. ================