Your Windows installer is fundamentally broken for secondary-drive (non-C:) installations on high-spec server hardware (Supermicro X10DRU-i+). Despite reaching Difficulty 37 on dual Xeons, the identity.exe tool fails to generate node.cert and node.key locally, and the service repeatedly throws ‘Invalid configuration file key’ errors for valid S: drive paths. This is not ‘streamlined’; it’s non-functional trash.
X10DRU-i+'s are ewaste, but I’d still expect the install to complete cleanly. Could you include more of the docker logs from when you try to start your node, and let us know what version of Windows you’re using?
I’m sure we can figure it out.
High spec, lol. I agree with Roxor, it’s an e-waste.
Hardware perceived power is not a problem.
This is.
You OS is garbage, not the software.
I you provided details on whaat command you ran, and what output you received, under what configuration, someone may be able to help you.
Otherwise it’s a rant thread about nothing.
Hello @Solitude,
Welcome to the forum!
Please provide a command which you run.
Please also specify how your S: drive is connected? Please note, the node software doesn’t support any network filesystems, they may work but not supported.