you can send me EXE for windows for test, i will make it fast
Sorry I don’t have access to that file myself.
Is the problem on the updater side or the storagenode binary itself?
I just did a clean install of v1.42.3 and the updater runs fine and reports:
2021-11-04T20:35:53.729+0100 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.42.3"}
2021-11-04T20:35:53.729+0100 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2021-11-04T20:35:55.207+0100 INFO Current binary version {"Service": "storagenode", "Version": "v1.42.3"}
2021-11-04T20:35:55.207+0100 INFO Version is up to date {"Service": "storagenode"}
2021-11-04T20:35:55.459+0100 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.42.3"}
2021-11-04T20:35:55.459+0100 INFO Version is up to date {"Service": "storagenode-updater"}
problem with storagenode itself, i do not use updater at all.
Yeah seems like something with the service itself, the binary started via the command line runs fine.
yep. in powershell (run as admin) from folder where storagenode.exe file, execute command
.\storagenode.exe run --config-dir “C:\Program Files\Storj1\Storage Node\”
and it works.
but still not running as windows service.
We are currently testing out a fix and hopefully can release it shortly in an point release v1.42.4 
3 Likes
Version v1.42.4 is now in rollout!
For those of you that have stuck services, please kill the storagenode processes (via the Details Tab) and then restart the updater. That should hopefully do everything in right order then, including a successful storagenode start!
1 Like
first test node working.
and, I’m haven’t updater at all.