Is it possible you skipped a few versions when updating?
If so, you may have skipped the version of the node that created the file in the first place. I think you should be able to fix this by running the setup command manually.
I’m not entirely sure whether that would overwrite other stuff. So best do that in a different folder.
Fair warning, I haven’t tried this. But I think this should create the files required for a new node, which will likely include that missing file you need. You can then just copy that one over and start the node as normal.
Make sure you actually specify the path to your identity.cert file and create the tmp-path folder first.
You might want to wait until someone from Storj Labs confirms this might work. Perhaps @Alexey can point out if I’m on the right track here?
You skipped several versions during update (maybe your updater was not running?)
The fix, mentioned by @BrightSilence should work.
It will fail if you specify the existing location for the config because the config.yaml there (it’s made for to prevent the start when something is wrong with the drive).
To simplify process, you can add a --storage.path D:\ to the setup command, for example: