How To Root Windows Phone 8.1

Database for Microsoft Windows

Windows Registry

Registry Editor, the user interface for the registry, in Windows 10
Programmer(southward)	Microsoft
Initial release	April 6, 1992; 30 years ago  (1992-04-06) with Windows three.1
Operating system	Microsoft Windows
Platform	IA-32, x86-64 and ARM (and historically Dec Blastoff, Itanium, MIPS, and PowerPC)
Included with	Microsoft Windows
Type	Hierarchical database
Website	docs.microsoft.com/en-us/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 use the registry. The kernel, device drivers, services, Security Accounts Managing director, and user interfaces can all use the registry. The registry also 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 example, when a program is installed, a new subkey containing settings such every bit a program's location, its version, and how to start the programme, 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 data in the profusion of INI files, which held the configurations for individual programs, and were stored at various locations.^{[ane] [2]} It is not a requirement for Windows applications to utilize the Windows Registry. For instance, .NET Framework applications employ 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 as a text file or binary file, often located in a shared location that did non provide user-specific settings in a multi-user scenario. By dissimilarity, the Windows Registry stores all application settings in ane logical repository (but a number of discrete files) and in a standardized course. According to Microsoft, this offers several advantages over .INI files.^{[ii] [three]} Since file parsing is done much more than efficiently with a binary format, it may be read from or written to more apace than a text INI file. Furthermore, strongly typed data tin can be stored in the registry, as opposed to the text information stored in .INI files. This is a benefit when editing keys manually using regedit.exe, the congenital-in Windows Registry Editor. Because user-based registry settings are loaded from a user-specific path rather than from a read-just system location, the registry allows multiple users to share the same machine, and also allows programs to work for less privileged users. Backup and restoration is also simplified equally the registry tin be accessed over a network connection for remote direction/support, including from scripts, using the standard set up of APIs, every bit long equally the Remote Registry service is running and firewall rules permit this.

Because the registry is a database, it offers improved arrangement integrity with features such as atomic updates. If 2 processes attempt to update the same registry value at the same time, one process'due south change will precede the other'due south and the overall consistency of the data will be maintained. Where changes are made to .INI files, such race weather can consequence in inconsistent data that does not match either attempted update. Windows Vista and later operating systems provide transactional updates to the registry by means of the Kernel Transaction Director, extending the atomicity guarantees across multiple key and/or value changes, with traditional commit–abort semantics. (Note however that NTFS provides such support for the file system besides, so the aforementioned 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 indicate levels of hierarchy. Keys must have a case insensitive proper noun without backslashes.

The hierarchy of registry keys tin can only be accessed from a known root key handle (which is bearding but whose effective value is a constant 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 within another root fundamental, or mapped to a registered service or DLL that provides access to its contained subkeys and values.

E.one thousand. 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 according 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 (merely in Windows NT, just 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 exist restricted past admission 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 be predefined by the system itself, and configured past local system administrators or by domain administrators). Different users, programs, services or remote systems may just run into some parts of the bureaucracy or distinct hierarchies from the same root keys.

Registry values are name/data pairs stored inside keys. Registry values are referenced separately from registry keys. Each registry value stored in a registry key has a unique proper name whose letter of the alphabet instance is not meaning. The Windows API functions that query and manipulate registry values take value names separately from the key path and/or handle that identifies the parent fundamental. Registry values may contain backslashes in their names, but doing so makes them hard 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, as each registry central is similar to an associative array, where standard terminology would refer to the proper noun part of each registry value as a "primal". The terms are a holdout from the 16-bit registry in Windows 3, in which registry keys could not incorporate arbitrary name/data pairs, but rather contained just one unnamed value (which had to be a cord). In this sense, the Windows 3 registry was similar a unmarried associative assortment, in which the keys (in the sense of both 'registry primal' and 'associative array key') formed a hierarchy, and the registry values were all strings. When the 32-fleck registry was created, so was the additional capability of creating multiple named values per primal, and the meanings of the names were somewhat distorted.^[6] For compatibility with the previous behavior, each registry fundamental may have a "default" value, whose proper noun is the empty string.

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

Listing of standard registry value types

Type ID	Symbolic type proper name	Meaning and encoding of the information stored in the registry value
0	REG_NONE	No type (the stored value, if any)
1	REG_SZ	A string value, commonly stored and exposed in UTF-16LE (when using the Unicode version of Win32 API functions), usually terminated by a NUL grapheme
2	REG_EXPAND_SZ	An "expandable" string value that can contain surroundings variables, normally stored and exposed in UTF-16LE, usually terminated by a NUL grapheme
3	REG_BINARY	Binary data (any capricious data)
four	REG_DWORD / REG_DWORD_LITTLE_ENDIAN	A DWORD value, a 32-bit unsigned integer (numbers between 0 and 4,294,967,295 [232 – 1]) (little-endian)
v	REG_DWORD_BIG_ENDIAN	A DWORD value, a 32-flake unsigned integer (numbers betwixt 0 and 4,294,967,295 [232 – i]) (big-endian)
six	REG_LINK	A symbolic link (UNICODE) to another registry key, specifying a root fundamental and the path to the target cardinal
7	REG_MULTI_SZ	A multi-string value, which is an ordered list of non-empty strings, normally stored and exposed in Unicode, each one terminated past a zilch character, the list being commonly terminated by a second aught character.[8]
8	REG_RESOURCE_LIST	A resource list (used past the Plug-north-Play hardware enumeration and configuration)
9	REG_FULL_RESOURCE_DESCRIPTOR	A resource descriptor (used past the Plug-n-Play hardware enumeration and configuration)
10	REG_RESOURCE_REQUIREMENTS_LIST	A resources requirements list (used by the Plug-n-Play hardware enumeration and configuration)
xi	REG_QWORD / REG_QWORD_LITTLE_ENDIAN	A QWORD value, a 64-bit integer (either big- or little-endian, or unspecified) (introduced in Windows 2000)[9]

Root keys [edit]

The keys at the root level of the hierarchical database are more often than not named by their Windows API definitions, which all begin "HKEY".^[2] They are oft abbreviated to a three- or 4-letter short name starting with "HK" (east.g. 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 system kernel at boot time and so 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 car-specific configuration data) and HKEY_CURRENT_USER (user-specific configuration data) nodes accept a like construction to each other; user applications typically look up their settings by first checking for them in "HKEY_CURRENT_USER\Software\Vendor's proper name\Application's name\Version\Setting proper name", and if the setting is not found, look instead in the same location under the HKEY_LOCAL_MACHINE key^{[ citation needed ]}. However, the converse may apply for administrator-enforced policy settings where HKLM may have precedence over HKCU. The Windows Logo Program has specific requirements for where different types of user data may be stored, and that the concept of to the lowest degree privilege be followed so that ambassador-level access is not 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.^[xi]

The key located by HKLM is actually not stored on disk, but maintained in memory past the system kernel in order to map all the other subkeys. Applications cannot create any additional subkeys. On Windows NT, this central contains four subkeys, "SAM", "SECURITY", "Organization", and "SOFTWARE", that are loaded at kick time within their respective files located in the %SystemRoot%\System32\config folder. A 5th subkey, "HARDWARE", is volatile and is created dynamically, and as such is not stored in a file (it exposes a view of all the currently detected Plug-and-Play devices). On Windows Vista and above, 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 kicking configuration data, \kicking\BCD on the system partition.

• The "HKLM\SAM" key usually appears as empty for virtually users (unless they are granted access past administrators of the local system or administrators of domains managing the local system). It is used to reference all "Security Accounts Manager" (SAM) databases for all domains into which the local arrangement has been administratively authorized or configured (including the local domain of the running organization, whose SAM database is stored in a subkey as well named "SAM": other subkeys volition be created as needed, one for each supplementary domain). Each SAM database contains all builtin accounts (generally grouping aliases) and configured accounts (users, groups and their aliases, including invitee accounts and administrator accounts) created and configured on the corresponding domain, for each account in that domain, it notably contains the user name which tin 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 status flags (for example if the account can be enumerated and exist visible in the logon prompt screen), and the listing of domains (including the local domain) into which the account was configured.
• The "HKLM\SECURITY" key unremarkably appears empty for nigh 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 system domain, this key will exist linked to the registry hive stored by the local motorcar and managed by local system administrators or by the builtin "System" account and Windows installers). The kernel will access it to read and enforce the security policy applicative to the electric current user and all applications or operations executed by this user. It besides contains a "SAM" subkey which is dynamically linked to the SAM database of the domain onto which the current user is logged on.
• The "HKLM\Organisation" central is normally only writable by users with administrative privileges on the local system. It contains information near the Windows system setup, data for the secure random number generator (RNG), the list of currently mounted devices containing a filesystem, several numbered "HKLM\SYSTEM\Control Sets" containing alternative configurations for system hardware drivers and services running on the local system (including the currently used 1 and a backup), a "HKLM\Arrangement\Select" subkey containing the status of these Control Sets, and a "HKLM\Organization\CurrentControlSet" which is dynamically linked at boot time to the Control Prepare which is currently used on the local system. Each configured Control Set contains:
  • an "Enum" subkey enumerating all known Plug-and-Play devices and associating them with installed system drivers (and storing the device-specific configurations of these drivers),
  • a "Services" subkey listing all installed system 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 can be automatically started),
  • a "Control" subkey organizing the various hardware drivers and programs running as services and all other system-wide configuration,
  • a "Hardware Profiles" subkey enumerating the various profiles that accept been tuned (each one with "System" or "Software" settings used to change the default profile, either in system drivers and services or in the applications) likewise as the "Hardware Profiles\Current" subkey which is dynamically linked to ane of these profiles.
• The "HKLM\SOFTWARE" subkey contains software and Windows settings (in the default hardware profile). Information technology is by and large modified by application and organization installers. Information technology is organized by software vendor (with a subkey for each), only 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 handling these types on the local machine (yet these associations are configurable for each user, see below), and a "Policies" subkey (also organized by vendor) for enforcing general usage policies on applications and organisation services (including the central certificates store used for authenticating, authorizing or disallowing remote systems or services running exterior the local network domain).
• The "HKLM\SOFTWARE\Wow6432Node" central is used by 32-bit applications on a 64-bit Windows OS, and is equivalent to but separate from "HKLM\SOFTWARE". The key path is transparently presented to 32-bit applications by WoW64 as HKLM\SOFTWARE^[12] (in a similar mode that 32-flake applications see %SystemRoot%\Syswow64 equally %SystemRoot%\System32)

HKEY_CLASSES_ROOT (HKCR) [edit]

Abbreviated HKCR, HKEY_CLASSES_ROOT contains information about registered applications, such as file associations and OLE Object Class IDs, tying them to the applications used to handle these items. On Windows 2000 and in a higher place, HKCR is a compilation of user-based HKCU\Software\Classes and machine-based HKLM\Software\Classes. If a given value exists in both of the subkeys higher up, the one in HKCU\Software\Classes takes precedence.^[13] The design 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 motorcar, though user hives are normally only 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.^[14] The HKEY_CURRENT_USER cardinal 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)" key has the following suffix "(HKCU)\Software\Classes\..." then information technology corresponds to "(HKU)\(SID)_CLASSES\..." i.e. 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 inside their own Documents and Settings subfolder (or their ain Users sub folder in Windows Vista and to a higher place). Settings in this hive follow users with a roaming contour from automobile to automobile.

HKEY_PERFORMANCE_DATA [edit]

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

HKEY_DYN_DATA [edit]

This fundamental is used merely on Windows 95, Windows 98 and Windows ME.^[15] Information technology contains data about hardware devices, including Plug and Play and network performance statistics. The data in this hive is besides non stored on the hard drive. The Plug and Play data is gathered and configured at startup and is stored in memory.^[16]

Hives [edit]

Fifty-fifty though the registry presents itself every bit an integrated hierarchical database, branches of the registry are actually stored in a number of deejay files called hives.^[17] (The word hive constitutes an in-joke.)^[18]

Some hives are volatile and are not stored on disk at all. An example of this is the hive of the branch starting at HKLM\HARDWARE. This hive records information about system hardware and is created each fourth dimension 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 organisation loads the user hive under the HKEY_USERS primal and sets the HKCU (HKEY_CURRENT_USER) symbolic reference to point to the current user. This allows applications to store/call back settings for the current user implicitly under the HKCU primal.

Not all hives are loaded at any 1 time. At boot fourth dimension, only a minimal set up of hives are loaded, and after that, hives are loaded every bit the operating system initializes and as users log in or whenever a hive is explicitly loaded past an awarding.

File locations [edit]

The registry is physically stored in several files, which are generally obfuscated from the user-style 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, simply they are all on the local automobile. The location for system 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. There is 1 of these per user; if a user has a roaming contour, so this file will be 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 tin be exported, loaded and unloaded by the Registry Editor in these operating systems. The following arrangement 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\Organization
• Default – HKEY_USERS\.DEFAULT
• Userdiff – Not associated with a hive. Used only when upgrading operating systems.^[19]

The post-obit 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 following 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 non localized) allonym %LocalAppData%\Microsoft\Windows\Usrclass.dat – HKEY_USERS\<User SID>_Classes (HKEY_CURRENT_USER\Software\Classes)

Windows 2000 keeps an alternating 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 considering NTLDR on those versions of Windows can process the System.log file to bring upward to appointment a System hive that has become inconsistent during a shutdown or crash. In addition, the %SystemRoot%\Repair binder contains a re-create of the organisation's registry hives that were created after installation and the outset successful startup of Windows.

Each registry information file has an associated file with a ".log" extension that acts as a transaction log that is used to ensure that whatsoever interrupted updates tin exist completed upon side by side startup.^[21] Internally, Registry files are split 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 Organization.DAT with the improver of CLASSES.DAT in Windows ME. Also, each user profile (if profiles are enabled) has its ain USER.DAT file which is located in the user's profile directory in %WINDIR%\Profiles\<Username>\.

Windows three.eleven [edit]

The only registry file is called REG.DAT and information technology is stored in the %WINDIR% directory.

Windows 10 Mobile [edit]

Notation: To access the registry files, the Phone needs to be gear up in a special mode using either:

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

If any of above Methods worked - The Device Registry Files can exist found in the post-obit 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 system, for installed applications too as individual settings for each user and application. A devil-may-care change to the operating system configuration in the registry could cause irreversible damage, and then information technology is ordinarily 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 fill-in of the registry be performed before the modify.^[22] When a plan is removed from control panel, information technology may not be completely removed and, in case of errors or glitches caused by references to missing programs, the user might have to manually check inside directories such as program files. Later on this, the user might need to manually remove whatsoever reference to the uninstalled program in the registry. This is ordinarily washed past using RegEdit.exe.^[23] Editing the registry is sometimes necessary when working around Windows-specific issues eastward.thousand. problems when logging onto a domain can be resolved past editing the registry.^[24]

Windows Registry tin be edited manually using programs such as RegEdit.exe, although these tools do not betrayal some of the registry'southward metadata such equally the last modified engagement.

The registry editor for the 3.one/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-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 just)
• Bookmarking user-selected registry keys as Favorites
• Finding item strings in fundamental names, value names and value data
• Remotely editing the registry on another networked reckoner

.REG files [edit]

.REG files (also known every bit 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 later, they comprise the string Windows Registry Editor Version five.00 at the beginning and are Unicode-based. On Windows 9x and NT iv.0 systems, they contain the cord REGEDIT4 and are ANSI-based.^[26] Windows 9x format .REG files are compatible with Windows 2000 and later. The Registry Editor on Windows on these systems too supports exporting .REG files in Windows 9x/NT format. Data is stored in .REG files using the following syntax:^[26]

                        [<Hive proper name>\<Fundamental name>\<Subkey name>]            "Value proper noun"            =            <Value type>:<Value information>          

The Default Value of a key can be edited past using "@" instead of "Value Proper name":

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

String values exercise not require a <Value type> (come across instance), but backslashes ('\') need to exist written as a double-backslash ('\\'), and quotes ('"') as backslash-quote ('\"').

For instance, to add together the values "Value A", "Value B", "Value C", "Value D", "Value E", "Value F", "Value M", "Value H", "Value I", "Value J", "Value K", "Value L", and "Value Thousand" to the HKLM\SOFTWARE\Foobar key:

            Windows Registry Editor Version v.00            [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            "Value A"            =            "<String 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 (equally comma-delimited list of hexadecimal values)>            "Value E"            =            hex(1):<REG_SZ (as comma-delimited list of hexadecimal values representing a UTF-16LE NUL-terminated string)>            "Value F"            =            hex(2):<Expandable string value data (as comma-delimited listing of hexadecimal values representing a UTF-16LE NUL-terminated cord)>            "Value G"            =            hex(3):<Binary information (as comma-delimited list of hexadecimal values)> ; equal to "Value B"            "Value H"            =            hex(4):<DWORD value (as comma-delimited list of 4 hexadecimal values, in lilliputian endian byte society)>            "Value I"            =            hex(v):<DWORD value (as comma-delimited list of 4 hexadecimal values, in big endian byte guild)>            "Value J"            =            hex(vii):<Multi-cord value data (every bit comma-delimited list of hexadecimal values representing UTF-16LE NUL-terminated strings)>            "Value K"            =            hex(8):<REG_RESOURCE_LIST (equally comma-delimited list of hexadecimal values)>            "Value L"            =            hex(a):<REG_RESOURCE_REQUIREMENTS_LIST (every bit comma-delimited list of hexadecimal values)>            "Value M"            =            hex(b):<QWORD value (as comma-delimited list of viii hexadecimal values, in little endian byte order)>          

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

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

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

                        [            -            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]          

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

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

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

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

                        [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            @            =-          

Lines beginning with a semicolon are considered comments:

                        ; This is a comment. This can be placed in any function of a .reg file            [            HKEY_LOCAL_MACHINE            \SOFTWARE\Foobar]            "Value"            =            "Example cord"          

Group policies [edit]

Windows group policies can change registry keys for a number of machines or individual users based on policies. When a policy first takes effect for a machine or for an individual user of a car, the registry settings specified as part of the policy are applied to the motorcar or user settings.

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

Through its scope a policy defines which machines and/or users the policy is to be applied to. Whether a motorcar or user is within the scope of a policy or not is divers by a set of rules which tin can filter on the location of the machine or user account in organizational directory, specific users or machine accounts or security groups. More than advanced rules tin can exist gear up using Windows Management Instrumentation expressions. Such rules can filter on properties such as reckoner vendor name, CPU compages, installed software, or networks continued to.

For instance, the ambassador tin create a policy with one set of registry settings for machines in the accounting department and policy with another (lock-downwardly) set of registry settings for kiosk terminals in the visitors area. When a car is moved from one scope to some other (e.g. changing its name or moving information technology to some other organizational unit), the correct policy is automatically practical. When a policy is inverse it is automatically re-applied to all machines currently in its telescopic.

The policy is edited through a number of authoritative templates which provides a user interface for picking and changing settings. The set of authoritative templates is extensible and software packages which back up such remote administration can register their own templates.

Control line editing [edit]

reg

Developer(south)	Microsoft
Operating system	Microsoft Windows
Blazon	Control
License	Proprietary commercial software
Website	docs.microsoft.com/en-us/windows-server/administration/windows-commands/reg

regini

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

The registry tin be manipulated in a number of means from the command 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 Resource Kit CDs or the original Installation CD of Windows.

Also, a .REG file can be imported from the control line with the post-obit control:

RegEdit.exe /s          file        

The /southward 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 /s switch as well causes RegEdit.exe to ignore the setting in the registry that allows administrators to disable information technology. When using the /s switch RegEdit.exe does non return an advisable 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 whatever of

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

export the specified (sub)fundamental (which has to be enclosed in quotes if information technology contains spaces) only.

RegEdit.exe /a          file        

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

RegEdit.exe /a          file          <key>        

exports the specified (sub)key (which has to be enclosed in quotes if information technology 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 tin 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 primal can be displayed using:

                        SubInACL.exe            /keyreg            HKEY_LOCAL_MACHINE\SOFTWARE            /brandish          

PowerShell commands and scripts [edit]

Using PowerShell to navigate the registry

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

Too like the file arrangement, PowerShell uses the concept of a current location which defines the context on which commands by default operate. The Become-ChildItem (also available through the aliases ls, dir or gci) retrieves the child keys of the electric current location. By using the Fix-Location (or the allonym cd) command the user can change the 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 can be used to rename keys, remove keys or entire sub-trees or alter values.

Through PowerShell scripts files, an administrator can prepare scripts which, when executed, brand changes to the registry. Such scripts tin can be distributed to administrators who can execute them on individual machines. The PowerShell Registry provider supports transactions, i.east. multiple changes to the registry can exist bundled into a unmarried atomic 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 exist edited through the APIs of the Avant-garde Windows 32 Base API Library (advapi32.dll).^[30] List of registry API functions:

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

Many programming languages offering built-in runtime library functions or classes that wrap the underlying Windows APIs and thereby enable programs to shop settings in the registry (east.g. Microsoft.Win32.Registry in VB.Cyberspace and C#, or TRegistry in Delphi and Free Pascal). COM-enabled applications like Visual Bones half-dozen can utilize the WSH WScript.Crush object. Some other way is to utilise the Windows Resource Kit Tool, Reg.exe past executing it from code,^[31] although this is considered poor programming practice.

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 as well enable registry editing from scripts.

Offline editing [edit]

The offreg.dll^[33] available from the Windows Commuter Kit offers a set up of APIs for the cosmos and manipulation of currently not loaded registry hives similar to those provided by advapi32.dll.

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

COM cocky-registration [edit]

Prior to the introduction of registration-free COM, developers were encouraged to add initialization code to in-procedure and out-of-procedure binaries to perform the registry configuration required for that object to work. For in-process binaries such every bit .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 like 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 problems tin 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-manner applications to annals to receive a notification issue if a particular registry key is changed.^[38] APIs are also available to allow kernel-way applications to filter and modify registry calls fabricated by other applications.^[39]

Windows likewise supports remote access to the registry of another computer via the RegConnectRegistry office^[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 can accept an associated security descriptor. The security descriptor contains an access control listing (ACL) that describes which user groups or individual users are granted or denied access permissions. The gear up of registry permissions include 10 rights/permissions which can be explicitly immune or denied to a user or a group of users.

Registry permissions

Permission	Description
Query Value	The right to read the registry key value.
Prepare Value	The right to write a new value
Create Subkey	The right to create subkeys.
Enumerate Subkeys	Allow the enumeration of subkeys.
Notify	The right to asking change notifications for registry keys or subkeys.
Create Link	Reserved by the operating system.
Delete	The right to delete a key.
Write DACL	The right to modify permissions of the container's DACL.
Write Owner	The right to alter the container's owner.
Read Command	The right to read the DACL.

As with other securable objects in the operating arrangement, individual access control entries (ACE) on the security descriptor can be explicit or inherited from a parent object.^[42]

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

Special ACEs on the security descriptor tin also implement mandatory integrity command for the registry key and subkeys. A process running at a lower integrity level cannot write, change or delete a registry key/value, even if the business relationship of the process has otherwise been granted access through the ACL. For case, Internet Explorer running in Protected Fashion tin read medium and depression integrity registry keys/values of the currently logged on user, but it can only alter low integrity keys.^[44]

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

Backups and recovery [edit]

Different editions of Windows take supported a number of dissimilar methods to back up and restore the registry over the years, some of which are at present deprecated:

• Organization Restore can support the registry and restore it as long as Windows is bootable, or from the Windows Recovery Surroundings (starting with Windows Vista).
• NTBackup can back up the registry as role of the System State and restore it. Automated Arrangement Recovery in Windows XP tin also restore the registry.
• On Windows NT, the Last Known Skilful Configuration option in startup menu relinks the HKLM\Organisation\CurrentControlSet key, which stores hardware and device driver information.
• Windows 98 and Windows ME include command line (Scanreg.exe) and GUI (Scanregw.exe) registry checker tools to check and fix the integrity of the registry, create up to five automatic regular backups by default and restore them manually or whenever corruption is detected.^[47] The registry checker tool backs upwards the registry, by default, to %Windir%\Sysbckup Scanreg.exe can likewise 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 upward the registry to the files organisation.da0 and user.da0 on every successful boot.
• Windows NT 4.0 included RDISK.EXE, a utility to support and restore the entire registry.^[49]
• Windows 2000 Resource Kit contained an unsupported pair of utilities called Regback.exe and RegRest.exe for fill-in and recovery of the registry.^[50]
• Periodic automatic backups of the registry are now disabled past default on Windows 10 May 2019 Update (version 1903). Microsoft recommends System Restore be used instead.^[51]

Policy [edit]

Group policy [edit]

Windows 2000 and subsequently versions of Windows use 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 figurer 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 can use a special file to be merged into the registry, called a policy file (POLICY.Politician). The policy file allows administrators to foreclose non-administrator users from changing registry settings like, for example, the security level of Internet 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 concern needs to exist protected from rogue or devil-may-care users.

The default extension for the policy file is .POL. The policy file filters the settings it enforces by user and by group (a "group" is a defined prepare of users). To do that the policy file merges into the registry, preventing users from circumventing information technology past only irresolute back the settings. The policy file is usually distributed through a LAN, just can be placed on the local calculator.

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

Virtualization [edit]

INI file virtualization [edit]

Windows NT kernels support 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 allow legacy applications written for xvi-bit versions of Windows to be able to run under Windows NT platforms on which the System folder is no longer considered an appropriate location for user-specific data or configuration. Non-compliant 32-bit applications can also exist redirected in this manner, even though the characteristic was originally intended for 16-chip applications.

Registry virtualization [edit]

Windows Vista introduced limited registry virtualization, whereby poorly written applications that exercise not respect the principle of least privilege and instead endeavour to write user information to a read-only organization location (such as the HKEY_LOCAL_MACHINE hive), are silently redirected to a more appropriate location, without changing the application itself.

Similarly, application virtualization redirects all of an application'southward invalid registry operations to a location such as a file. Used together with file virtualization, this allows applications to run on a motorcar without being installed on it.

Depression integrity processes may also employ registry virtualization. For example, Cyberspace Explorer vii or 8 running in "Protected Mode" on Windows Vista and higher up will automatically redirect registry writes by ActiveX controls to a sandboxed location in gild to frustrate some classes of security exploits.

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

Disadvantages [edit]

Critics labeled the registry in Windows 95 a single signal of failure, considering re-installation of the operating system was required if the registry became corrupt.^{[ citation needed ]} Notwithstanding, 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 similar catastrophic events during database updates.^[55] Even in the case of a not-recoverable error, Windows tin repair or re-initialize damaged registry entries during system kicking.^[55]

Equivalents and alternatives [edit]

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

In contrast to Windows Registry's binary-based database model, some other operating systems use separate manifestly-text files for daemon and application configuration, simply group these configurations together for ease of direction.

• In Unix-like operating systems (including Linux) that follow the Filesystem Hierarchy Standard, system-broad configuration files (information like to what would appear 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 (data that would be roughly equivalent to that in HKEY_CURRENT_USER) is stored in hidden directories and files (that showtime with a menstruum/full stop) within the user's abode directory. However XDG-compliant applications should refer to the environment variables divers in the Base Directory specification.^[56]
• In macOS, system-wide configuration files are typically stored in the /Library/ binder, whereas per-user configuration files are stored in the corresponding ~/Library/ folder in the user'southward home directory, and configuration files set by the organisation are in /Organisation/Library/. Within these respective directories, an application typically stores a holding list file in the Preferences/ sub-directory.
• RISC OS (not to be confused with MIPS RISC/os) uses directories for configuration data, which allows applications to be copied into application directories, as opposed to the separate installation process that typifies Windows applications; this approach is besides used on the ROX Desktop for Linux.^[57] This directory-based configuration besides makes it possible to use different versions of the same application, since the configuration is done "on the fly".^[58] If one wishes to remove the application, information technology is possible to just delete the binder belonging to the application.^{[59] [60]} This will often not remove configuration settings which are stored independently from the application, usually within the computer'due south !Boot structure, in !Boot.Choices or potentially anywhere on a network fileserver. It is possible to copy installed programs between computers running RISC Os by copying the application directories belonging to the programs, however some programs may require re-installing, due east.g. when shared files are placed outside an application directory.^[58]
• IBM AIX (a Unix variant) uses a registry component called Object Data Manager (ODM). The ODM is used to shop data nigh system and device configuration. An extensive set up of tools and utilities provides users with means of extending, checking, correcting the ODM database. The ODM stores its data in several files, default location is /etc/objrepos.
• The GNOME desktop environment uses a registry-similar interface called dconf for storing configuration settings for the desktop and applications.
• The Elektra Initiative provides alternative dorsum-ends for various different text configuration files.
• While not an operating system, the Wine compatibility layer, which allows Windows software to run on a Unix-similar system, also employs a Windows-similar registry every bit text files in the WINEPREFIX binder: system.reg (HKEY_LOCAL_MACHINE), user.reg (HKEY_CURRENT_USER) and userdef.reg.^[61]

Run into also [edit]

• Registry cleaner
• Awarding virtualization
• LogParser – SQL-similar querying of various types of log files
• List of Shell Icon Overlay Identifiers
• Ransomware attack that uses Registry

Notes [edit]

1. ^ When applications neglect to execute considering they request more privileges than they require (and are denied those privileges), this is known equally 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 nineteen, 2007.
2. ^ ^{a b c} "The Organisation Registry".
3. ^ "Windows 95 Compages Components". www.microsoft.com. Archived from the original on February vii, 2008. Retrieved April 29, 2008. The following table shows other difficulties or limitations caused by using .INI files that are overcome by using the Registry.
4. ^ Hipson 2002, p. v, 41–43.
5. ^ Richter, Jeffrey; Nasarre, Christophe (2008). Windows Via C/C++ (5th ed.). Microsoft Printing. ISBN9780735642461 . Retrieved Baronial 28, 2021.
6. ^ Raymond Chen, "Why practise registry keys have a default value?"
7. ^ Hipson 2002, pp. 207, 513–514.
8. ^ Hipson 2002, pp. 520–521.
9. ^ Hipson 2002, p. vii.
10. ^ "Designed for Windows XP Application Specification". Microsoft. August 20, 2002. Retrieved April eight, 2009.
11. ^ "HKEY_LOCAL_MACHINE". Gautam. 2009. Retrieved April 8, 2009.
12. ^ "Registry Keys Afflicted by WOW64 (Windows)". Msdn.microsoft.com. Retrieved Apr 10, 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 Fundamental in Windows 95, Windows 98, and Windows 98 SE". back up.microsoft.com.
16. ^ "A Closer Look at HKEY_DYN_DATA". rinet.ru. Archived from the original on May ix, 2008.
17. ^ "Registry hives". Retrieved July 19, 2007.
18. ^ Chen, Raymond (Baronial 8, 2011). "Why is a registry file chosen a "hive"?". The Old New Matter. Retrieved July 29, 2011.
19. ^ "Overview of the Windows NT Registry". Retrieved December 2, 2011.
20. ^ "Inside the Registry". Retrieved December 28, 2007.
21. ^ ^{a b} Norris, Peter (February 2009). "The Internal Structure of the Windows Registry" (PDF). Cranfield Academy. Archived from the original (PDF) on May 29, 2009.
22. ^ "Wrong 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 3rd Party Software? - AskVG". world wide web.askvg.com.
24. ^ "Yous may receive a "Stop 0x00000035 NO_MORE_IRP_STACK_LOCATIONS" error message when you effort to log on to a domain". Oct ix, 2011. Retrieved March 31, 2012. This page tells the user to edit the registry when resolving the issue.
25. ^ key renaming is implemented as removal and add while retaining subkeys/values, equally the underlying APIs do not support the rename function direct
26. ^ ^{a b c d} "How to add together, modify, or delete registry subkeys and values by using a .reg file". support.microsoft.com.
27. ^ "Applying Group Policy". Microsoft.
28. ^ ^{a b c} Payette, Bruce; Siddaway, Richard (2018). Windows PowerShell in Action (Third ed.). Manning Publications. pp. 7–8, 24, 608, 708–710. ISBN9781633430297 . Retrieved August 28, 2021.
29. ^ Warner, Timothy L. (May 2015). Windows PowerShell in 24 Hours, Sams Teach Yourself. Sams Publishing. p. nineteen, 211. ISBN9780134049359 . Retrieved August 28, 2021.
30. ^ "Reading and Writing Registry Values with Visual Basic". Retrieved July nineteen, 2007.
31. ^ "REG command in Windows XP". Retrieved July 19, 2007.
32. ^ "registry transmission folio – Tcl Bundled Packages". www.tcl.tk . Retrieved December fourteen, 2017.
33. ^ "Offline Registry Library". Retrieved June 4, 2014.
34. ^ "DllInstall Role". Microsoft. March 7, 2012. Retrieved March 22, 2012.
35. ^ "Regsvr32". Microsoft. Retrieved March 22, 2012.
36. ^ "How to: Annals 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 function". Microsoft.
41. ^ "How to Manage Remote Access to the Registry". Microsoft.
42. ^ Gibson, Darril (June 28, 2011). "Affiliate 4: Securing Access with Permissions". Microsoft Windows security : essentials. Indianapolis, Ind.: Wiley. ISBN978-1-118-01684-eight.
43. ^ "Application Compatibility: Windows Resource Protection (WRP)". Microsoft. Retrieved August eight, 2012.
44. ^ Marc Silbey, Peter Brundrett. "Understanding and Working in Protected Mode Cyberspace Explorer". Retrieved Baronial 8, 2012.
45. ^ "RegDelNull v1.i". Nov 1, 2006. Retrieved August 8, 2012.
46. ^ "Unable to delete sure registry keys – Error while deleting key". March 23, 2010. Retrieved August 8, 2012. Microsoft Support page.
47. ^ "Clarification of the Windows Registry Checker Tool (Scanreg.exe)".
48. ^ "Command-Line Switches for the Registry Checker Tool".
49. ^ "How To Fill-in, Edit, and Restore the Registry in Windows NT iv.0". support.microsoft.com.
50. ^ "Technical Reference to the Registry: Related Resources". Microsoft. Retrieved September ix, 2011.
51. ^ "Microsoft Kills Automatic Registry Backups in Windows 10". ExtremeTech . Retrieved July 1, 2019.
52. ^ "How Cadre Grouping Policy Works". Microsoft. September 2, 2009. Retrieved Baronial xiii, 2012.
53. ^ "Affiliate 26 – Initialization Files and the Registry". Microsoft. Retrieved March 3, 2008.
54. ^ "Microsoft Application Compatibility Toolkit v.0". Microsoft. Retrieved July 26, 2008.
55. ^ ^{a b} Ionescu, Marking Russinovich, David A. Solomon, Alex (2012). "Registry Internals". Windows internals (6th ed.). Redmond, Wash.: Microsoft Printing. ISBN978-0-7356-4873-nine.
56. ^ "XDG Base Directory Specification". standards.freedesktop.org.
57. ^ "Awarding directories". Archived from the original on May 27, 2012. Retrieved May 17, 2012.
58. ^ ^{a b} "Case Studies Of The Top 132 Annoyances With Operating Systems Other Than RISC Os". Retrieved Apr iii, 2012. Page from the riscos.com website. Mentioned in points 82 and 104.
59. ^ "RISC OS bout". Retrieved July nineteen, 2007.
60. ^ "The RISC OS Products Directory". November 2, 2006. Archived from the original on February 19, 2007. Retrieved April 1, 2012.
61. ^ 3.2. Using the Registry and Regedit (Wine User Guide)

References [edit]

• Hipson, Peter (2002). Mastering Windows XP Registry. Wiley. ISBN0-7821-2987-0 . Retrieved August 28, 2021.
• Russinovich, Marking E.; Solomon, David A. (2005). Microsoft Windows Internals (Fourth ed.). Microsoft Press. pp. 183–236. ISBN978-0-7356-1917-three.

External links [edit]

• Windows Registry info & reference in the MSDN Library

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

Posted by: kruegerbittly.blogspot.com

Share this post