SABnzbd Forums

I've had SABNZBD installed on 4 computers with the exact same issue.....I setup the directory for my downloads, SAB creates folders for movies, tv etc.  For some reason or another, about 50% of the time I go into these folders to look at files or to open a movie, the folder freezes and i get an error report that crashes/restarts explorer.exe  The fact that I'm having the same issue on 2-3 computers is boggling to me...I used the program for over a year without having this issue once, now it's a frequent occurrence....anyone got any ideas, do i have a setting messed up thats causing this maybe?

Thanks in advance...

I use nod32....the sabnzbd created folders are the only ones that crash explorer.  I have no viruses and each machine is running xp sp3. 

Try to examine the folder with a command prompt.
The type commands like:
cd /d d:\go\to\my\folder
dir /p

This will show you a listing of files. Maybe you'll see odd characters.

In general, if Explorer crashes, that's more a sign of an unstable
Windows installation than a SABnzbd problem.

Tried that...no strange characters.  The only reason I assume its caused by sabnzbd is because the same exact issue is occuring on 3-4 machines, all effecting the sabnzbd download directory, and on a 5th computer I'm using a different newsgroup client with the same exact XP build and I'm having no problems.  As I mentioned I was able to use sabnzbd problem free for  over a year before this started happening.....thanks again for help.

I see your point, but SABnzbd causing Windows Explorer to crash
doesn't sound really convincing.
At the very least it indicates also a serious issue with Explorer.

You've got that right.
There has always been a serious issue with windows explorer .
lol, just kidding.

i'm saying the folder created/modified by SABNZBD is making explorer crash, not the actual program....the program is creating the folder....there is a problem with the folder for some reason.  It is the only folders on any of these computers that are crashing while being viewed.  If i've replicated this issue on 4 computers someone else has surely experienced it...

With most people's system this doesn't happen.
So it's either a problem with the system or with the kind of
files that are downloaded (and unpacked).
Without more information, what can I do?
At least email me an example of an NZB file that shows this problem.
bugs at sabnzbd.org