[BUG] - Cardano Node Fails to Start: "DiffusionErrored CreateNamedPipe" Error on Windows 11

[OlafTheDread7]

Internal/External
External

Area
Other (Node Startup)

Summary
Cardano node fails to start with "DiffusionErrored CreateNamedPipe" error due to insufficient permissions, despite extensive troubleshooting.

Steps to reproduce

1. Download and extract cardano-node-10.1.4-win64.

2. Create C:\cardano-node\db directory.

3. Run the following command from C:\cardano-node\bin:

   .\cardano-node.exe run --topology C:\cardano-node\share\mainnet\topology.json --database-path C:\cardano-node\db --socket-path C:\cardano-node\db\node.socket --host-addr 0.0.0.0 --port 3001 --config C:\cardano-node\share\mainnet\config.json

4. Observe the error message:

   [Chaney:cardano.node.DiffusionInitializationTracer:Critical:3] [DATE/TIME] DiffusionErrored CreateNamedPipe ('C:\cardano-node\db\node.socket'): invalid argument (The filename, directory name, or volume label syntax is incorrect.)
   

Expected behavior

The Cardano node should start successfully and begin syncing with the blockchain.

System info

• OS Name: Windows 11 Home
• OS Version: 23H2 (OS build 22631.4602)
• Node version: 10.1.4 (cardano-node-10.1.4-win64)
• CLI version: (Not applicable, as the node fails to start)

Screenshots and attachments

(Attach screenshots of any relevant error messages, log entries, or permission settings)

Additional context

• Tried various troubleshooting steps, including running as administrator, adjusting folder permissions with icacls, disabling antivirus and firewall, performing a clean boot, reinstalling the node, and checking for symbolic links and long path names.
• No relevant error messages found in Event Viewer logs.
• The error message suggests a permission issue, but even after extensive permission adjustments, the error persists.

This issue is preventing me from running a Cardano node. Any help in resolving this would be greatly appreciated.

[carbolymer]

I think you need to follow the pipe name convention \\.\pipe\somepipename for the socket name

https://learn.microsoft.com/en-us/windows/win32/ipc/pipe-names