Thanks for the help, I haven't quite fixed the issue but I have discovered a
little more about the problem. I opened Task Manager and selected the
Virtualization column in attempt to manually set the process to run as a
virtualized process however I found that all applications were listed as "Not
Allowed" and the Virtualization option was greyed out. This would definitely
cause the file virtualization to break.

This seems to indicate that something is disabling the virtualization
(policy perhaps), has anyone seen this before. I have checked secpol: Windows
Settings-Security Settings-Local Policies-Security Options - all the
relevant UAC policies are enabled including "UAC: Virtualize file and
registry write failures...."

"Susan Bradley" wrote:

Jesper wrote:
I would be very disappointed if this was the case.

Sorry to disappoint you, although I am conjecturing.

Are there any Path variables or registry objects File Virtualization uses
that I can check, such as the path of %LocalAppData%.

More than likely it uses the standard environment variables. There is
nothing specific to virtualization, but based on the symptoms, it is quite
certain that they are not using the LocalAppData variable. To start with, I
would fire up Process Monitor and see if I could tell what was failing.

How exactly did you move the folders? It could also be a permissions issue I
suppose.
NTFS symbolic link - Wikipedia, the free encyclopedia:
http://en.wikipedia.org/wiki/NTFS_symbolic_link
There's a KB I've seen (that I can't find right now) that talks about
this symbolic link issue.
http://rogerhendriks.blogspot.com/20...directory.html