SABnzbd Forums

When a download finishes on my machine I can see it repairing and extracting properly and then when it finishes extracting the file is no where to be found.  I can see "where" it is placing the downloads however I am lost.  I check all my drives (at least I think I'm checking everywere it could be).  I did change the default direcotry from C:\ to an external drive.  There is nothing in the recycle bin..

I am scratching my head over this.  The only files that remain are some samples and incomplete files.  Anyone have any idea where I can start to look?

Thanks,



Version: 0.5.3
OS: 7
Install-type: Windows Installer
Firewall Software: Win Firewall
Are you using IPV6? No
Is the issue reproducible? Yes

what are the settings in the ini  ?

What does your log tell you ?

I got something similar on my Mac so don't if the issue is exactly the same, but your problem sounds exactly the same. Found out in the folder settings of SAB (?) that the destination drive location was not the same as the actual location. SAB had it down as "whatever name 1" when in reality the HDD was just "whatever name". But the history showed the right location and without showing the 1 at the the end.

Then OSX/SAB put the extracted file in a hidden file ( under "volumes" for mac readers ). Dunno where it could be for Windows though. I had to get my Mac to show the all hidden files to find the downloads.

So maybe just try and do the same for Windows? I ended up getting a program to show the hidden files, so maybe you could do the same?

The issue on OSX occurs when people forget to mount their external drive.
When the drive isn't mounted, OSX quietly writes files to the local disk.

This issue is non-existent on Windows because there you mount a drive on a drive letter.
An unmounted drive will result in errors.

I changed the default drive to my d drive instead of d:\tv\... .  Now the files are showing up.  Not real a solution but it is an answer.  Thanks guys

shypike wrote: The issue on OSX occurs when people forget to mount their external drive.
When the drive isn't mounted, OSX quietly writes files to the local disk.

This issue is non-existent on Windows because there you mount a drive on a drive letter.
An unmounted drive will result in errors.

Yeah found that out when my drive was switched off and started again later ( or something like that ) and OSX gave it a +1 in the drive name.

Glad you  found a little result anyways Raptor3861