Could not access profile folder Options

[Cesium]

I'm trying to start foobar2000, but I keep getting an error message that says:

foobar2000 encountered an error

Could not access profile folder

I tried reinstalling and Google, neither of those helped. Any ideas?

[shakey_snake]

Do you have a folder at the system location: %appdata%\foobar2000 ?

Do users have read permissions to that folder?

Or did you install fb2k in portable mode?
did you install it somewhere where users have read permissions?

This post has been edited by shakey_snake: Oct 1 2010, 19:11

[Cesium]

I do have a folder there. Users do have read permissions to the folder, or I think so. How can I check?

Fb2k was not installed inportable mode.

It is installed in the default directory.

[Robertina]

I do have a folder there. Users do have read permissions to the folder, or I think so. How can I check?

Right-click the folder in question, choose the security tab and check the permissions you have (or don't have)...

Edit: you also need write permissions for that folder, read permissions are not enough.

This post has been edited by Robertina: Oct 2 2010, 05:35

[Cesium]

Yes, I have full control over all the permissions. All the things are checked for "Allow."

[Robertina]

What version of foobar do you use?
Did you an upgrade or a fresh installation?

[Cesium]

Version 1.1. Did a full re-installation.

[Robertina]

May I suggest to deinstall foobar2000, to delete both the program folder and the %appdata%\foobar2000 folder and then to install it again? If I understand you correctly you have not been able to run foobar successfully till now so that I conclude you wouldn't lose any personal settings?

Also do you use any Security Suite which might block foobar's access to certain folders?

[noway]

in version 1.1.14 beta 1 and 1.1.13 (haven't tested earlier ones)
same error "could not access profile folder" occurs when:
1) foobar is already running
2) you try to feed it some files, but executing it from the same physical location which is symbolically different, e.g. from a symlink or junction
and i figure it doesn't matter whether it's a portable installation or not

for test case:
1) install foobar at c:\bin\foobar\
2) mount c: as a subfolder on d: mountvol d:\mycdrive \\?\{volume c: guid goes here...}
2a) or otherwise: mklink /j d:\mycdrive c:\
3) make a symlink for easy /bin access: mklink /s d:\bin mycdrive\bin
now you have the same foobar in 3 symbolically different locations: c:\bin\foobar, d:\bin\foobar and d:\mycdrive\bin\foobar
4) start foobar from any of those locations
5) try to run it from any other without closing the first and you'll get this bug

and an obvious workaround is: to put the same symbolic location into all of your shortcuts, file associations, shell scripts, etc.
and it better be a physical location or the one with less reparse poins on its way
for the 2a) case this should be c:\bin\foobar, while for the 2) case any of d:\mycdrive\bin\foobar and c:\bin\foobar would probably do

[Madrusnl]

I have also had this problem (Windows 7 x64). I installed foobar2000 with elevated rights and "could access profile folder" appeared actually to be write access problem for normal user on the installation directory. I added the write permissions on this folder and - voila! - foobar2000 could start without any further problems.