Side-by-side assembly (SxS, or WinSxS on Microsoft Windows) technology is a standard for executable files in Windows 98 Second Edition, Windows 2000, and later versions of Windows that attempts to alleviate problems (collectively known as "DLL Hell") that arise from the use of dynamic-link libraries (DLLs) in Microsoft Windows. Such problems include version conflicts, missing DLLs, duplicate DLLs, and incorrect or missing registration. In side-by-side, Windows stores multiple versions of a DLL in the %systemroot%\WinSxS directory, and loads them on demand. This reduces dependency problems for applications that include a side-by-side manifest.
Microsoft Visual C++ 2005 and 2008 employ SxS with all C runtime libraries. However, runtime libraries in Visual C++ 2010 no longer use this technology; instead, they include the version number of a DLL in its file name, which means that different versions of one DLL will technically be completely different DLLs now.[1] [2]
SxS is also the technological basis for registration-free COM activation. Only in-process COM servers may be activated this way.
An application that employs SxS must have a manifest. Manifests are typically a section embedded in the application's executable file but may also be an external file. When the operating system loads the application and detects the presence of a manifest, the operating system DLL loader is directed to the version of the DLL corresponding to that listed in the manifest. If there is no manifest, the DLL loader loads a default version of all DLL dependencies. If the DLL is a COM server, it must have a manifest of its own for registration-free activation to succeed.
On Windows Vista and later, can help to diagnose failures in the starting of applications due to SxS misconfiguration.
If a user wishes to override manifest-specified assemblies (for example, in the case of security patches applied to a library), a publisher configuration file can globally redirect assemblies. Digital signatures can ensure the legitimacy of such redirection.[3]
The application manifest is internally represented as XML. The URN associated with SxS manifests is "urn:schemas-microsoft-com:asm.v1".
Several other recent Microsoft technologies such as ClickOnce employ the same manifest format.
The following is an example of a manifest for an application that depends on a C runtime DLL.
A manifest like the one above is parsed into an activation context by the SxS loader. There is a stack of activation contexts for each thread or fiber. An API allows programmatic manipulation of these contexts. It may be necessary for a library (DLL) to change its activation context, for example if it requires a specific version of another library for its own consumption instead of using the activation context of its caller. This type of issue is sometimes called (activation context) pollution.[4] To prevent polluting its activation context, a DLL can have a manifest embedded as a resource, which is parsed when the DLL is loaded. This manifest must be at resource id 2 in the image file for the loader to find it.[5]
From Vista onward, the Windows operating system uses WinSxS for its core components. Operating system files in the directory are hard linked from their usual locations in the Windows directory structure. A file in a subdirectory in may be linked from multiple locations (e.g. the directory and application directories). Windows Explorer double-counts the disk space occupied by these files.[6] This can be demonstrated using the fsutil command-line program.[7] Some third-party Explorer extensions to show the link count also exist.
However, not all files from are projected this way to "live" operating system files. For example, after installing some Windows updates, old file versions replaced by the updates are still kept in although they are no longer linked in the "live" Windows directories. This allows updates to be uninstalled safely.[8]
Because of its elevated importance, from Vista onward the directory is owned by the Trusted Installer service SID. By default not even administrators can modify its contents (without taking ownership first). Uninstalling applications does not immediately free space in the directory; space for unused assemblies is garbage-collected over time by the Installer service.[9]
Although not officially documented, the algorithm for generating the directory names residing inside the directory has been made public on an MSDN Microsoft employee's blog. The algorithm was changed in the transition from XP to Vista.[10]
Windows 7 includes Windows AIK tool Deployment Image Servicing and Management (DISM) which can remove files used by superseded OS updates using the Trusted Installer worker service, without the need to reboot or take down the system;[11] post-SP1 updates add Windows Update cleanup to the Disk Cleanup tool [12] and the downloadable System Update Readiness tool (CheckSUR)[13] which can repair components store errors and replace corrupt or missing OS files with known good versions. Windows 8 integrates repair capability to the DISM tool which is now able to copy valid OS files from Windows Update or an offline WIM image, as well as reset the component store to only contain the latest versions of OS components.[14] Windows 10 runs the automatic task to clean up the component store.[15]
While the directory is extremely large and contains multiple versions of many files, there are some files elsewhere in the Windows folder (e.g.) that are hardlinks to files in the directory.[17] Thus, programs estimating the size of the Windows folder must be careful not to add the size of additional hard links to a file after one has already been counted.[18]
DIR and Explorer fail to check for hard links, and so may count the same file multiple times, adding incorrectly to the perceived disk usage. The disk usage reported by these two programs is as if each hard link is an actual file.[19]
Since Windows 8.1, the DISM tool can be used to analyze the component store and report its actual size.[20]