Welcome Guest ( Log In | Register )

> foobar2000 Tech Support Forum Rules

Please read foobar2000 Tech Support Forum Rules before posting and comply with all the points.
Failure to provide all the information pointed out in the above document in your post is considered wasting other people's time and in extreme cases will lead to your topic getting locked without a reply.

See also: Hydrogenaudio Terms of Service.

Could not access profile folder
post Oct 1 2010, 06:03
Post #1

Group: Members
Posts: 7
Joined: 5-September 10
Member No.: 83636

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?
Go to the top of the page
+Quote Post
Start new topic
post Oct 2 2010, 07:07
Post #2

Group: Banned
Posts: 1310
Joined: 4-January 09
Member No.: 65169

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?

This is HA. Not the Jerry Springer Show.
Go to the top of the page
+Quote Post
post Jul 21 2012, 16:08
Post #3

Group: Members
Posts: 5
Joined: 13-July 12
Member No.: 101415

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
Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 30th November 2015 - 04:43