Forum Discussion
CreateProcessAsUser Error 5 - ServiceUI.exe
Hi All I've recently updated my SCCM Site version to v1910, since performing this update i've been having issues with my Upgrade Task Sequence. Previously i've had a command line step in the ...
What OS are you running this on? 1809? 1909?
We had issues with our Splash Screen as well when running on 1909.
There is change in how powershell uses run spaces in 1909. More Details here:
https://smsagent.blog/2020/03/12/windows-10-splash-screen-issue-fixed-for-w10-1909-configmgr-task-sequence/
I'll give this a try, for more information though..
This has only began happenning since upgrading from SCCM 1906 to SCCM 1910, the Operating systems are on v1803 and upgrading to v1909 🙂
Ok, our Splash screen (which is completely PowerShell) didn't have any issues between any of the CM Upgrades.
https://garytown.com/windows-splash-screen-for-the-task-sequence-progressFeel free to take a look. There have been changes in the TS engine with each build, but I haven't seen any issues with any of the places I've used ServiceUI.exe in my testing.
If you use ServiceUI to launch a Command Prompt, do you get the same issue? Basically do you get error anytime you use ServiceUI in your TS, or just with your Splash Screen?
Other examples of using ServiceUI: https://garytown.com/launch-application-in-task-sequence-in-os-serviceuigwblok - Thanks for the response, So after more testing.. I can run ServiceUI.exe manually as Domain admin and it will launch programs succesfully.
However when i use PSEXEC and run ServiceUI as the System Account, it times out (even when using it to launch something as basic as notepad.exe)
So this points to me that System doesn't have the permissions to launch a process as a user (Error 5 above).. However i have no idea what permissions are required for this.
After more investigation, and talking with a Microsoft MVP.. the outcome for us has been this.
ServiceUI.exe is an ancient program with no support anymore, and is seen as a security flaw.
Therefore it could be a case of the SCCM Upgrade has changed the Task Sequence engine, which is recognising ServiceUI.exe as a security risk and blocking it.
We are looking into reverting to Windows Servicing to perform our OS updates instead.
