Product: PowerShell Universal
Version: 2026.1.3.0
Not a PSU bug, but a msi installation bug, I am testing a fresh installed windows 2025.
doing the msi install variant, and the service won’t start, when I checked the box that the service will start after installation.
after some time I decieded to uncheck that box and let the installation finish. and the service still can’t be started.
at last, when I remove the service user and added the same user again, a message showed up, like the user is granted run as service right, I forgot to take a screenshot.
but anyway, it would be nice to add that to the msi in case the msi is installing on a new fresh installed OS 
A follow up bug, after I fixed the service account start as service right issue, first time I started the service, it stopped after a while, I can see it created a lot of tables in ms sql database. and system log showed very little. but when I started the service once more, it worked
Since local server permissions are technically outside of PSU and there’s many different ways to host and deploy it, I’d imagine thats why it’s not included - especially in a non interactive msi install.
These permissions are also documented in the docs for PSU, I think most enterprise users would have this as part of their SOP for building the server, or as part of group/local policy settings.
Seems more like a missing local permission than an issue with PSU.
thanks for the reply. I agree with you partly
well, in some strictly controlled enterprise environments, the permissions are not granted by default. the installer ran as admin should check any missing prereq.
this is not anyway a demand from me, maybe a slight request for improvements, as “run as service” is an essential requirement for PSU service to run.
BR
