Setup Failed to Read Registry Key in Sql 2000

Database for Microsoft Windows

Windows Registry

Registry Editor, the user interface for the registry, in Windows ten
Developer(s)	Microsoft
Initial release	April 6, 1992; 29 years agone  (1992-04-06) with Windows 3.1
Operating system	Microsoft Windows
Platform	IA-32, x86-64 and ARM (and historically Dec Alpha, Itanium, MIPS, and PowerPC)
Included with	Microsoft Windows
Type	Hierarchical database
Website	docs.microsoft.com/en-usa/windows/desktop/SysInfo/registry

The Windows Registry is a hierarchical database that stores low-level settings for the Microsoft Windows operating system and for applications that opt to utilise the registry. The kernel, device drivers, services, Security Accounts Manager, and user interfaces can all use the registry. The registry likewise allows access to counters for profiling organisation functioning.

In other words, the registry or Windows Registry contains information, settings, options, and other values for programs and hardware installed on all versions of Microsoft Windows operating systems. For case, when a program is installed, a new subkey containing settings such as a program'due south location, its version, and how to start the program, are all added to the Windows Registry.

When introduced with Windows 3.1, the Windows Registry primarily stored configuration information for COM-based components. Windows 95 and Windows NT extended its use to rationalize and centralize the information in the profusion of INI files, which held the configurations for individual programs, and were stored at diverse locations.^{[1] [2]} It is not a requirement for Windows applications to employ the Windows Registry. For example, .Cyberspace Framework applications use XML files for configuration, while portable applications usually keep their configuration files with their executables.

Rationale [edit]

Prior to the Windows Registry, .INI files stored each program's settings equally a text file or binary file, often located in a shared location that did not provide user-specific settings in a multi-user scenario. By dissimilarity, the Windows Registry stores all application settings in ane logical repository (simply a number of discrete files) and in a standardized course. According to Microsoft, this offers several advantages over .INI files.^{[2] [iii]} Since file parsing is done much more than efficiently with a binary format, it may be read from or written to more quickly than a text INI file. Furthermore, strongly typed data can be stored in the registry, as opposed to the text information stored in .INI files. This is a do good when editing keys manually using regedit.exe, the built-in Windows Registry Editor. Because user-based registry settings are loaded from a user-specific path rather than from a read-only system location, the registry allows multiple users to share the aforementioned machine, and also allows programs to work for less privileged users. Backup and restoration is also simplified every bit the registry tin can be accessed over a network connectedness for remote management/back up, including from scripts, using the standard ready of APIs, as long every bit the Remote Registry service is running and firewall rules permit this.

Because the registry is a database, it offers improved system integrity with features such as atomic updates. If two processes attempt to update the aforementioned registry value at the same time, one procedure'southward alter volition precede the other'south and the overall consistency of the information volition exist maintained. Where changes are fabricated to .INI files, such race conditions tin result in inconsistent data that does not lucifer either attempted update. Windows Vista and later operating systems provide transactional updates to the registry by means of the Kernel Transaction Manager, extending the atomicity guarantees across multiple fundamental and/or value changes, with traditional commit–abort semantics. (Notation however that NTFS provides such support for the file organization also, so the same guarantees could, in theory, be obtained with traditional configuration files.)

Structure [edit]

Keys and values [edit]

The registry contains two basic elements: keys and values. Registry keys are container objects similar to folders. Registry values are non-container objects similar to files. Keys may incorporate values and subkeys. Keys are referenced with a syntax similar to Windows' path names, using backslashes to point levels of hierarchy. Keys must have a instance insensitive name without backslashes.

The hierarchy of registry keys can just be accessed from a known root central handle (which is anonymous but whose constructive value is a abiding numeric handle) that is mapped to the content of a registry key preloaded past the kernel from a stored "hive", or to the content of a subkey inside another root key, or mapped to a registered service or DLL that provides access to its contained subkeys and values.

E.m. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows refers to the subkey "Windows" of the subkey "Microsoft" of the subkey "Software" of the HKEY_LOCAL_MACHINE root key.

There are 7 predefined root keys, traditionally named co-ordinate to their constant handles defined in the Win32 API, or by synonymous abbreviations (depending on applications):^[4]

• HKEY_LOCAL_MACHINE or HKLM
• HKEY_CURRENT_CONFIG or HKCC
• HKEY_CLASSES_ROOT or HKCR
• HKEY_CURRENT_USER or HKCU
• HKEY_USERS or HKU
• HKEY_PERFORMANCE_DATA (just in Windows NT, but invisible in the Windows Registry Editor)^[5]
• HKEY_DYN_DATA (only in Windows 9x, and visible in the Windows Registry Editor)

Like other files and services in Windows, all registry keys may be restricted by access control lists (ACLs), depending on user privileges, or on security tokens acquired by applications, or on system security policies enforced by the system (these restrictions may exist predefined by the organization itself, and configured past local system administrators or by domain administrators). Unlike users, programs, services or remote systems may but see some parts of the hierarchy or distinct hierarchies from the same root keys.

Registry values are name/data pairs stored within keys. Registry values are referenced separately from registry keys. Each registry value stored in a registry fundamental has a unique name whose letter instance is not significant. The Windows API functions that query and manipulate registry values take value names separately from the cardinal path and/or handle that identifies the parent key. Registry values may contain backslashes in their names, but doing and then makes them difficult to distinguish from their key paths when using some legacy Windows Registry API functions (whose usage is deprecated in Win32).

The terminology is somewhat misleading, every bit each registry key is similar to an associative assortment, where standard terminology would refer to the name part of each registry value as a "central". The terms are a holdout from the sixteen-bit registry in Windows 3, in which registry keys could not incorporate arbitrary name/data pairs, but rather independent only one unnamed value (which had to exist a string). In this sense, the Windows iii registry was like a single associative array, in which the keys (in the sense of both 'registry key' and 'associative array key') formed a hierarchy, and the registry values were all strings. When the 32-bit registry was created, so was the boosted capability of creating multiple named values per key, and the meanings of the names were somewhat distorted.^[6] For compatibility with the previous beliefs, each registry central may have a "default" value, whose name is the empty string.

Each value tin shop arbitrary information with variable length and encoding, but which is associated with a symbolic type (defined as a numeric constant) defining how to parse this data. The standard types are:^[7]

List of standard registry value types

Type ID	Symbolic type name	Meaning and encoding of the data stored in the registry value
0	REG_NONE	No type (the stored value, if whatever)
1	REG_SZ	A string value, normally stored and exposed in UTF-16LE (when using the Unicode version of Win32 API functions), usually terminated by a NUL character
2	REG_EXPAND_SZ	An "expandable" string value that can incorporate environment variables, usually stored and exposed in UTF-16LE, commonly terminated by a NUL grapheme
iii	REG_BINARY	Binary information (any arbitrary data)
4	REG_DWORD / REG_DWORD_LITTLE_ENDIAN	A DWORD value, a 32-bit unsigned integer (numbers between 0 and four,294,967,295 [ii32 – one]) (little-endian)
5	REG_DWORD_BIG_ENDIAN	A DWORD value, a 32-bit unsigned integer (numbers between 0 and iv,294,967,295 [232 – i]) (big-endian)
half dozen	REG_LINK	A symbolic link (UNICODE) to another registry cardinal, specifying a root key and the path to the target cardinal
seven	REG_MULTI_SZ	A multi-string value, which is an ordered list of not-empty strings, normally stored and exposed in Unicode, each 1 terminated by a null grapheme, the list being unremarkably terminated by a 2nd nil grapheme.[8]
8	REG_RESOURCE_LIST	A resources list (used past the Plug-due north-Play hardware enumeration and configuration)
nine	REG_FULL_RESOURCE_DESCRIPTOR	A resources descriptor (used by the Plug-northward-Play hardware enumeration and configuration)
10	REG_RESOURCE_REQUIREMENTS_LIST	A resource requirements list (used past the Plug-n-Play hardware enumeration and configuration)
11	REG_QWORD / REG_QWORD_LITTLE_ENDIAN	A QWORD value, a 64-fleck integer (either large- or piffling-endian, or unspecified) (introduced in Windows 2000)[ix]

Root keys [edit]

The keys at the root level of the hierarchical database are generally named by their Windows API definitions, which all begin "HKEY".^[2] They are ofttimes abbreviated to a iii- or 4-alphabetic character short name starting with "HK" (due east.k. HKCU and HKLM). Technically, they are predefined handles (with known abiding values) to specific keys that are either maintained in memory, or stored in hive files stored in the local filesystem and loaded by the arrangement kernel at boot time and then shared (with various access rights) between all processes running on the local system, or loaded and mapped in all processes started in a user session when the user logs on the arrangement.

The HKEY_LOCAL_MACHINE (local automobile-specific configuration information) and HKEY_CURRENT_USER (user-specific configuration data) nodes take a similar construction to each other; user applications typically look upward their settings by first checking for them in "HKEY_CURRENT_USER\Software\Vendor'due south name\Application's proper name\Version\Setting name", and if the setting is not found, await instead in the same location nether the HKEY_LOCAL_MACHINE fundamental^{[ commendation needed ]}. All the same, the antipodal may employ for ambassador-enforced policy settings where HKLM may accept precedence over HKCU. The Windows Logo Programme has specific requirements for where different types of user information may be stored, and that the concept of least privilege be followed so that administrator-level access is non required to use an application.^{[a] [x]}

HKEY_LOCAL_MACHINE (HKLM) [edit]

Abbreviated HKLM, HKEY_LOCAL_MACHINE stores settings that are specific to the local computer.^[eleven]

The key located by HKLM is really not stored on disk, simply maintained in memory by the system kernel in order to map all the other subkeys. Applications cannot create any additional subkeys. On Windows NT, this key contains four subkeys, "SAM", "SECURITY", "SYSTEM", and "SOFTWARE", that are loaded at boot time within their corresponding files located in the %SystemRoot%\System32\config folder. A fifth subkey, "HARDWARE", is volatile and is created dynamically, and as such is non stored in a file (information technology exposes a view of all the currently detected Plug-and-Play devices). On Windows Vista and higher up, a sixth and seventh subkey, "COMPONENTS" and "BCD", are mapped in memory by the kernel on-demand and loaded from %SystemRoot%\system32\config\COMPONENTS or from boot configuration information, \boot\BCD on the system partition.

• The "HKLM\SAM" key normally appears as empty for most users (unless they are granted admission by administrators of the local system or administrators of domains managing the local organization). It is used to reference all "Security Accounts Manager" (SAM) databases for all domains into which the local organisation has been administratively authorized or configured (including the local domain of the running arrangement, whose SAM database is stored in a subkey also named "SAM": other subkeys volition be created equally needed, i for each supplementary domain). Each SAM database contains all builtin accounts (by and large group aliases) and configured accounts (users, groups and their aliases, including guest accounts and administrator accounts) created and configured on the respective domain, for each business relationship in that domain, information technology notably contains the user name which can be used to log on that domain, the internal unique user identifier in the domain, a cryptographic hash of each user's password for each enabled authentication protocol, the location of storage of their user registry hive, various condition flags (for example if the account can be enumerated and exist visible in the logon prompt screen), and the list of domains (including the local domain) into which the account was configured.
• The "HKLM\SECURITY" cardinal usually appears empty for most users (unless they are granted access by users with administrative privileges) and is linked to the Security database of the domain into which the current user is logged on (if the user is logged on the local arrangement domain, this fundamental volition be linked to the registry hive stored by the local auto and managed past local system administrators or by the builtin "System" business relationship and Windows installers). The kernel will access it to read and enforce the security policy applicable to the electric current user and all applications or operations executed past this user. It also contains a "SAM" subkey which is dynamically linked to the SAM database of the domain onto which the electric current user is logged on.
• The "HKLM\Arrangement" primal is normally merely writable by users with authoritative privileges on the local organisation. It contains information about the Windows system setup, data for the secure random number generator (RNG), the list of currently mounted devices containing a filesystem, several numbered "HKLM\Arrangement\Command Sets" containing culling configurations for organisation hardware drivers and services running on the local system (including the currently used 1 and a backup), a "HKLM\SYSTEM\Select" subkey containing the condition of these Control Sets, and a "HKLM\Organisation\CurrentControlSet" which is dynamically linked at boot time to the Control Fix which is currently used on the local organization. Each configured Control Set contains:
  • an "Enum" subkey enumerating all known Plug-and-Play devices and associating them with installed organisation drivers (and storing the device-specific configurations of these drivers),
  • a "Services" subkey listing all installed arrangement drivers (with not device-specific configuration, and the enumeration of devices for which they are instantiated) and all programs running as services (how and when they tin can be automatically started),
  • a "Control" subkey organizing the diverse hardware drivers and programs running every bit services and all other system-wide configuration,
  • a "Hardware Profiles" subkey enumerating the various profiles that have been tuned (each one with "System" or "Software" settings used to change the default profile, either in organisation drivers and services or in the applications) as well every bit the "Hardware Profiles\Current" subkey which is dynamically linked to 1 of these profiles.
• The "HKLM\SOFTWARE" subkey contains software and Windows settings (in the default hardware contour). It is mostly modified by awarding and system installers. It is organized by software vendor (with a subkey for each), but also contains a "Windows" subkey for some settings of the Windows user interface, a "Classes" subkey containing all registered associations from file extensions, MIME types, Object Classes IDs and interfaces IDs (for OLE, COM/DCOM and ActiveX), to the installed applications or DLLs that may be treatment these types on the local machine (still these associations are configurable for each user, see below), and a "Policies" subkey (also organized by vendor) for enforcing full general usage policies on applications and organisation services (including the key certificates store used for authenticating, authorizing or disallowing remote systems or services running outside the local network domain).
• The "HKLM\SOFTWARE\Wow6432Node" primal is used by 32-scrap applications on a 64-bit Windows OS, and is equivalent to simply separate from "HKLM\SOFTWARE". The fundamental path is transparently presented to 32-bit applications by WoW64 equally HKLM\SOFTWARE^[12] (in a similar way that 32-bit applications run into %SystemRoot%\Syswow64 as %SystemRoot%\System32)

HKEY_CLASSES_ROOT (HKCR) [edit]

Abbreviated HKCR, HKEY_CLASSES_ROOT contains information well-nigh registered applications, such as file associations and OLE Object Form IDs, tying them to the applications used to handle these items. On Windows 2000 and above, HKCR is a compilation of user-based HKCU\Software\Classes and motorcar-based HKLM\Software\Classes. If a given value exists in both of the subkeys above, the ane in HKCU\Software\Classes takes precedence.^[xiii] The blueprint allows for either machine- or user-specific registration of COM objects.

HKEY_USERS (HKU) [edit]

Abbreviated HKU, HKEY_USERS contains subkeys corresponding to the HKEY_CURRENT_USER keys for each user profile actively loaded on the machine, though user hives are usually merely loaded for currently logged-in users.

HKEY_CURRENT_USER (HKCU) [edit]

Abbreviated HKCU, HKEY_CURRENT_USER stores settings that are specific to the currently logged-in user.^[fourteen] The HKEY_CURRENT_USER central is a link to the subkey of HKEY_USERS that corresponds to the user; the same information is accessible in both locations. The specific subkey referenced is "(HKU)\(SID)\..." where (SID) corresponds to the Windows SID; if the "(HKCU)" primal has the post-obit suffix "(HKCU)\Software\Classes\..." then it corresponds to "(HKU)\(SID)_CLASSES\..." i.due east. the suffix has the string "_CLASSES" is appended to the (SID).

On Windows NT systems, each user's settings are stored in their own files called NTUSER.DAT and USRCLASS.DAT within their own Documents and Settings subfolder (or their own Users sub binder in Windows Vista and in a higher place). Settings in this hive follow users with a roaming contour from machine to machine.

HKEY_PERFORMANCE_DATA [edit]

This key provides runtime information into performance information provided by either the NT kernel itself, or running system drivers, programs and services that provide performance information. This key is not stored in any hive and not displayed in the Registry Editor, only it is visible through the registry functions in the Windows API, or in a simplified view via the Performance tab of the Chore Manager (only for a few operation data on the local system) or via more advanced control panels (such every bit the Performances Monitor or the Performances Analyzer which allows collecting and logging these data, including from remote systems).

HKEY_DYN_DATA [edit]

This key is used only on Windows 95, Windows 98 and Windows ME.^[xv] It contains information nearly hardware devices, including Plug and Play and network functioning statistics. The information in this hive is also not stored on the hard drive. The Plug and Play information is gathered and configured at startup and is stored in memory.^[xvi]

Hives [edit]

Even though the registry presents itself as an integrated hierarchical database, branches of the registry are actually stored in a number of disk files called hives.^[17] (The give-and-take hive constitutes an in-joke.)^[18]

Some hives are volatile and are not stored on disk at all. An case of this is the hive of the branch starting at HKLM\HARDWARE. This hive records information near system hardware and is created each time the system boots and performs hardware detection.

Individual settings for users on a system are stored in a hive (disk file) per user. During user login, the system loads the user hive under the HKEY_USERS central and sets the HKCU (HKEY_CURRENT_USER) symbolic reference to point to the electric current user. This allows applications to shop/call back settings for the current user implicitly nether the HKCU key.

Not all hives are loaded at any one time. At boot time, merely a minimal set of hives are loaded, and after that, hives are loaded every bit the operating system initializes and equally users log in or whenever a hive is explicitly loaded past an application.

File locations [edit]

The registry is physically stored in several files, which are mostly obfuscated from the user-mode APIs used to manipulate the data inside the registry. Depending upon the version of Windows, there will exist different files and different locations for these files, but they are all on the local machine. The location for organization registry files in Windows NT is %SystemRoot%\System32\Config; the user-specific HKEY_CURRENT_USER user registry hive is stored in Ntuser.dat inside the user profile. In that location is one of these per user; if a user has a roaming profile, so this file volition exist copied to and from a server at logout and login respectively. A second user-specific registry file named UsrClass.dat contains COM registry entries and does not roam by default.

Windows NT [edit]

Windows NT systems store the registry in a binary file format which can exist exported, loaded and unloaded by the Registry Editor in these operating systems. The following system registry files are stored in %SystemRoot%\System32\Config\:

• Sam – HKEY_LOCAL_MACHINE\SAM
• Security – HKEY_LOCAL_MACHINE\SECURITY
• Software – HKEY_LOCAL_MACHINE\SOFTWARE
• Organization – HKEY_LOCAL_MACHINE\Organisation
• Default – HKEY_USERS\.DEFAULT
• Userdiff – Not associated with a hive. Used merely when upgrading operating systems.^[19]

The following file is stored in each user's profile binder:

• %USERPROFILE%\Ntuser.dat – HKEY_USERS\<User SID> (linked to by HKEY_CURRENT_USER)

For Windows 2000, Server 2003 and Windows XP, the post-obit additional user-specific file is used for file associations and COM information:

• %USERPROFILE%\Local Settings\Application Data\Microsoft\Windows\Usrclass.dat (path is localized) – HKEY_USERS\<User SID>_Classes (HKEY_CURRENT_USER\Software\Classes)

For Windows Vista and later, the path was changed to:

• %USERPROFILE%\AppData\Local\Microsoft\Windows\Usrclass.dat (path is not localized) alias %LocalAppData%\Microsoft\Windows\Usrclass.dat – HKEY_USERS\<User SID>_Classes (HKEY_CURRENT_USER\Software\Classes)

Windows 2000 keeps an alternate copy of the registry hives (.ALT) and attempts to switch to it when corruption is detected.^[20] Windows XP and Windows Server 2003 exercise not maintain a System.alt hive because NTLDR on those versions of Windows can process the System.log file to bring upwardly to date a Arrangement hive that has get inconsistent during a shutdown or crash. In addition, the %SystemRoot%\Repair binder contains a copy of the organization'south registry hives that were created afterwards installation and the beginning successful startup of Windows.

Each registry data file has an associated file with a ".log" extension that acts as a transaction log that is used to ensure that any interrupted updates can be completed upon adjacent startup.^[21] Internally, Registry files are dissever into iv kB "bins" that incorporate collections of "cells".^[21]

Windows 9x [edit]

The registry files are stored in the %WINDIR% directory nether the names USER.DAT and SYSTEM.DAT with the addition of CLASSES.DAT in Windows ME. Besides, each user profile (if profiles are enabled) has its own USER.DAT file which is located in the user'south contour directory in %WINDIR%\Profiles\<Username>\.

Windows 3.11 [edit]

The merely registry file is chosen REG.DAT and it is stored in the %WINDIR% directory.

Windows 10 Mobile [edit]

Annotation: To access the registry files, the Phone needs to be set in a special style using either:

• WpInternals ( Put the mobile device into flash style. )
• InterOp Tools ( mount the MainOS Partition with MTP. )

If any of above Methods worked - The Device Registry Files can be found in the following location:

          {Phone}\EFIESP\Windows\System32\config        

Note: InterOp Tools also includes a registry editor.

Editing [edit]

Registry editors [edit]

The registry contains important configuration information for the operating organisation, for installed applications likewise as private settings for each user and awarding. A careless change to the operating system configuration in the registry could cause irreversible damage, so it is usually only installer programs which perform changes to the registry database during installation/configuration and removal. If a user wants to edit the registry manually, Microsoft recommends that a backup of the registry be performed before the change.^[22] When a programme is removed from command panel, it may non be completely removed and, in case of errors or glitches caused by references to missing programs, the user might accept to manually check within directories such as programme files. After this, the user might need to manually remove any reference to the uninstalled program in the registry. This is usually done by using RegEdit.exe.^[23] Editing the registry is sometimes necessary when working effectually Windows-specific issues eastward.chiliad. problems when logging onto a domain tin be resolved past editing the registry.^[24]

Windows Registry tin can be edited manually using programs such equally RegEdit.exe, although these tools do not expose some of the registry'due south metadata such as the concluding modified appointment.

The registry editor for the 3.1/95 series of operating systems is RegEdit.exe and for Windows NT it is RegEdt32.exe; the functionalities are merged in Windows XP. Optional and/or tertiary-political party tools similar to RegEdit.exe are available for many Windows CE versions.

Registry Editor allows users to perform the following functions:

• Creating, manipulating, renaming^[25] and deleting registry keys, subkeys, values and value data
• Importing and exporting .REG files, exporting data in the binary hive format
• Loading, manipulating and unloading registry hive format files (Windows NT systems only)
• Setting permissions based on ACLs (Windows NT systems only)
• Bookmarking user-selected registry keys every bit Favorites
• Finding item strings in key names, value names and value data
• Remotely editing the registry on some other networked computer

.REG files [edit]

.REG files (also known equally Registration entries) are text-based human-readable files for exporting and importing portions of the registry using a INI-based syntax. On Windows 2000 and afterward, they contain the cord Windows Registry Editor Version five.00 at the get-go and are Unicode-based. On Windows 9x and NT 4.0 systems, they contain the string REGEDIT4 and are ANSI-based.^[26] Windows 9x format .REG files are uniform with Windows 2000 and afterwards. The Registry Editor on Windows on these systems also supports exporting .REG files in Windows 9x/NT format. Data is stored in .REG files using the post-obit syntax:^[26]

                        [<Hive proper noun>\<Key name>\<Subkey name>]            "Value name"            =            <Value type>:<Value data>          

The Default Value of a key tin be edited by using "@" instead of "Value Name":

                        [<Hive name>\<Key name>\<Subkey proper noun>]            @            =            <Value blazon>:<Value data>          

String values practice not require a <Value blazon> (see instance), but backslashes ('\') need to be written as a double-backslash ('\\'), and quotes ('"') as backslash-quote ('\"').

For example, to add together the values "Value A", "Value B", "Value C", "Value D", "Value Due east", "Value F", "Value One thousand", "Value H", "Value I", "Value J", "Value K", "Value L", and "Value Yard" to the HKLM\SOFTWARE\Foobar key:

            Windows Registry Editor Version v.00            [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            "Value A"            =            "<Cord value data with escape characters>"            "Value B"            =            hex:<Binary data (as comma-delimited list of hexadecimal values)>            "Value C"            =            dword:<DWORD value integer>            "Value D"            =            hex(0):<REG_NONE (as comma-delimited list of hexadecimal values)>            "Value Due east"            =            hex(1):<REG_SZ (every bit comma-delimited listing of hexadecimal values representing a UTF-16LE NUL-terminated string)>            "Value F"            =            hex(two):<Expandable string value data (every bit comma-delimited list of hexadecimal values representing a UTF-16LE NUL-terminated cord)>            "Value One thousand"            =            hex(3):<Binary data (as comma-delimited list of hexadecimal values)> ; equal to "Value B"            "Value H"            =            hex(4):<DWORD value (as comma-delimited list of iv hexadecimal values, in little endian byte club)>            "Value I"            =            hex(5):<DWORD value (as comma-delimited list of iv hexadecimal values, in large endian byte order)>            "Value J"            =            hex(7):<Multi-cord value information (as comma-delimited list of hexadecimal values representing UTF-16LE NUL-terminated strings)>            "Value Yard"            =            hex(viii):<REG_RESOURCE_LIST (as comma-delimited list of hexadecimal values)>            "Value L"            =            hex(a):<REG_RESOURCE_REQUIREMENTS_LIST (every bit comma-delimited listing of hexadecimal values)>            "Value M"            =            hex(b):<QWORD value (equally comma-delimited list of eight hexadecimal values, in fiddling endian byte club)>          

Data from .REG files can be added/merged with the registry by double-clicking these files or using the /south switch in the command line. REG files tin also be used to remove registry data.

To remove a key (and all subkeys, values and data), the key name must be preceded by a minus sign ("-").^[26]

For instance, to remove the HKLM\SOFTWARE\Foobar key (and all subkeys, values and data),

                        [            -            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]          

To remove a value (and its data), the values to be removed must have a minus sign ("-") afterward the equal sign ("=").^[26]

For case, to remove but the "Value A" and "Value B" values (and their data) from the HKLM\SOFTWARE\Foobar primal:

                        [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            "Value A"            =-            "Value B"            =-          

To remove only the Default value of the key HKLM\SOFTWARE\Foobar (and its data):

                        [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            @            =-          

Lines offset with a semicolon are considered comments:

                        ; This is a comment. This tin be placed in whatsoever part of a .reg file            [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            "Value"            =            "Example string"          

Group policies [edit]

Windows grouping policies can change registry keys for a number of machines or private users based on policies. When a policy kickoff takes result for a machine or for an private user of a car, the registry settings specified as function of the policy are applied to the machine or user settings.

Windows will likewise look for updated policies and apply them periodically, typically every 90 minutes.^[27]

Through its telescopic a policy defines which machines and/or users the policy is to be applied to. Whether a auto or user is within the scope of a policy or not is defined past a ready of rules which tin can filter on the location of the machine or user account in organizational directory, specific users or automobile accounts or security groups. More advanced rules tin be set up using Windows Direction Instrumentation expressions. Such rules can filter on properties such as computer vendor proper name, CPU architecture, installed software, or networks connected to.

For instance, the administrator can create a policy with one set of registry settings for machines in the accounting section and policy with another (lock-down) set up of registry settings for kiosk terminals in the visitors area. When a automobile is moved from ane scope to another (e.1000. changing its name or moving information technology to another organizational unit), the correct policy is automatically practical. When a policy is changed it is automatically re-practical to all machines currently in its telescopic.

The policy is edited through a number of administrative templates which provides a user interface for picking and changing settings. The ready of administrative templates is extensible and software packages which support such remote administration tin annals their own templates.

Command line editing [edit]

reg

Developer(southward)	Microsoft
Operating system	Microsoft Windows
Type	Command
License	Proprietary commercial software
Website	docs.microsoft.com/en-usa/windows-server/administration/windows-commands/reg

regini

Developer(s)	Microsoft
Operating system	Microsoft Windows
Blazon	Command
License	Proprietary commercial software
Website	docs.microsoft.com/en-united states of america/windows-server/administration/windows-commands/regini

The registry tin can be manipulated in a number of ways from the control line. The Reg.exe and RegIni.exe utility tools are included in Windows XP and later versions of Windows. Culling locations for legacy versions of Windows include the Resources Kit CDs or the original Installation CD of Windows.

Also, a .REG file tin be imported from the command line with the following command:

RegEdit.exe /southward          file        

The /s means the file will be silent merged to the registry. If the /s parameter is omitted the user will be asked to confirm the functioning. In Windows 98, Windows 95 and at least some configurations of Windows XP the /south switch likewise causes RegEdit.exe to ignore the setting in the registry that allows administrators to disable it. When using the /s switch RegEdit.exe does not render an appropriate return code if the operation fails, unlike Reg.exe which does.

RegEdit.exe /e          file        

exports the whole registry in V5 format to a UNICODE .REG file, while any of

RegEdit.exe /east          file          HKEY_CLASSES_ROOT[\<key>] RegEdit.exe /e          file          HKEY_CURRENT_CONFIG[\<fundamental>] RegEdit.exe /e          file          HKEY_CURRENT_USER[\<key>] RegEdit.exe /e          file          HKEY_LOCAL_MACHINE[\<key>] RegEdit.exe /e          file          HKEY_USERS[\<primal>]        

export the specified (sub)key (which has to be enclosed in quotes if it contains spaces) only.

RegEdit.exe /a          file        

exports the whole registry in V4 format to an ANSI .REG file.

RegEdit.exe /a          file          <fundamental>        

exports the specified (sub)cardinal (which has to exist enclosed in quotes if it contains spaces) only.

It is also possible to use Reg.exe. Here is a sample to display the value of the registry value Version:

                        Reg.exe            QUERY            HKLM\Software\Microsoft\ResKit            /v            Version          

Other command line options include a VBScript or JScript together with CScript, WMI or WMIC.exe and Windows PowerShell.

Registry permissions can be manipulated through the command line using RegIni.exe and the SubInACL.exe tool. For example, the permissions on the HKEY_LOCAL_MACHINE\SOFTWARE key can be displayed using:

                        SubInACL.exe            /keyreg            HKEY_LOCAL_MACHINE\SOFTWARE            /display          

PowerShell commands and scripts [edit]

Using PowerShell to navigate the registry

Windows PowerShell comes with a registry provider which presents the registry as a location type similar to the file arrangement. The same commands used to manipulate files and directories in the file organisation can be used to manipulate keys and values of the registry.^[28]

Likewise like the file system, PowerShell uses the concept of a current location which defines the context on which commands past default operate. The Go-ChildItem (likewise available through the aliases ls, dir or gci) retrieves the child keys of the electric current location. By using the Set-Location (or the alias cd) command the user can change the electric current location to another key of the registry.^[28] Commands which rename items, remove items, create new items or set content of items or properties tin can exist used to rename keys, remove keys or entire sub-trees or change values.

Through PowerShell scripts files, an administrator tin can prepare scripts which, when executed, make changes to the registry. Such scripts can be distributed to administrators who can execute them on individual machines. The PowerShell Registry provider supports transactions, i.e. multiple changes to the registry tin exist bundled into a single diminutive transaction. An atomic transaction ensures that either all of the changes are committed to the database, or if the script fails, none of the changes are committed to the database.^{[28] [29]}

Programs or scripts [edit]

The registry tin be edited through the APIs of the Avant-garde Windows 32 Base API Library (advapi32.dll).^[30]

Listing of registry API functions

RegCloseKey	RegOpenKey	RegConnectRegistry	RegOpenKeyEx
RegCreateKey	RegQueryInfoKey	RegCreateKeyEx	RegQueryMultipleValues
RegDeleteKey	RegQueryValue	RegDeleteValue	RegQueryValueEx
RegEnumKey	RegReplaceKey	RegEnumKeyEx	RegRestoreKey
RegEnumValue	RegSaveKey	RegFlushKey	RegSetKeySecurity
RegGetKeySecurity	RegSetValue	RegLoadKey	RegSetValueEx
	RegNotifyChangeKeyValue	RegUnLoadKey

Many programming languages offer built-in runtime library functions or classes that wrap the underlying Windows APIs and thereby enable programs to store settings in the registry (e.one thousand. Microsoft.Win32.Registry in VB.NET and C#, or TRegistry in Delphi and Free Pascal). COM-enabled applications like Visual Basic 6 tin can use the WSH WScript.Shell object. Another way is to use the Windows Resources Kit Tool, Reg.exe by executing it from code,^[31] although this is considered poor programming exercise.

Similarly, scripting languages such as Perl (with Win32::TieRegistry), Python (with winreg), TCL (which comes bundled with the registry package),^[32] Windows Powershell and Windows Scripting Host also enable registry editing from scripts.

Offline editing [edit]

The offreg.dll^[33] bachelor from the Windows Driver Kit offers a set of APIs for the creation and manipulation of currently non loaded registry hives like to those provided by advapi32.dll.

It is also possible to edit the registry (hives) of an offline system from Windows PE or Linux (in the latter case using open source tools).

COM self-registration [edit]

Prior to the introduction of registration-complimentary COM, developers were encouraged to add initialization code to in-process and out-of-process binaries to perform the registry configuration required for that object to piece of work. For in-process binaries such equally .DLL and .OCX files, the modules typically exported a function chosen DllInstall()^[34] that could be called by installation programs or invoked manually with utilities similar Regsvr32.exe;^[35] out-of-procedure binaries typically support the commandline arguments /Regserver and /Unregserver that created or deleted the required registry settings.^[36] COM applications that intermission because of DLL Hell bug can commonly be repaired with RegSvr32.exe or the /RegServer switch without having to re-invoke installation programs.^[37]

Advanced functionality [edit]

Windows exposes APIs that allows user-way applications to register to receive a notification event if a particular registry key is changed.^[38] APIs are too bachelor to allow kernel-style applications to filter and modify registry calls made past other applications.^[39]

Windows likewise supports remote access to the registry of another estimator via the RegConnectRegistry part^[40] if the Remote Registry service is running, correctly configured and its network traffic is not firewalled.^[41]

Security [edit]

Each key in the registry of Windows NT versions tin accept an associated security descriptor. The security descriptor contains an access control list (ACL) that describes which user groups or individual users are granted or denied access permissions. The set of registry permissions include x rights/permissions which can be explicitly allowed or denied to a user or a group of users.

Registry permissions

Permission	Description
Query Value	The right to read the registry key value.
Set Value	The right to write a new value
Create Subkey	The correct to create subkeys.
Enumerate Subkeys	Allow the enumeration of subkeys.
Notify	The right to request alter notifications for registry keys or subkeys.
Create Link	Reserved by the operating organization.
Delete	The right to delete a fundamental.
Write DACL	The right to modify permissions of the container'southward DACL.
Write Possessor	The right to modify the container'due south owner.
Read Command	The correct to read the DACL.

Equally with other securable objects in the operating system, private access control entries (ACE) on the security descriptor can exist explicit or inherited from a parent object.^[42]

Windows Resource Protection is a feature of Windows Vista and later versions of Windows that uses security to deny Administrators and the organisation WRITE access to some sensitive keys to protect the integrity of the system from malware and adventitious modification.^[43]

Special ACEs on the security descriptor can also implement mandatory integrity control for the registry central and subkeys. A procedure running at a lower integrity level cannot write, change or delete a registry key/value, even if the account of the procedure has otherwise been granted access through the ACL. For instance, Internet Explorer running in Protected Mode can read medium and low integrity registry keys/values of the currently logged on user, but it can simply alter low integrity keys.^[44]

Outside security, registry keys cannot be deleted or edited due to other causes. Registry keys containing NUL characters cannot exist deleted with standard registry editors and require a special utility for deletion, such every bit RegDelNull.^{[45] [46]}

Backups and recovery [edit]

Dissimilar editions of Windows take supported a number of different methods to support and restore the registry over the years, some of which are at present deprecated:

• System Restore can dorsum up the registry and restore it equally long as Windows is bootable, or from the Windows Recovery Surroundings (starting with Windows Vista).
• NTBackup tin back up the registry as part of the System State and restore information technology. Automated System Recovery in Windows XP tin also restore the registry.
• On Windows NT, the Terminal Known Good Configuration option in startup carte relinks the HKLM\Organization\CurrentControlSet key, which stores hardware and device driver data.
• Windows 98 and Windows ME include command line (Scanreg.exe) and GUI (Scanregw.exe) registry checker tools to bank check and fix the integrity of the registry, create upward to five automatic regular backups by default and restore them manually or whenever corruption is detected.^[47] The registry checker tool backs up the registry, by default, to %Windir%\Sysbckup Scanreg.exe can besides run from MS-DOS.^[48]
• The Windows 95 CD-ROM included an Emergency Recovery Utility (ERU.exe) and a Configuration Backup Tool (Cfgback.exe) to support and restore the registry. Additionally Windows 95 backs up the registry to the files system.da0 and user.da0 on every successful boot.
• Windows NT 4.0 included RDISK.EXE, a utility to back up and restore the entire registry.^[49]
• Windows 2000 Resource Kit contained an unsupported pair of utilities called Regback.exe and RegRest.exe for backup and recovery of the registry.^[l]
• Periodic automated backups of the registry are now disabled by default on Windows x May 2019 Update (version 1903). Microsoft recommends Arrangement Restore be used instead.^[51]

Policy [edit]

Grouping policy [edit]

Windows 2000 and later versions of Windows utilise Group Policy to enforce registry settings through a registry-specific client extension in the Group Policy processing engine.^[52] Policy may be applied locally to a single reckoner using gpedit.msc, or to multiple users and/or computers in a domain using gpmc.msc.

Legacy systems [edit]

With Windows 95, Windows 98, Windows ME and Windows NT four.0, administrators tin can use a special file to exist merged into the registry, called a policy file (POLICY.Politician). The policy file allows administrators to prevent non-administrator users from irresolute registry settings like, for instance, the security level of Net Explorer and the desktop groundwork wallpaper. The policy file is primarily used in a business concern with a large number of computers where the business needs to be protected from rogue or careless users.

The default extension for the policy file is .Politico. The policy file filters the settings it enforces by user and by group (a "grouping" is a divers set of users). To practice that the policy file merges into the registry, preventing users from circumventing information technology by simply irresolute back the settings. The policy file is unremarkably distributed through a LAN, simply can exist placed on the local computer.

The policy file is created past a free tool by Microsoft that goes past the filename poledit.exe for Windows 95/Windows 98 and with a computer direction module for Windows NT. The editor requires administrative permissions to exist run on systems that uses permissions. The editor can also directly change the current registry settings of the local computer and if the remote registry service is installed and started on another computer it tin can also change the registry on that computer. The policy editor loads the settings it tin alter from .ADM files, of which one is included, that contains the settings the Windows beat provides. The .ADM file is plain text and supports easy localisation by allowing all the strings to exist stored in i place.

Virtualization [edit]

INI file virtualization [edit]

Windows NT kernels back up redirection of INI file-related APIs into a virtual file in a registry location such as HKEY_CURRENT_USER using a characteristic called "InifileMapping".^[53] This functionality was introduced to permit legacy applications written for 16-chip versions of Windows to exist able to run nether Windows NT platforms on which the Arrangement folder is no longer considered an appropriate location for user-specific data or configuration. Non-compliant 32-bit applications can also be redirected in this manner, even though the feature was originally intended for 16-bit applications.

Registry virtualization [edit]

Windows Vista introduced limited registry virtualization, whereby poorly written applications that practice non respect the principle of to the lowest degree privilege and instead try to write user data to a read-only system location (such every bit the HKEY_LOCAL_MACHINE hive), are silently redirected to a more appropriate location, without irresolute the awarding itself.

Similarly, awarding virtualization redirects all of an application's invalid registry operations to a location such every bit a file. Used together with file virtualization, this allows applications to run on a car without being installed on it.

Low integrity processes may too employ registry virtualization. For instance, Cyberspace Explorer 7 or viii running in "Protected Fashion" on Windows Vista and in a higher place will automatically redirect registry writes by ActiveX controls to a sandboxed location in order to frustrate some classes of security exploits.

The Awarding Compatibility Toolkit^[54] provides shims that tin can transparently redirect HKEY_LOCAL_MACHINE or HKEY_CLASSES_ROOT Registry operations to HKEY_CURRENT_USER to address "LUA" bugs that cause applications non to work for users with insufficient rights.

Disadvantages [edit]

Critics labeled the registry in Windows 95 a single signal of failure, because re-installation of the operating system was required if the registry became corrupt.^{[ commendation needed ]} Nevertheless, Windows NT uses transaction logs to protect against corruption during updates. Current versions of Windows use 2 levels of log files to ensure integrity even in the case of power failure or like catastrophic events during database updates.^[55] Even in the instance of a non-recoverable error, Windows can repair or re-initialize damaged registry entries during organisation boot.^[55]

Equivalents and alternatives [edit]

In Windows, use of the registry for storing program data is a matter of developer'south discretion. Microsoft provides programming interfaces for storing data in XML files (via MSXML) or database files (via SQL Server Compact) which developers can use instead. Developers are also gratis to employ non-Microsoft alternatives or develop their ain proprietary data stores.

In contrast to Windows Registry'south binary-based database model, some other operating systems use dissever plain-text files for daemon and application configuration, but grouping these configurations together for ease of direction.

• In Unix-like operating systems (including Linux) that follow the Filesystem Hierarchy Standard, organization-wide configuration files (data similar to what would announced in HKEY_LOCAL_MACHINE on Windows) are traditionally stored in files in /etc/ and its subdirectories, or sometimes in /usr/local/etc. Per-user information (information that would exist roughly equivalent to that in HKEY_CURRENT_USER) is stored in hidden directories and files (that starting time with a menses/total stop) within the user'southward domicile directory. However XDG-compliant applications should refer to the environs variables defined in the Base Directory specification.^[56]
• In macOS, system-wide configuration files are typically stored in the /Library/ folder, whereas per-user configuration files are stored in the corresponding ~/Library/ binder in the user'south home directory, and configuration files set by the system are in /System/Library/. Within these respective directories, an application typically stores a property list file in the Preferences/ sub-directory.
• RISC Os (not to be dislocated with MIPS RISC/os) uses directories for configuration data, which allows applications to be copied into awarding directories, as opposed to the split installation process that typifies Windows applications; this approach is also used on the ROX Desktop for Linux.^[57] This directory-based configuration also makes it possible to use different versions of the same application, since the configuration is done "on the fly".^[58] If 1 wishes to remove the application, information technology is possible to simply delete the folder belonging to the application.^{[59] [60]} This will frequently not remove configuration settings which are stored independently from the application, normally inside the computer'due south !Boot construction, in !Kicking.Choices or potentially anywhere on a network fileserver. Information technology is possible to copy installed programs between computers running RISC OS by copying the application directories belonging to the programs, however some programs may crave re-installing, east.g. when shared files are placed outside an awarding directory.^[58]
• IBM AIX (a Unix variant) uses a registry component chosen Object Data Manager (ODM). The ODM is used to store information about arrangement and device configuration. An all-encompassing gear up of tools and utilities provides users with means of extending, checking, correcting the ODM database. The ODM stores its information in several files, default location is /etc/objrepos.
• The GNOME desktop environment uses a registry-like interface called dconf for storing configuration settings for the desktop and applications.
• The Elektra Initiative provides alternative back-ends for various different text configuration files.
• While not an operating organisation, the Wine compatibility layer, which allows Windows software to run on a Unix-like system, too employs a Windows-like registry as text files in the WINEPREFIX folder: organisation.reg (HKEY_LOCAL_MACHINE), user.reg (HKEY_CURRENT_USER) and userdef.reg.^[61]

Encounter also [edit]

• Registry cleaner
• Application virtualization
• LogParser – SQL-like querying of various types of log files
• Listing of Shell Icon Overlay Identifiers
• Ransomware attack that uses Registry

Notes [edit]

1. ^ When applications fail to execute because they request more privileges than they require (and are denied those privileges), this is known every bit a express user application (LUA) issues.

Footnotes [edit]

1. ^ Esposito, Dino (November 2000). "Windows 2000 Registry: Latest Features and APIs Provide the Ability to Customize and Extend Your Apps". MSDN Magazine. Microsoft. Archived from the original on April 15, 2003. Retrieved July 19, 2007.
2. ^ ^{a b c} "The System Registry".
3. ^ "Windows 95 Architecture Components". www.microsoft.com. Archived from the original on Feb 7, 2008. Retrieved April 29, 2008. The following table shows other difficulties or limitations caused by using .INI files that are overcome past using the Registry.
4. ^ Hipson 2002, p. 5, 41–43.
5. ^ Richter, Jeffrey; Nasarre, Christophe (2008). Windows Via C/C++ (Fifth ed.). Microsoft Press. ISBN9780735642461 . Retrieved August 28, 2021.
6. ^ Raymond Chen, "Why do registry keys have a default value?"
7. ^ Hipson 2002, pp. 207, 513–514.
8. ^ Hipson 2002, pp. 520–521.
9. ^ Hipson 2002, p. 7.
10. ^ "Designed for Windows XP Application Specification". Microsoft. August 20, 2002. Retrieved April 8, 2009.
11. ^ "HKEY_LOCAL_MACHINE". Gautam. 2009. Retrieved Apr 8, 2009.
12. ^ "Registry Keys Affected by WOW64 (Windows)". Msdn.microsoft.com. Retrieved Apr x, 2014.
13. ^ "Description of the Microsoft Windows registry". Retrieved September 25, 2008.
14. ^ "HKEY_CURRENT_USER". Microsoft. 2009. Retrieved April 8, 2009.
15. ^ "Description of the HKEY_DYN_DATA Registry Key in Windows 95, Windows 98, and Windows 98 SE". support.microsoft.com.
16. ^ "A Closer Expect at HKEY_DYN_DATA". rinet.ru. Archived from the original on May 9, 2008.
17. ^ "Registry hives". Retrieved July 19, 2007.
18. ^ Chen, Raymond (August 8, 2011). "Why is a registry file called a "hive"?". The Old New Thing. Retrieved July 29, 2011.
19. ^ "Overview of the Windows NT Registry". Retrieved December ii, 2011.
20. ^ "Inside the Registry". Retrieved December 28, 2007.
21. ^ ^{a b} Norris, Peter (February 2009). "The Internal Construction of the Windows Registry" (PDF). Cranfield University. Archived from the original (PDF) on May 29, 2009.
22. ^ "Incorrect Icons Displayed for .ico Files". November fifteen, 2009. Retrieved March 31, 2012.
23. ^ "How to Completely Uninstall / Remove a Software Program in Windows without using third Party Software? - AskVG". www.askvg.com.
24. ^ "You may receive a "Stop 0x00000035 NO_MORE_IRP_STACK_LOCATIONS" error bulletin when you try to log on to a domain". October 9, 2011. Retrieved March 31, 2012. This folio tells the user to edit the registry when resolving the issue.
25. ^ key renaming is implemented as removal and add while retaining subkeys/values, as the underlying APIs do not support the rename function directly
26. ^ ^{a b c d} "How to add, alter, or delete registry subkeys and values past using a .reg file". support.microsoft.com.
27. ^ "Applying Group Policy". Microsoft.
28. ^ ^{a b c} Payette, Bruce; Siddaway, Richard (2018). Windows PowerShell in Activity (Third ed.). Manning Publications. pp. 7–eight, 24, 608, 708–710. ISBN9781633430297 . Retrieved August 28, 2021.
29. ^ Warner, Timothy 50. (May 2015). Windows PowerShell in 24 Hours, Sams Teach Yourself. Sams Publishing. p. 19, 211. ISBN9780134049359 . Retrieved Baronial 28, 2021.
30. ^ "Reading and Writing Registry Values with Visual Basic". Retrieved July 19, 2007.
31. ^ "REG command in Windows XP". Retrieved July xix, 2007.
32. ^ "registry manual folio – Tcl Arranged Packages". www.tcl.tk . Retrieved December 14, 2017.
33. ^ "Offline Registry Library". Retrieved June 4, 2014.
34. ^ "DllInstall Function". Microsoft. March 7, 2012. Retrieved March 22, 2012.
35. ^ "Regsvr32". Microsoft. Retrieved March 22, 2012.
36. ^ "How to: Register Automation Servers". Microsoft. Retrieved March 22, 2012.
37. ^ "How to re-register PowerPoint 2000, PowerPoint 2003, PowerPoint 2007 and PowerPoint 2010". Microsoft. January 2012. Retrieved March 22, 2012.
38. ^ "RegNotifyChangeKeyValue function". Microsoft.
39. ^ "Registering for Notifications". Microsoft.
40. ^ "RegConnectRegistry office". Microsoft.
41. ^ "How to Manage Remote Access to the Registry". Microsoft.
42. ^ Gibson, Darril (June 28, 2011). "Chapter four: Securing Admission with Permissions". Microsoft Windows security : essentials. Indianapolis, Ind.: Wiley. ISBN978-1-118-01684-8.
43. ^ "Application Compatibility: Windows Resource Protection (WRP)". Microsoft. Retrieved August 8, 2012.
44. ^ Marc Silbey, Peter Brundrett. "Understanding and Working in Protected Mode Internet Explorer". Retrieved August 8, 2012.
45. ^ "RegDelNull v1.1". November 1, 2006. Retrieved August viii, 2012.
46. ^ "Unable to delete certain registry keys – Error while deleting key". March 23, 2010. Retrieved August 8, 2012. Microsoft Support page.
47. ^ "Description of the Windows Registry Checker Tool (Scanreg.exe)".
48. ^ "Command-Line Switches for the Registry Checker Tool".
49. ^ "How To Backup, Edit, and Restore the Registry in Windows NT 4.0". support.microsoft.com.
50. ^ "Technical Reference to the Registry: Related Resources". Microsoft. Retrieved September 9, 2011.
51. ^ "Microsoft Kills Automatic Registry Backups in Windows 10". ExtremeTech . Retrieved July one, 2019.
52. ^ "How Cadre Group Policy Works". Microsoft. September 2, 2009. Retrieved August 13, 2012.
53. ^ "Chapter 26 – Initialization Files and the Registry". Microsoft. Retrieved March iii, 2008.
54. ^ "Microsoft Application Compatibility Toolkit 5.0". Microsoft. Retrieved July 26, 2008.
55. ^ ^{a b} Ionescu, Marker Russinovich, David A. Solomon, Alex (2012). "Registry Internals". Windows internals (6th ed.). Redmond, Wash.: Microsoft Press. ISBN978-0-7356-4873-9.
56. ^ "XDG Base Directory Specification". standards.freedesktop.org.
57. ^ "Application directories". Archived from the original on May 27, 2012. Retrieved May 17, 2012.
58. ^ ^{a b} "Instance Studies Of The Acme 132 Annoyances With Operating Systems Other Than RISC Os". Retrieved April 3, 2012. Folio from the riscos.com website. Mentioned in points 82 and 104.
59. ^ "RISC Os bout". Retrieved July xix, 2007.
60. ^ "The RISC Bone Products Directory". November 2, 2006. Archived from the original on February 19, 2007. Retrieved April 1, 2012.
61. ^ three.2. Using the Registry and Regedit (Wine User Guide)

References [edit]

• Hipson, Peter (2002). Mastering Windows XP Registry. Wiley. ISBN0-7821-2987-0 . Retrieved Baronial 28, 2021.
• Russinovich, Mark E.; Solomon, David A. (2005). Microsoft Windows Internals (Quaternary ed.). Microsoft Printing. pp. 183–236. ISBN978-0-7356-1917-3.

External links [edit]

• Windows Registry info & reference in the MSDN Library

haindeast1966.blogspot.com

Source: https://en.wikipedia.org/wiki/Windows_Registry

Share this post