Windows - Running as a service "Lock" command does not work

[sandstheman]

With IoTuring configured to run as a service in Windows with the local user (using nssm), the Lock command does not work and the computer remains unlocked.

When I run IoTuring directly from the terminal as my local user then the lock command works fine and the computer locks. Think this is related to how Windows runs services as their own sessions separate to the session for the actual user at the computer. So when running it as a service the lock command applies only to the service session and not the active user.

No idea if this would even be possible to fix, but though I'd report it anyway

[infeeeee]

Have you tried running as an explicit user? In NSSM on the "Log on" tab, select "This account" and type your username and password:

Maybe the "allow service to interact..." could also help.

https://nssm.cc/usage

Or do you use a different service setup?

[sandstheman]

I am using an explicit user, realise my wording might be a little ambiguous. I didn't tick the "allow service to interact with desktop option" i'll give that a go

[sandstheman]

Ok so an update - that didn't work, so "Allow Service to Interact with Desktop" is only available when choosing Local System account, so when selecting that the "Lock" command still has no effect...

[infeeeee]

Have you tried local system with "allow interact"? Does that break other things?

[sandstheman]

Yes that's the only way to select "allow interact" doesn't break anything, everything else still works fine - just the Lock command doesn't work

[richibrics]

Hi, do you still have this problem ? If not, how did you solve ?