UAC - File Virtualization (VirtualStore missing)

[Simonfr]

I’m currently troubleshooting a problem with UAC - File Virtualization in
Vista SP1. File Virtualization is not working in Vista and is breaking some
applications that previously tested good. The difference with this build is
that the C:\User folder has now been relocated to the D:\User. It now seems
that Vista is not creating the VirtualStore Folder & and respective
sub-folders under %LocalAppData% (which is pointing to the correct path on
D:\). I’m wondering if Virtualization has some known problems if the User
Data folders have been relocated, and if there’s something I can do.

 

[Jesper]

I wouldn't be one bit surprised if there is code that looks for a language
specific version of %homedrive%\users and that is what causes virtualization
to break.

 

[Simonfr]

I would be very disappointed if this was the case.
Are there any Path variables or registry objects File Virtualization uses
that I can check, such as the path of %LocalAppData%.
I have confirmed that secpol shows UAC File & registry Virtualization to be
enabled, it just doesn't appear to be doing it's job. There is no
VirtualStore folder and additionally no events in the UAC-FileVirtualization
event log.

 

[Jesper]

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.

 

[Susan Bradley]

Sorry to disappoint you, although I am conjecturing.


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/2007/09/moving-vista-users-directory.html

 

[Simonfr]

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...."

 

[Simonfr]

False alarm...I didn't realise I was logged in as the adminstrator, this is
why the Virtualization was set to "Not Allowed".

 

[Rexus]

Hi Simonfr, I encountered the issue recently.
Our "Users" profiles folder moved from C: to another disk, and virtualization stopped to work immeditedly.
I even called the Microsoft Support to resolve the issue.
The solution was to move %LocalAppData% to C:, while retending profiles on that unsystem disk.
Have you solved it in other way ?