"cannot create file" in programs folder

rivre · 29 Jun 2016

I'm new to Windows 10 and I'm installing some of my software. I came across this error today running Audio Identifier:

The Application encountered an error! (cannot create file "C:\Program Files (x86)\Audio Identifier\settings.xml". Access is denied.

I'm guessing it wants to create the settings file in the programs folder itself and Windows is blocking it? What can I do to allow it to do this? Is there a permissions setting I can change? I'm wondering if I'm going to come across this issue with some of my older software.

In properties for that folder it is set to read-only. I tried unsetting the read-only but as soon as I set it and then re-open properties it's set back to read-only again. What can I do?

Would it be best to just uninstall the program and re-install it to another folder outside "Program Files"? I have a programs folder set up for standalone portable programs. I'd still like to know how to allow the file to write in the Program Files folder though for future reference, since I'm betting I'll come across this again soon.

pyramid10 · 30 Jun 2016

Audio Identifier is a very 'old' Russian program (2008 and beta?).

You might try and install using Compatibility Mode.

I generally prefer to install into custom folders outside of Program Files. I think .msi don't usually offer such options.

Slartybart · 30 Jun 2016

rivre said:

I'm new to Windows 10 and I'm installing some of my software. I came across this error today running Audio Identifier:

The Application encountered an error! (cannot create file "C:\Program Files (x86)\Audio Identifier\settings.xml". Access is denied.

I'm guessing it wants to create the settings file in the programs folder itself and Windows is blocking it? What can I do to allow it to do this? Is there a permissions setting I can change? I'm wondering if I'm going to come across this issue with some of my older software.

In properties for that folder it is set to read-only. I tried unsetting the read-only but as soon as I set it and then re-open properties it's set back to read-only again. What can I do?

Would it be best to just uninstall the program and re-install it to another folder outside "Program Files"? I have a programs folder set up for standalone portable programs. I'd still like to know how to allow the file to write in the Program Files folder though for future reference, since I'm betting I'll come across this again soon.

It's probably a poorly written installer - it's definitely old.

I would not change the security on Programs Files (x86) or Program Files. That would only open up your system to possible intrusion.

I found a portable version: http://www.portablefreeware.com/?id=1295
It does not have to live in Program Files (x86). You said you have a folder for portable apps - cool.
Use at your own discretion.

From what I read about Audio Identifier, you can get the same information from File Explorer if you add some columns.
I don't know where AI gets the Quality attribute though.

Navigate to your user Music folder (C:\Users\Dad\Music for example)
Change view to Details
Right click an existing column
Pick More... at the bottom of the list
Place a tick in the attributes you want to see
Press OK

Arrange the columns to your liking (size, position, and sort by)
Open the blue File menu
Select Folder optins
Press the View tab
Press the Apply to folders
answer yes

Now any folder of type Music will display the attributes in the columns you selected.

topgundcp · 30 Jun 2016

Would it be best to just uninstall the program and re-install it to another folder outside "Program Files"? I have a programs folder set up for standalone portable programs. I'd still like to know how to allow the file to write in the Program Files folder though for future reference, since I'm betting I'll come across this again soon.

Make it portable. Just download the AudioIdentifier_setup.exe and use 7-zip to unzip to where ever you want then run:

"cannot create file" in programs folder-b.png

"cannot create file" in programs folder-.png

rivre · 30 Jun 2016

Some great tips in here. Thanks very much!

I found that selecting "run as administrator" in the file properties of the .exe in the Program Files folder works well for this issue. It wanted to write the settings file in the Program Files folder and for whatever reason Windows 10 didn't like it. Giving the .exe file administrator rights allows it to write to the folder no problem. I think it should be safe to do that with an old piece of software like this without worry. I appreciate all the tips though. I grabbed the portable version in case I decide to use that instead, and the tips on setting the view properties is definitely useful.

rivre · 30 Jun 2016

topgundcp said:

Make it portable. Just download the AudioIdentifier_setup.exe and use 7-zip to unzip to where ever you want then run:

I didn't know you could do that. Thank you for the tip!

LMiller7 · 30 Jun 2016

rivre said:

Some great tips in here. Thanks very much!

I found that selecting "run as administrator" in the file properties of the .exe in the Program Files folder works well for this issue. It wanted to write the settings file in the Program Files folder and for whatever reason Windows 10 didn't like it. Giving the .exe file administrator rights allows it to write to the folder no problem. I think it should be safe to do that with an old piece of software like this without worry. I appreciate all the tips though. I grabbed the portable version in case I decide to use that instead, and the tips on setting the view properties is definitely useful.

In programs written for XP and older systems it was a common, but not recommended practice, to save application settings in the program files folder. Some newer applications do this as well. But starting in Vista security was tightened up and standard accounts no longer have write access to the program files folder. With UAC enabled (the default setting) even admin level accounts will have standard user rights by default. That means they will not be able to save their settings. The easiest solution is to run the application as Administrator which has this right.