Intra-build uninstall support
• In order for a build to be truly removed from the system, specific keys must be removed from the O/S in order toproperly remove an application and properly perform a re-install. These keys are build-specific and removing these keys involves determining the key values at install time, updating the staticregistry sets, and then performing the removal. SCSCleanWipe 1.0 contains a program (GenerateRegKeys.exe) that will, based on a preset upgrade code, determine build-independent product code, component code,and uninstall registry keys that will be removed by SCSCleanWipe. With GenerateRegKeys.exe, SCSCleanWipe has the capability to handle “future” builds as long as the upgrade code andproduct/component/uninstall registry referencing and obfuscation algorithms remain the same.
External file removal list
• To better manage additions and subtractions of static files to be removed, SCSCleanWipe1.0 contains a program (DeleteFiles.exe) that deletes files contained in an external file. A log file will be created reporting on the outcome of the file deletion(s). By separating out files to beremoved to a separate file , there will be easier file maintenance and multiple external files can be used as well for better file grouping and separation.De
External directory removal list
• Tobetter manage additions and subtractions of static files to be removed, SCSCleanWipe 1.0 contains a program (DeleteFiles.exe) that deletes folders contained in an external file. A log file will becreated reporting on the outcome of the file deletion(s). Unlike NoNAV, which deletes Folders using the rd command , SCSCleanWipe deletes folders only if they are empty. The benefit for doing this isthat any files created outside of an installation and not part of the expected set will not be removed. While harder to maintain , this is a safer alternative.
External service shutdown list