Please, stop the storagenode. If it’s a docker, then remove the container.
Please, remove everything from the S:\Storj4, include config.yaml.
Add a SYSTEM user to that folder with full rights and make it an owner, then run the storagenode and check your logs.
If you use a standalone binary, you must run storagenode.exe setup with all needed parameters first. You can see them with storagenode.exe setup --help
If you use a Windows GUI installer, then no one action is needed, except adding a SYSTEM user with full rights to the folder and make it an owner, then restart the storagenode service.
I checked with the latest installer. It will create all needed files only on setup.
If the folder for data (in your case it is a root of the disk) is empty after the setup (was cleaned or have an error during setup, etc.), the attempt to start a service will fail.
It was implemented to do not start with empty storage in case of disk disappearing or other disaster and do not disqualify your node.
So, in this situation, when access rights now are fixed, you should reinstall the storagenode.