Support Forum

Thanks for the help shypike.

And fixed. Seems "take ownership" doesn't remove or override inherent security from previous OS installs. all my HD's think my previous OS owns it still. Now to change all my drives and remove this "lock" symbol from my folders :/

OK so it displays "Can't write to logfile"

I have access to the logfile and my user account is the owner of the file. hmmm

Aezrith wrote:So the .ini is in it's appdata/sabnzbd/sabnzbd.ini location. Nothing in the program folder itself. The startup shortcut has " -b0" at the end.

My user account has full access to the .ini and program folder.

I just removed the " -b0" extension, results are the exact same.

So the .ini is in it's appdata/sabnzbd/sabnzbd.ini location. Nothing in the program folder itself. The startup shortcut has " -b0" at the end.

My user account has full access to the .ini and program folder.

I'll have to check the extention when iI get home. As for the configuration files, everything is in the correct place (app data folder). several reinstalls and even changing the. ini location didn't help.

Normally I put a shortcut in the startup folder. I'm now forced to right click, run as administrator.

Version: 0.7.6 OS: Windows 7 Ult x64 Install-type: Windows Installer Skin (if applicable): smpl skin Firewall Software: Windows Firewall / Avira (exceptions have been made in both programs) Are you using IPV6? No Is the issue reproducible? Yes Sab will open and wait for about 5 seconds, then shutdow...