Runtime files getting created in local windows folder
Hi,
I am working on an app that needs to create runtime files in the Windows folder. I've added some as empty files into the Virtual package (CSIDL_WINDOWS) and the application updates them fine.
However it needs to create dynamically named files (depending on the way the application is used) to save user settings. The problem is that its failing to create the files in the virtual environment and even if I add an empty file into the virtual env with the correct name it fails to update it. It will always try to create the file in the local C:\Windows folder.
Anyone have any ideas?
Cheers,
I am working on an app that needs to create runtime files in the Windows folder. I've added some as empty files into the Virtual package (CSIDL_WINDOWS) and the application updates them fine.
However it needs to create dynamically named files (depending on the way the application is used) to save user settings. The problem is that its failing to create the files in the virtual environment and even if I add an empty file into the virtual env with the correct name it fails to update it. It will always try to create the file in the local C:\Windows folder.
Anyone have any ideas?
Cheers,
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
kkaminsk
15 years ago
Hmm, I wonder if it is sneaking out of the sequence somehow. Have you done a procmon trace to see exactly what process is writing these files? Can you determine if this process is running inside the sequence or did the application call something outside of the sequence that didn't launch inside the sequence.
Posted by:
ChluainEois
15 years ago
Thanks for the tip, but I checked again and the process is running inside the sequence and its the same process that opens and writes other INI files in the virtual environment.
Posted by:
kkaminsk
15 years ago
Ah, this is probably because your application is creating random file names in a folder not set to be fully virtual. The problem is setting the windows folder to be virtualized will probably break your application. I havent worked with the application compatibility shims to know if you can redirect calls for one file type such as .ini files but that might be something to explore.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.