Event ID: 1041 Could not fully enable Secure Lockdown

I've just started a trial of Secure Lockdown v2 Internet Explorer Edition.  Everything seemed to install correctly and configuration was pretty straight-forward to set it up the way I want it to work.  I installed under the local administrator account and then created a new administrator account named portalkiosk.  The system is Windows XP SP3 and has .NET 3.5 SP1 installed.  I've double-checked and portalkiosk is a member of the administrators group and the local administrators group has full control of the registry.  When I try to enable Secure Lockdown I receive the error message below and it generates the title event in Event Viewer.  I have completely removed my antivirus software and tested enabling it under the local administrator account with the same result.  Any ideas?  I have to be doing something wrong.

"Could not fully enable Secure Lockdown.  Ensure that you are logged on with administrator rights.  Error: Object reference not set to an instance of an object."

This error message indicates that Secure Lockdown could not write to some area of the Windows Registry. Try creatng the user as a local administrator instead of adding the user to the Administrators group. Also, what is the full error reported in the Windows Application Event log under error code "1041"?

I'll give it a try but the system created default administrator account generates the same error message.  There are actually two error events.  The full Windows Events are below.

1041 - Could not fully enable Secure Lockdown. Ensure that you are logged on with administrator rights. Error: Object reference not set to an instance of an object. Trace Stack:    at SecureLockdown.Functions.disableExplorerLibraries(Boolean bSetting) at SecureLockdown.Functions.EnableSecureLockdown()


1022 - Could not delete Windows Registry key. Object reference not set to an instance of an object.

Both of these errors indicate that the account under which Secure Lockdown is running does not have sufficient privileges. Also, be sure you do not have any specific Group Policy rules enabled that may cause these errors.

I have attempted to enable Secure Lockdown using a domain admin account and receive the same error message.  There are no GPOs that restrict access to the registry or any other area of the PC for a domain admin that I am aware of.  The domain admin is completely unrestricted on that system and I am able to write and delete from any area on the hard drive and the registry.  I am able to install and uninstall applications using that account and cannot think of any restriction on that user account that would inhibit access to any software component.  Should I disjoin it from the domain?  I also show multiple warnings around those errors.  They are all Event ID 1025 and state "The system cannot find the file specified."

Update-
I've removed the system from the domain and scanned through the local security policy.  I do not see anything that would restrict the Secure Lockdown software from enabling itself.  I then tested enabling the software under the local administrator account and the newly created portalkiosk user account.  Still the same result.  I'm going to try uninstalling and reinstalling the Secure Lockdown software.

Upon further testing, this has been found to be a bug when using Win XP. Please download the latest release posted today with the fix.

The new release worked perfectly.  Thanks for your help.

Bumping this thread as we are having the same issue, but on Windows 10 and Multi Application Edition.

Eventlog:
1022 - Could not delete Windows Registry key. Object reference not set to an instance of an object.

1041 - Could not fully enable Secure Lockdown. Ensure that you are logged on with administrator rights. Error: Object reference not set to an instance of an object. Trace Stack:    vid SecureLockdown.Functions.EnableSecureLockdown(String commandLineState, String commandLineShutdown)

Secure Lockdown:
Multi Application Edition 2.00.162

OS:
Windows 10 version 1607 (OS-version 14393.447)

I am running this on the only local admin account on that PC, and I have never had this issue prior.

Please download and install the latest release of Secure Lockdown from our website. This issue has been resolved.