My customer has numerous .NET applications deployed across numberous client machines in their enterprise. The .NET applications are all written internally by their development team and they all have a common design flaw: all applications write and read files from the C:\ root. Now their applications have been working for many years, and as you can imagine when Vista came out and UAC was introduced, they immediately ran into security issues. The same issue happens with Windows 7 clients, and their apps run fine if they turn off UAC.
My question is:
My customer wants to know the lowest effort workaround for solving this problem in their enterprise without having to disable UAC and increase security risks. They know that they can change their applications to read and write files to other directories which aren't blocked by UAC, but this would mean re-writing and re-deploying MANY applications. Changing the source code of all their legacy applicatoins is the an extremely large job and would like to consider that as a last resort. Is there a way to allow writing to the C:\ root with UAC on?