Share via

Files going to C:\Windows instead of VirtualStore for Non-Admin User

Anonymous
2019-04-15T18:11:52+00:00

We have a non-admin user on Windows 7 Professional that is having issues with a legacy software title. Anytime the user attempts to make a change in the system, a "write" error is presented stating that the program is "unable to write to" the specific file; the error doesn't include the path, but I was able to find the location.

The issue is that the program is trying to write INI files to C:\Windows rather than the VirtualStore path. Being that the program doesn't run with elevated privileges and he's a standard user, he is unable to write to said path. Any ideas why this would be happening or how to redirect the per-user location? I really don't want to give out admin privileges if I can avoid it.

Windows for home | Previous Windows versions | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-04-15T18:30:28+00:00

    The program is trying to write INI files to C:\Windows rather than the VirtualStore path.

    What exactly is your "Virtual StorePath"?

    C:\Users\Username\AppData\Local\VirtualStore

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-04-15T18:25:33+00:00

    The program is trying to write INI files to C:\Windows rather than the VirtualStore path.

    What exactly is your "Virtual StorePath"?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-04-15T18:48:57+00:00

    Does the folder Windows exist in your virtual store?

    For an application to make us of the virtual store technique, it must meet a number of requirements. you can see them here. Does your legacy software meet them?

    If your application tries to use its own folder in C:\Windows then you could create a symbolic link such as C:\Windows\MyLegacyProg whose physical storage location lies in an unprotected area.

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more