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.
New: Kanri (Oct 9, '24), Platform 29.5.3 (Jun 27, '24)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
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.
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.
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!
This is fixed in IObit Unlocker Portable 1.0 Rev 2.
Sometimes, the impossible can become possible, if you're awesome!