"Unable to write to this location" error

Hi
I have been using Kodak Imaging (last provided by MS with windows XP) successfully on every operating system since XP. The program files are saved in Programs (x86), the ocx files are registered using the command prompt and hey presto, it works fine.

On windows 10 too until I get this error today on trying to save output from the program (an appended page to existing tif file):

"Unable to write to this location. Possible causes may be low disk space, write protection or invalid filename."

I have just reregistered all the ocx files and made sure that the program is still running with administrator privileges. No go. I can find nothing on google that matches an error like this..so far.

Can anyone with more knowledge than I give me a pointer as to where to start. (I have already restarted machine - first thing I did).

Thanks in advance.

UPDATE: Is only happening with existing files when trying to append a page - something I have been doing for years. Creating a new file saves ok in the same location as the problematic existing file.

pepanee said:

It's probably that you have to have complete Ownership of that folder, so Windows would write to it.
Windows 10 uses a different folder to save program files' data to.
In XP, it used to write at: C:\Program Files & C:\Program Files (x86)
But in Windows 10, whenever files need to get saved to "Program Files", Windows 10 writes those files at somewhere in: C:\Users\Admin\AppData

Yet if you have COMPLETE ownership of that folder in Program Files, then Windows 10 will write there.

Hi thanks. Not actually writing to the program files folder, unless the program is writing something there when I save a file elsewhere. But will check on ownership of folder locations to see if that works. Thanks again.

pepanee said:

There's a possibility that the program is trying to write some files there, like updating its settings every time the program runs.

One thing you can try is to make a copy the whole program's directory on the Desktop or something, and run the program from that folder. Does it say the same thing?

1. Hmmmm, I wonder if I should have done this. I took ownership of complete "Program Files (x86)" folder. And still does not allow save. Might have been better to just limit it to the folder that this program may be writing too....? Are there any down sides to what I have done and can it be reversed?
2. The program does not appear to have a folder in any of the appdata folders.

This was working ok the week before on this machine as it has done for years.

UPDATE:
Copying the file to desktop, appending page works there and allows saving. So you are right it looks like something to do with location permissions. Should a restart required after applying 'take ownership' registry entry?

pepanee said:

1) Hmm. It's best not to have ownership of the whole Program Files folder. See if you can do a System Restore to the last one. Search for System Restore.

2) There is no appdata folder for it because what I understood was that you said it's a really old app, which means that the data that gets saved for the app wasn't programmed to have a folder in the appdata folder.

If it was working well just a week before, then try uninstalling/reinstalling the program instead.

Thanks but as stated previously there is no installation routine. Files are just saved on the hard drive and the ocx files registered manually using command prompt, which I have already tried.

Still haven't solved the write issue for Kodak Imaging program but have found a registry key for 'Restore Ownership'
http://www.askvg.com/add-restore-own...vista-7-and-8/

Solved eventualy but now cannot remember how. Sorry guys. Not that many people will still be using this very useful document manager.