You are here

[Fixed] Problem with IObitUnlocker Portable

4 posts / 0 new
Last post
tapsklaps
Offline
Last seen: 4 years 3 months ago
Developer
Joined: 2010-10-17 08:11
[Fixed] Problem with IObitUnlocker Portable

After the closure of IObitUnlocker Portable I detected, that the registry key HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_IOBITUNLOCKER remains in the registry. Furthermore I can't delete this registry key.

tapsklaps
Offline
Last seen: 4 years 3 months ago
Developer
Joined: 2010-10-17 08:11
only manually removable

Meanwhile I've found a way, how I can delete the above mentioned registry key. Therefore it was necessary, that I allow myself in the registry editor about the command edit -> authorizations... full access to this key.

But normally this permission is not given. Accordingly it's not possible by the code "-=HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_IOBITUNLOCKER", that this registry key will be removed after the closure of the app. Consequently this app is not portable in this direction.

John T. Haller
John T. Haller's picture
Offline
Last seen: 3 hours 31 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
SetACL

I may be able to work around this with SetACL. The older version is open source so we can bundle it freely (the current one is freeware and can't be bundled without paying). I can do some custom code to determine if the key is there or not in the beginning and if not, assign the proper rights before removing on exit. In theory, anyway.

Sometimes, the impossible can become possible, if you're awesome!

John T. Haller
John T. Haller's picture
Offline
Last seen: 3 hours 31 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Fixed in 1.0 Rev 2

This is fixed in IObit Unlocker Portable 1.0 Rev 2.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments