← Back to Knowledge Base

KB #240155: Returning to a clean state

⏱️ 2 min read

Type:

Info

Summary:

This article provides some extra steps if there are issues with uninstall and you need to get to a clean machine that removes virtually all traces of Encryptionizer binaries and Windows registry entries. (Note: This approach does not decrypt data)

Additional Information:

Typically you will use the Control Panel to uninstall Encryptionizer software.  You will be reminded to decrypt data, if desired. The uninstall does not decrypt your data automatically.

Note: If you remove the software and you still have encrypted data, you will not be able to decrypt your encrypted data with any other means than our software.

This article provides some extra steps for removal of our software in the event that you don’t have an entry in the control panel to uninstall Encryptionizer or you need to take an extra step to clean up.

  • Download the Uninstall Module to a temporary location.
  • From a command window with the Run as Administrator option:
    uninstall.fsql.nep.dist.exe /UNINSTALL

This will complete the initial installation.

This next step uses a command file to scan standard file locations and registry entries for additional removals.

  • Download the Clean command to a temporary location.
  • Copy the cleancmd1cmd file to the Encryptionizer installation folder (default C:Program Files (x86)netlibsecsql or C:Program Files (x86)netlibnep unless changed during installation process)
  • From a command window with the Run as Administrator option which will put the output into the Cleanlog.txt file:
    cleancmd1.cmd -oCleanlog.txt
  • Note: the output of the command will show many cases of file or entry not found. This is because command file looks for not only the current version of software, but also older versions, across files and registry entries. It looks in a number locations for files to make sure things are clean.
  • Manually delete your Encryptionizer installation directory
  • Reboot the machine
  • You should now be ready for a fresh installation if desired.

 

 

Was this article helpful?

Related Articles

KB #240109: Encrypted Backups to Tape

Type: Information Summary: Encryptionizer driver versions 2008.201.40 and later supports encrypted backups directly to tape.…

KB #240023: DBF becomes decrypted after xBase PACK command

Type: Tip Summary: This explains why an encrypted DBF might become decrypted after a PACK…

KB #240146: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Type: Fixed. Summary: This issue has been addressed in Encryptionizer versions 2501.1.7.50217. If you have…

Still need help?

Our support team is here to assist you.

NetLib Security
AI Assistant · Online
Hi! I'm the NetLib Security assistant. I can answer questions about our encryption solutions, HIPAA compliance, Encryptionizer, and more. How can I help you today?