Windows 7 / Getting Started

Side-by-Side Installs and Virtual Registries

Windows 98 Second Edition provided a feature called side-by-side DLLs. This feature allowed a developer to use the version of DLLs required by a particular program without overwriting system DLLs (those stored in the \Windows\System folder). This feature worked only on Windows 98SE and only if the program developer took advantage of the feature.

Windows 2000 introduced Windows File Protection, which restored system files automatically if they were overwritten by an application when you installed it or ran it. This protected Windows from crashing but didn't do anything about a program that needed a particular system file version to run.

Side-by-side installs enable users to install multiple versions of the same product on the same computer. For example, suppose Microsoft just released a new version of Office. You want to run a trial version of the new Office suite to learn about new features and test drive it, but you don't want to uninstall the current, well-oiled version. However, multiple programs that use a different version of the same DLL sometimes cause complications-"DLL Hell." When programs use the wrong DLL files, they crash and can take the whole OS down with them.

Windows XP Professional provided a way to handle DLL Hell. It was called Fusion. Fusion allowed programs to install whatever system files (DLLs and others) they needed and redirect any files that would replace system files to the program's own folder. When such a program was run, Fusion created a memory-protected virtual machine to run the program with its own DLLs. The end result was that even if two or more programs were running at the same time, using different versions of DLL or other system files that would "break" the system in past versions of Windows, both programs would run properly. No other programs could touch the area of memory granted to each program. Nor could that program or other programs gain access to the area of memory in which the basics of the OS were running.

Windows 7 and Windows Vista contain a different method from the Windows XP solution. Instead of a single Registry, they use a virtual registry that contains multiple DLLs. A virtualized application registry eliminates any conflicts between software. So, if you want to have two versions of Microsoft Office available on the same computer, for example, the virtual registry lets you run them without conflicts.

Virtual registries also have one other important aspect. Because Windows 7 can create and use virtual registries for data, Microsoft applied this concept to users who do not have Administrator privileges. By using virtual registries, nonadministrative guests can use a virtual registry and will not disrupt the main Registry. Usually, only administrators have the rights that allow one to install software that writes to the Registry. But now nonadministrators can install software and other various programs onto the system without causing any harm. Windows 7 will continue to run and display all software installed but will not experience any permanent effect from the data on the virtual registry.

Note Windows Vista introduced virtual folders, which help users get data quickly and easily. This technology has been replaced with libraries in Windows 7.

[Previous] [Contents] [Next]

In this tutorial:

  1. Windows 7 and Other software Up to Date
  2. Understanding Windows Live
  3. Updates versus upgrades
  4. Why updates are important
  5. Windows Update
  6. Windows Update: The essentials
  7. Types of Updates
  8. Completing an Update
  9. Configuring automatic Updating
  10. Windows Update Applet and Functions
  11. Manually Install Updates Using Windows Update
  12. Action Center
  13. Updates Do Not Install Properly
  14. Other Windows Update Settings
  15. Configuring Windows 7 Update to Use a Proxy Server
  16. Can't Find Hidden Update
  17. Viewing and Changing Installed Updates
  18. Can't Uninstall Current Update
  19. Upgrade Windows Anytime
  20. Understanding Windows Server Update Services
  21. Windows Update Policies
  22. Updating Drivers
  23. Using Device Manager to Update Drivers
  24. Windows Update Driver Settings
  25. Windows 7 Service Packs
  26. Basic Service Pack Information
  27. Installation of Service Packs
  28. Installing and Removing Software
  29. Installation via CD or DVD
  30. Problem Installing from Disc
  31. Installation via Downloaded Program
  32. Viewing and Changing Programs
  33. Uninstalling Software
  34. Compatibility Issues in 64-Bit Version
  35. Upgrade Issues with 64-Bit Windows 7
  36. Other Program Compatibility Issues
  37. Side-by-Side Installs and Virtual Registries
  38. Removing Updates from Windows 7
  39. Thwarting Exploits with DEP
  40. Microsoft Baseline Security Analyzer
  41. Picking Computers to Scan
  42. Vulnerability Checks
  43. Installing MBSA
  44. Running the MBSA
  45. Running the MBSACLI
  46. MBSACLI Location
  47. Running in an Isolated Environment
  48. Using Windows Server Update Services
  49. WSUS Updates
  50. WSUS Requirements
  51. Installing, Configuring, and Using WSUS
  52. Adding the Application Server and Web Server (IIS) Roles
  53. Installing the Report Viewer
  54. Installing WSUS
  55. Configuring Group Policy Settings for WSUS
  56. Creating a GPO to Configure Clients to Use WSUS
  57. Verifying That Clients Are Using GPO Settings for WSUS
  58. Verifying That Clients Are Using GPO Settings with GPResult
  59. Creating Computer Groups on WSUS
  60. Approving Updates in WSUS
  61. Viewing WSUS Reports