Windows native binary creates double /complete/complete/ path in WebDAV

[bubbly1210]

When running the native Windows binary with complete_dir: /complete in config.yaml, files are placed at /webdav/complete/complete/Movies/ instead of /webdav/complete/Movies/.
This breaks AIOStreams integration which hardcodes the lookup path as /complete/Movies/ per the official wiki.

Am I doing something wrong here? Been at it for hours

Thanks!

[javi11]

Which version are you using?

[Treacherouz]

I can confirm this bug and add some additional findings from extensive testing on Windows.

Environment:

• Windows 11 Home (native binary, not Docker)
• Altmount v0.2.0 stable, also tested the July 1 dev build (02528c0a)
• Used as a Stremio/AIOStreams backend via the SABnzbd-compatible endpoint
• config.yaml: sabnzbd.complete_dir: /complete

Finding 1: The duplication happens with every complete_dir value, not just /complete

With complete_dir: /complete, imports succeed but content lands at /complete/complete/<category>/...:

INFO Successfully processed single file {"virtual_path":"/complete/complete/TV/<release>.mkv"}

I then tested complete_dir: / hoping to avoid the duplication. The value still gets doubled — the resulting // prefix produces a malformed Windows path and the import hard-fails at mkdir instead:

failed to create directory //TV/<release>/...: failed to create metadata directory
C:\altmount\metadata\TV\<release>\...: The system cannot find the path specified.

(A blank value is rejected by the config UI, so there is no value that avoids the doubling.)

Finding 2: The July 1 dev build does not fix it, and adds a new blocking issue on Windows

On the dev build, every NZB submitted via the SABnzbd endpoint fails before import even starts, at the new temp-queue staging step:

ERROR Failed to move NZB to persistent storage {"error":"rename
C:\\WINDOWS\\SystemTemp\\altmount-uploads\\TV\\<release>.nzb
C:\\WINDOWS\\SystemTemp\\.altmount-queue\\<release>.nzb:
The process cannot access the file because it is being used by another process."}
ERROR Failed to ensure persistent NZB during queue addition

This repeats on every retry indefinitely. I ruled out AV interference: it persists with Windows Defender exclusions on both temp folders and with Malwarebytes fully disabled. It looks like the file is still held open (by Altmount itself?) when the rename is attempted — a classic Windows-vs-Linux file-locking difference. Setting import.import_dir explicitly did not change the paths used by this code path; the SABnzbd upload flow appears to use C:\WINDOWS\SystemTemp regardless. I reverted to v0.2.0 because of this.

Finding 3 (minor): category segment can also be doubled

During WebDAV lookups of failed/fallback items I also observed a doubled category segment: /complete/complete/TV/TV — possibly related to the same path-joining logic.

Current workaround: since I build AIOStreams from source, I patched its Altmount content prefix from /complete to /complete/complete to match where the files actually land. Streaming then works end-to-end, so the imports themselves are fine — it's purely the path construction that's off.

Hope this helps!