Virtualization of registry and files?

  • Thread starter Thread starter Norman Diamond
  • Start date Start date
N

Norman Diamond

Windows Task Manager has a column labelled Virtualization. I've read that
this means virtualization of some registry keys and files. For example if a
program tries to write to a registry key where it has no permission or a
file where it has no permission, Vista might create a key or file in a
location owned by the user, and redirect the program's access to the
virtualized location.

I've read that this kind of virtualization is a temporary measure for poorly
written legacy programs and this temporary measure will be removed in a
while.

This kind of virtualization is not needed for programs that were written
with security in mind, right? This kind of virtualization is not needed for
programs that are designed for Windows Vista, right?

Is Windows Mobile Device Centre a poorly written legacy program? It wasn't
designed for Vista? Or am I misunderstanding the meaning of the
Virtualization column?
 
In message <#[email protected]> "Norman Diamond"
Windows Task Manager has a column labelled Virtualization. I've read that
this means virtualization of some registry keys and files. For example if a
program tries to write to a registry key where it has no permission or a
file where it has no permission, Vista might create a key or file in a
location owned by the user, and redirect the program's access to the
virtualized location.

I've read that this kind of virtualization is a temporary measure for poorly
written legacy programs and this temporary measure will be removed in a
while.

This kind of virtualization is not needed for programs that were written
with security in mind, right? This kind of virtualization is not needed for
programs that are designed for Windows Vista, right?

Is Windows Mobile Device Centre a poorly written legacy program? It wasn't
designed for Vista? Or am I misunderstanding the meaning of the
Virtualization column?
Click to expand...

Virtualization is enabled for all executables by default, unless the
executable is running elevated or it uses a manifest to indicate
virtualization is not required.

Many applications will show that virtualization is enabled when they
only attempt to write to permitted locations, this is normal behaviour.
 
DevilsPGD said:
Virtualization is enabled for all executables by default, unless the
executable is running elevated or it uses a manifest to indicate
virtualization is not required.
Click to expand...

OK, I think I understand. If I want my programs to look like well behaved
programs when listed in Task Manager, I have to add something to a manifest.
Many applications will show that virtualization is enabled when they only
attempt to write to permitted locations, this is normal behaviour.
Click to expand...

Isn't this irrelevant? If I really understood about the default, then the
attribute shown in Task Manager only depends on the manifest, right?
 
In message <[email protected]> "Norman Diamond"
OK, I think I understand. If I want my programs to look like well behaved
programs when listed in Task Manager, I have to add something to a manifest.
Click to expand...

That's correct.
Isn't this irrelevant? If I really understood about the default, then the
attribute shown in Task Manager only depends on the manifest, right?
Click to expand...

Yes, but if there is no manifest specifying virtualization, the
assumption is that virtualization might be needed, so it's enabled.

In other words, whether an application is well behaved or not won't
dictate whether it is listed with virtualization being enabled or
disabled, the manifest itself dictates that.

If your application is properly written, there is no explicit need to
turn virtualization off, aside from a *minor* performance boost and the
apperance of not needed virtualization.
 
Back
Top