[Bug]: I can't use PostgreSQL with Herd on Windows 11, Herd 1.11.0

[ahajicek07]

Platform

Windows

Operating system version

Windows 11 Pro 10.0.22631 Build 22631

System architecture

Intel (x86)

Herd Version

1.11.0

PHP Version

PHP 8.3

Bug description

I can't use PostgreSQL with Herd, it was working, but when I updated to the latest version I can't run it anymore. When I try to turn on PostgreSQL services it turns back to red with error log.

Steps to reproduce

I've tried to delete and reinstall the service, and it doesn't work.

Relevant log output

Starting PostgreSQL (PostgreSQL) on port 5432 with datapath 7ab49abb-5c94-4232-ab07-466157cf5d56Execution of PostgreSQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises.  See the documentation for
more information on how to properly start the server.

[mechelon]

Can you try to force-quit all PostgreSQL services and then restart, as shown in the screenshot?

[ahajicek07]

So I got it to work on 1 of 2 computers. My home computer worked by start herd and not using, "run as administrator" but it doesn't work on my work computer as a way to get this to work.

So I did the force quit, and deleted the service and tried to reinstall the PostgreSQL and it gives me this error

"Herd was unable to setup the service. Please check your log files and try again."

Then I get the same error when I try to start it in the error log:

"Starting PostgreSQL (PostgreSQL) on port 5432 with datapath 52d6303c-63e9-4786-b0fe-292c45b38928Execution of PostgreSQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises. See the documentation for
more information on how to properly start the server."

[mpociot]

@ahajicek07 but you are not running Herd as an Administrator, right?

[ahajicek07]

@mpociot I was able to get it to work on my work machine. This was the difference, where-as on my home machine fixed things to just run herd without explicitly clicking 'run as administrator' by right clicking herd and clicking 'run as administrator,' at work, because its on a 'work domain' and my user is an 'administrator' I had to right click herd and click 'Run as a different user' and login to a new user that isn't my default at work 'administrator,' Doing that I can't access the user folder I currently have my projects, but I'll just move them. Hopefully this fixes things for now since I can now run PostgreSQL.

P.S. Thank you for helping me with this, and beyond excited for what you're doing with dumping all the variables on the laravel error page you've been demo'ing on Laravel. Would be a huge productivity boost when working through new code.