Hi @tkctkc,
Please post the last 20-30 lines from the storagenode.log file. The most recent entries will show the ERROR or FATAL reason. By default the log location in Windows 10 is C:\Program Files\Storj\Storage Node\storagenode.log
The delay will not solve the problem of external address being not reachable from outside, more like your public IP has changed.
The delay on service start can solve only the one problem - if the storagenode service is failed to start after reboot because system services are not up and running yet.
Please, compare specified public address in the contact.external-address: of the "C:\Program Files\Storj\Storage Node\config.yaml" with the IP there: Open Port Check Tool - Test Port Forwarding on Your Router
If it has changed - you need to update it in the config file and restart the storagenode service.
To update config file it’s better to use Notepad++ (the usual Notepad could broke the config), you should explicitly save changes, the Notepad++ will not offer to save them on close.
To restart storagenode service after the change you can use either Services applet or elevated PowerShell:
Restart-Service storagenode
If your public IP has changed, It’s better to configure the DDNS address instead: Port Forwarding - Node Operator
I would recommend to configure your router to update that DDNS address (the configuration for popular DDNS providers is usually placed into DDNS section on your router).
Public IP was the issue, I checked the correct port is being allowed in and forwarded to the node, all OK! But completely missed that the IP had changed, compared to config.yaml. It was totally different!