Secure Provisioning Tool 3.0 and windows user account controls

[jan_visser]

My employer uses SPT version 3.0 for windows 10 in a production line to flash a product that contains a RT1052 processor.

This has worked flawlessly for about 6 months. A few weeks ago we suddenly started getting failures. The tool would report "SUCCESS: Writing Image", but the product would not boot. There were no changes to the hardware or firmware of the product.

Programming the product again on a PC from the R&D department did work. Eventually we found that we could only make the SPT work on the production line if we granted the user administrator priviliges. This is why programming on the R&D PC worked, the engineers have administrator rights, while production line workers are 'standard users' with User Account Control enabled.

Is there any way of making the SPT work correctly on a windows PC with User Account Control enabled?

It is also strange that the setup worked for 6 months without problems. I suspect that a recent windows update is responsible.

Some technical information:

-Programming is done over USB.

-De processor is a RT1052.

-Flash device is set to IS25LPxxxA.

-We don't use any custom scripts, the workers just click 'write image' and wait for the tool to finish.

[liborukropec]

Hello Jan,

this might be a permission error. Once an Administrator account is used for generating scripts/binaries, they might have write access for Administrators since that time and then normal user won't have rights to modify them. E.g. for Encrypted boot type in the write script the keyblob is re-written for every device.

Please try to reset the workspace permissions (including subfolders) so the worker account has write permission:

If the problem persists, you can look to <workspace>/log.txt if you see some suspicious errors. If not, you can share it here (just one write attempt).

Hope it helps.

Regards,

Libor