KACE Product Support

we had this issue and got the following response from Kace support. 

If the issue is the application crashing on xp when ran using system

account (like the kbox does) here is the workaround:

Based on the facts and our investigation it is confirmed that the new

framework (released sometime in 2010) uses APPDATA environment variable for

creating temporary files for extracting and executing the update.

The assumption made at that point of time that all users will have this

variable defined. But in case of Windows XP it seems the assumption fails

when run as system account. Since the environment variable APPDATA is not

set for system account it crashes when attempts were made to create folder

for temporary use. We are working within the team to look at other possible

alternatives and come up with a solution. But whatever the solution may be,

it will not solve the issue in hand. All updates that are created with the

framework will still fail till they are re-created with the rectified

framework.

In order to resolve the issue it requires that in Windows XP systems which

crash at the moment need to have the environment variable APPDATA defined.

I did some research and found that the right APPDATA location for system

account is C:\Windows\system32\config\systemprofile\Application Data. If

this environment variable is available for system account then the issue

will not occur."

Going forward the new frame work will be fixed for new drivers, but

existing drivers will need to use a workaround for now:

The workaround:

0. Import the Attached the kscript file: Script-99.kpkg

- Copy the attached file into the \\<KBOX_HOST>\clientdrop directory

(Please make sure SAMBA Share is enabled)

- Go to Settings -> Resource tab -> Click on Import K1000 Resources

- Choose the script called: APPDATA Fix

- This will import a script called APPDATA Fix which will set the APPDATA

enviornment variable using registry key

1. The local system user will need to setup the APPDATA envionronment

variable.

2. Import the following kscript, what the kscript does it actually does is

the following:

- It will run a registry file to set the APPDATA varilable for the local

system user to: "C:\\WINDOWS\\system32\\config\\systemprofile\\Application

Data

- Please note that the script will need to be able to run as a

administrator that has registry modification rights

3. Reboot the machine to take affect

4. Run your DELL or other drivers, it should work now.

Kace QA tested it here. 

I asked almost the exact same question a few days back and did not receive an answer.  We received errors just like this one, and were deploying the updates globally.  After our experience, and reports from others here of similar errors, we ended up turning it off.

If someone could answer this, I would also appreciate it.