Maybe too late, but I found a solution after some confusion on this Windows error:
According to the docs, 'you can run multiple times, but only one worker will do anything'.
When you start nginx, it creates a .PID file in the logs folder. When you quit, it deletes that file.
If you start more than once, it creates only one .PID file. When you quit the first time, that file gets deleted. Subsequent quits cannot find the file, thus the error.
The confusion (at least in my case) originates from a lack of messaging. When you use "start nginx", there is no confirmation message (e.g. "nginx is now running"). That's why I tried more commands, and ended up with too many processes.
(also maybe) Make sure your nginx directory, and all subdirectories are not Read-Only.
(also maybe) Be sure to run as admin.
According to the docs, 'you can run multiple times, but only one worker will do anything'.
When you start nginx, it creates a .PID file in the logs folder. When you quit, it deletes that file.
If you start more than once, it creates only one .PID file. When you quit the first time, that file gets deleted. Subsequent quits cannot find the file, thus the error.
The confusion (at least in my case) originates from a lack of messaging. When you use "start nginx", there is no confirmation message (e.g. "nginx is now running"). That's why I tried more commands, and ended up with too many processes.
(also maybe) Make sure your nginx directory, and all subdirectories are not Read-Only.
(also maybe) Be sure to run as admin.