I have searched the documentation and have not been able to determine how to accomplish this task. I would normally not worry about this but I need to do this during testing so the registry on my test PC(s) is not cluttered with outdated entries. Searching the registry via regedit, is a time consuming process I want to avoid, particularly because I have no idea how or where the Activation Key relevant information is stored. Can someone please point me in the right direction?
How to remove all registry entries during the uninstall process
- Thread starter Hermannjt
- Start date
oldteacher
Active member
Been awhile since I used Paquet Builder, but seems I recall this is very possible. The docs are
www.installpackbuilder.com
www.installpackbuilder.com
Write a Registry Entry
Write a value to the Windows Registry to store application settings, paths, or configuration data.
Remove a Registry Key or Entry
Delete a specific registry entry or an entire registry key with all its sub-keys and values from the Windows Registry during package execution or uninstall.
When the app first opens it asks the user to enter their Key. The app itself writes the "Activation Key" information once entered and submitted ... but where?Been awhile since I used Paquet Builder, but seems I recall this is very possible. The docs are
Write a Registry Entry
Write a value to the Windows Registry to store application settings, paths, or configuration data.
Remove a Registry Key or Entry
Delete a specific registry entry or an entire registry key with all its sub-keys and values from the Windows Registry during package execution or uninstall.
For this, use XLS Padlock's own Deactivation feature rather than trying to delete the activation entries from the registry by hand. Deactivation is the supported way to remove an activation from a machine: it clears the local activation cleanly so you can re-run the trial and activation flow from a fresh state, which is exactly what you need between test cycles, and it does the right thing wherever the data physically sits.
I would steer away from wiping XLS Padlock's internal activation entries directly from your uninstaller. They are stored in a form tied to your application, deleting the wrong branch could affect other protected apps on the same machine, and the internal layout can change between versions, so a hard-coded "Remove a Registry Key" action is fragile. Deactivation is version-safe and is the intended mechanism for precisely this.
If your real goal is a fully clean test machine between runs, deactivating the app, or testing under a fresh Windows user account or a VM snapshot, gets you there reliably without touching the registry manually.
I would steer away from wiping XLS Padlock's internal activation entries directly from your uninstaller. They are stored in a form tied to your application, deleting the wrong branch could affect other protected apps on the same machine, and the internal layout can change between versions, so a hard-coded "Remove a Registry Key" action is fragile. Deactivation is version-safe and is the intended mechanism for precisely this.
If your real goal is a fully clean test machine between runs, deactivating the app, or testing under a fresh Windows user account or a VM snapshot, gets you there reliably without touching the registry manually.
It looks like I need to create several "Mikey" accounts; even that clutters the registry with old/unusable entries. My interest is actually clearing the Registry Entries during the "Demo Test" uninstall process. I would never consider this for the actual production version!
I'm still looking for an easier solution if you can help. I'm a Networking Guy (Former CCNP *) not a Computer Admin Type.
Thanks again.
For a repeatable test loop, the tool that fits your goal best is not registry deletion at all, it is a disposable environment. Two good options, easiest first:
There is a supported command-line path if you would rather script it: the compiled app accepts
which starts XLS Padlock's own deactivation and cleanly removes that machine's activation. One caveat that matters specifically for a test loop: deactivation is final for that key on that machine, the key is blacklisted there and cannot be reused, so you would need a fresh key for the next cycle on the same PC. That is why, for repeated testing, the sandbox or a VM snapshot is the smoother choice: the same trial key keeps working and you never accumulate stale entries in the first place.
- Windows Sandbox (a free feature on Windows Pro and Enterprise). It gives you a clean, throwaway Windows session. Install your Paquet Builder package inside it, run your activation and trial tests, then close the sandbox: everything it wrote, including every registry entry, is discarded automatically. Nothing touches your real machine's registry, and you can start from a pristine state as often as you like. This is exactly the no-clutter, no-admin-surgery workflow you are describing, and it does not need you to be an admin type: you turn the feature on once, then just open and close it.
- A virtual machine snapshot (VirtualBox, Hyper-V, or VMware). Take a snapshot of a clean state, test, then revert to the snapshot. Same result: zero residue, and you can reuse the same keys every cycle.
There is a supported command-line path if you would rather script it: the compiled app accepts
Code:
YourApp.exe -deact