Unknown hero in Windows-virtual storage

Unknown hero in Windows-virtual storage this article only provides an idea with no other intent. However, this is only a measure of the Windows compatibility solution, and there must be many other measures. If you are interested, you can take a look at it. Www.2cto.com heard about "virtualization" and thought it was a virtualization technology provided by Xen, VMware, Hyper-v, and other virtualization software. The opposite result is that the Virtualization Technologies of Windows are file virtualization and Registry virtualization, which are replaced by "VirtualStore" following Microsoft's official instructions. Virtual storage cannot be understood as Virtual Disks (VHD, Virtual Hard Disk )). But here they are not so much a technology as a way of thinking. I think the core of this idea is how to keep the Windows system clean and standard. Don't worry about file virtualization or Registry virtualization. Let's talk about the origins of this technology in detail. The word "purity" and "normalization" were both fabricated here, but do you have any effect on making comments. The so-called integrity refers to how to maintain the Windows System directory (% SystemRoot %) and key directories such as "% SystemRoot % \ System32" and "% SystemRoot % \ SysWoW64" are not changed by other applications, for example, if the application writes (the result of the "write" operation may be "Overwrite") the configuration file or dll (Dynamic Link Library) file to % SystemRoot %. Normative refers to reminding program developers not to design programs that are inverse to Windows system development concepts or methods to damage the system and reduce system availability and maintainability, do not write the above files into those key directories. Windows developers prefer that applications can also implement the features of multiple users, that is, different users on the same computer use different configuration files, so that different users do not affect the settings and data of other users, although most programs have already been designed in this way. From this sentence, we can see that this technology is actually just a way to handle compatibility programs. How is this method implemented? The answer is interesting. It is file redirection. File redirection is not complex. Just like shortcuts or shortcut commands in PowerShell, you can actually use the target file or program by accessing the alias of the linked file or target file (alias. What is the use of so many concepts? It is useless. Now the latest Windows 7 Enterprise has hidden the "compatibility file" button on the Resource Manager toolbar, which makes it even more obscure. However, if you are careful, you can still find its existence. It is in the "C: \ User \ UserName \ AppData \ Local \ VirtualStore \" folder. This file is used to save the root folder of the redirection content. Every redirected file is found in the corresponding folder under this file. The following file locations can be redirected in this folder: % SystemRoot % \ System32 \ % SystemRoot % \ SysWoW64 \ % SystemRoot % \ Program Files (X86) \ as mentioned above, this technology only works for some compatibility programs, so it also faces problems. This mechanism is only useful when you use standard permissions to run the installer. It is useless for programs installed with administrator permissions. The same Registry virtualization is easy to understand! The key to be protected is HKEY_LOCAL_MACHINE \ Software. If you are interested, go to the TechNet Library on the Microsoft official website to view the relevant technical documents. Source http://dgd2010.blog.51cto.com/1539422/1095203