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 Manager, and user interface can all use the registry. The registry also allows access to counters for profiling system performance.
(Redirected from HKEY CURRENT USER)
In simple terms, 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 as a program's location, its version, and how to start the program, are all added to the Windows Registry.
Windows 10 comes with a hidden secret Dark theme mode which can be unlocked and tested in Modern (metro) apps: 1. In Registry Editor, go to following key: HKEYCURRENTUSER SOFTWARE Microsoft Windows CurrentVersion Themes Personalize. In right-side pane, create a new DWORD AppsUseLightTheme and leave its value to 0. W10usfclearoverridehkcu.zip â Windows 10 Clear the Overriding registry values for HKCU (See Table 2). HKCU is short for HKEYCURRENTUSER & HKLM is HKEYLOCALMACHINE. List of Shell folders & their default locations in Windows 10. Per-User: For the current user account, the special folder paths are stored in the following registry key.
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 rationalise and centralise the information in the profusion of INI files, which held the configurations for individual programs, and were stored at various locations.[1][2] It is not a requirement for Windows applications to use the Windows Registry. For example, .NET 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 as a text file, often located in a shared location that did not provide user-specific settings in a multi-user scenario. By contrast, the Windows Registry stores all application settings in one logical repository (but a number of discrete files) and in a standardized form. According to Microsoft, this offers several advantages over .INI files.[2][3] Since file parsing is done much more efficiently with a binary format, it may be read from or written to more quickly than an 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 benefit 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 same machine, and also allows programs to work for less privileged users. Backup and restoration is also simplified as the registry can be accessed over a network connection for remote management/support, including from scripts, using the standard set of APIs, as long as 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 same registry value at the same time, one process's change will precede the other's and the overall consistency of the data will be maintained. Where changes are made to .INI files, such race conditions can result 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 Manager, 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 as well, 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 contain 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 name without backslashes.
The hierarchy of registry keys can only be accessed from a known root key handle (which is anonymous but whose effective value is a constant numeric handle) that is mapped to the content of a registry key preloaded by the kernel from a stored 'hive', or to the content of a subkey within another root key, or mapped to a registered service or DLL that provides access to its contained subkeys and values.
E.g. HKEY_LOCAL_MACHINESoftwareMicrosoftWindows refers to the subkey 'Windows' of the subkey 'Microsoft' of the subkey 'Software' of the HKEY_LOCAL_MACHINE root key.
There are seven predefined root keys, traditionally named according to their constant handles defined in the Win32 API, or by synonymous abbreviations (depending on applications):
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 be predefined by the system itself, and configured by local system administrators or by domain administrators). Different users, programs, services or remote systems may only 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 key has a unique name whose letter case is not significant. 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 key. Registry values may contain backslashes in their names, but doing so 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, as each registry key is similar to an associative array, where standard terminology would refer to the name part of each registry value as a 'key'. The terms are a holdout from the 16-bit registry in Windows 3, in which registry keys could not contain arbitrary name/data pairs, but rather contained only one unnamed value (which had to be a string). In this sense, the Windows 3 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 additional capability of creating multiple named values per key, and the meanings of the names were somewhat distorted.[4] For compatibility with the previous behavior, each registry key may have a 'default' value, whose name is the empty string.
Each value can store arbitrary data 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:
Root keys[edit]
The keys at the root level of the hierarchical database are generally named by their WindowsAPI definitions, which all begin 'HKEY'.[2] They are frequently abbreviated to a three- or four-letter short name starting with 'HK' (e.g. HKCU and HKLM). Technically, they are predefined handles (with known constant 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 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 system.
The HKEY_LOCAL_MACHINE (local machine-specific configuration data) and HKEY_CURRENT_USER (user-specific configuration data) nodes have a similar structure to each other; user applications typically look up their settings by first checking for them in 'HKEY_CURRENT_USERSoftwareVendor's nameApplication's nameVersionSetting 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 take 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 least privilege be followed so that administrator-level access is not required to use an application.[a][5]
HKEY_LOCAL_MACHINE (HKLM)[edit]
Abbreviated HKLM, HKEY_LOCAL_MACHINE stores settings that are specific to the local computer.[6]
The key located by HKLM is actually not stored on disk, but 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 respective files located in the %SystemRoot%System32config folder. A fifth 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%system32configCOMPONENTS or from boot configuration data, bootBCD on the system partition.
HKEY_CURRENT_CONFIG (HKCC)[edit]
HKEY_CLASSES_ROOT (HKCR)[edit]
HKEY_USERS (HKU)[edit]
HKEY_CURRENT_USER (HKCU)[edit]
HKEY_PERFORMANCE_DATA[edit]
HKEY_DYN_DATA[edit]
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.[12] (The word hive constitutes an in-joke.)[13]
Some hives are volatile and are not stored on disk at all. An example of this is the hive of branch starting at HKLMHARDWARE. This hive records information about 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 key and sets the HKCU (HKEY_CURRENT_USER) symbolic reference to point to the current user. This allows applications to store/retrieve settings for the current user implicitly under the HKCU key.
Not all hives are loaded at any one time. At boot time, only a minimal set of hives are loaded, and after that, hives are loaded as the operating system initializes and as users log in or whenever a hive is explicitly loaded by an application.
File locations[edit]
The registry is physically stored in several files, which are generally obfuscated from the user-mode APIs used to manipulate the data inside the registry. Depending upon the version of Windows, there will be different files and different locations for these files, but they are all on the local machine. The location for system registry files in Windows NT is %SystemRoot%System32Config; the user-specific HKEY_CURRENT_USER user registry hive is stored in
Ntuser.dat inside the user profile. There is one of these per user; if a user has a roaming profile, then 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]Hkey_current_user Keyboard Layout Preload Windows 10
Windows NT systems store the registry in a binary file format which can be exported, loaded and unloaded by the Registry Editor in these operating systems. The following system registry files are stored in
%SystemRoot%System32Config :
The following file is stored in each user's profile folder:
For Windows 2000, Server 2003 and Windows XP, the following additional user-specific file is used for file associations and COM information:
For Windows Vista and later, the path was changed to:
Windows 2000 keeps an alternate copy of the registry hives (.ALT) and attempts to switch to it when corruption is detected.[15] Windows XP and Windows Server 2003 do not maintain a
System.alt hive because NTLDR on those versions of Windows can process the System.log file to bring up to date a System hive that has become inconsistent during a shutdown or crash. In addition, the %SystemRoot%Repair folder contains a copy of the system's registry hives that were created after installation and the first 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 next startup.[16] Internally, Registry files are split into 4 kB 'bins' that contain collections of 'cells'.[16]
You Are Reading FullMetal Alchemist in 365Manga From Viz: In an alchemical ritual gone wrong, Edward Elric lost his arm and his leg, and his brother Alphonse became nothing but a soul in a suit of armor. Equipped with mechanical 'auto-mail' limbs, Edward becomes a state alchemist, seeking the one thing that can restore his brother and himself. The legendary Philosopher's Stone. Jan 20, 2016 The brothers perform the banned alchemic technique of human transmutation in a effort to resurrect her when Trisha dies of the plague. As a result, the transmutation backfires and in law with equal exchange, the left leg and Alphonse's whole body of Edward are ruined. Alchemists are knowledgeable and naturally talented individuals who can manipulate and modify matter due to their art. Yet despite the wide range of possibilities, alchemy is not as all-powerful as most would believe. Human transmutation is strictly forbidden, and whoever attempts it risks severe consequences. Even so, siblings Edward and Alphonse Elric decide to ignore this great taboo. Fullmetal alchemist manga online.
Windows 9x[edit]
The registry files are stored in the
%WINDIR% directory under the names USER.DAT and SYSTEM.DAT with the addition of CLASSES.DAT in Windows ME. Also, each user profile (if profiles are enabled) has its own USER.DAT file which is located in the user's profile directory in %WINDIR%Profiles<Username> .
Windows 3.11[edit]
The only registry file is called
REG.DAT and it is stored in the %WINDIR% directory.
Windows 10 Mobile[edit]
Note: To access the registry files, the Phone needs to be set in a special mode using either:
If any of above Methods worked - The Device Registry Files can be found in the following location:
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 as well as individual settings for each user and application. 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.[17] When a program is removed from control panel, it is not completely removed and the user must manually check inside directories such as program files. After this, the user needs to manually remove any reference to the uninstalled program in the registry. This is usually done by using RegEdit.exe.[18] Editing the registry is sometimes necessary when working around Windows-specific issues e.g. problems when logging onto a domain can be resolved by editing the registry.[19]
Windows Registry can be edited manually using programs such as RegEdit.exe, although these tools do not expose some of the registry's metadata such as the last modified date.
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 third-party tools similar to RegEdit.exe are available for many Windows CE versions.
Registry Editor allows users to perform the following 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.g.
Microsoft.Win32.Registry
in VB.NET and C#, or TRegistry
in Delphi and Free Pascal). COM-enabled applications like Visual Basic 6 can use the WSHWScript.Shell
object. Another way is to use the Windows Resource Kit Tool, Reg.exe
by executing it from code,[24] 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),[25]Windows Powershell and Windows Scripting Host also enable registry editing from scripts.
Offline editing[edit]
The offreg.dll[26] available from the Windows Driver Kit offers a set of APIs for the creation and manipulation of currently not loaded registry hives similar 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-free 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 work. For in-process binaries such as .DLL and .OCX files, the modules typically exported a function called DllInstall()[27] that could be called by installation programs or invoked manually with utilities like Regsvr32.exe;[28] out-of-process binaries typically support the commandline arguments /Regserver and /Unregserver that created or deleted the required registry settings.[29] COM applications that break because of DLL Hell issues can commonly be repaired with RegSvr32.exe or the /RegServer switch without having to re-invoke installation programs.[30]
Advanced functionality[edit]
Windows exposes APIs that allows user-mode applications to register to receive a notification event if a particular registry key is changed.[31] APIs are also available to allow kernel-mode applications to filter and modify registry calls made by other applications.[32]
Windows also supports remote access to the registry of another computer via the
RegConnectRegistry
function[33] if the Remote Registry service is running, correctly configured and its network traffic is not firewalled.[34]Security[edit]
Each key in the registry of Windows NT versions can have 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 10 rights/permissions which can be explicitly allowed or denied to a user or a group of users.
Permission | Description |
---|---|
Query Value | The right to read the registry key value. |
Set 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 request 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 modify the container's owner. |
Read Control | The right to read the DACL. |
As with other securable objects in the operating system, individual access control entries (ACE) on the security descriptor can be explicit or inherited from a parent object.[35]
Windows Resource Protection is a feature of Windows Vista and later versions of Windows that uses security to deny Administrators and the system WRITE access to some sensitive keys to protect the integrity of the system from malware and accidental modification.[36]
Special ACEs on the security descriptor can also implement mandatory integrity control 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 account of the process 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 only modify low integrity keys.[37]
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.[38][39]
Backups and recovery[edit]
Different editions of Windows have supported a number of different methods to back up and restore the registry over the years, some of which are now deprecated:
- System Restore can back up the registry and restore it as long as Windows is bootable, or from the Windows Recovery Environment (starting with Windows Vista).
- NTBackup can back up the registry as part of the System State and restore it. Automated System Recovery in Windows XP can also restore the registry.
- On Windows NT, the Last Known Good Configuration option in startup menu relinks the
HKLMSYSTEMCurrentControlSet
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.[40] The registry checker tool backs up the registry, by default, to
%Windir%Sysbckup
Scanreg.exe can also run from MS-DOS.[41] - The Windows 95 CD-ROM included an Emergency Recovery Utility (ERU.exe) and a Configuration Backup Tool (Cfgback.exe) to back up 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.[42] - Windows 2000 Resource Kit contained an unsupported pair of utilities called Regback.exe and RegRest.exe for backup and recovery of the registry.[43]
- Periodic automatic backups of the registry are now disabled by default on Windows 10 May 2019 Update (version 1903). Microsoft recommends System Restore be used instead.[44]
Policy[edit]
Group policy[edit]
Windows 2000 and later versions of Windows use Group Policy to enforce registry settings through a registry-specific client extension in the Group Policy processing engine.[45] Policy may be applied locally to a single computer 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 4.0, administrators can use a special file to be merged into the registry, called a policy file (
POLICY.POL
). The policy file allows administrators to prevent non-administrator users from changing registry settings like, for instance, the security level of Internet Explorer and the desktop background wallpaper. The policy file is primarily used in a business 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
.POL
.The policy file filters the settings it enforces by user and by group (a 'group' is a defined set of users). To do that the policy file merges into the registry, preventing users from circumventing it by simply changing back the settings.The policy file is usually distributed through a LAN, but can be placed on the local computer.
I used to do some minor arcade repair while running a Namco arcade. This was a decade ago. Hantarex polo 25 service manual.
The policy file is created by a free tool by 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 be 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 can also change the registry on that computer.The policy editor loads the settings it 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 by allowing all the strings to be stored in one place.
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 feature called 'InifileMapping'.[46] This functionality was introduced to allow legacy applications written for 16-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 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 do not respect the principle of least privilege and instead try to write user data to a read-only system 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's invalid registry operations to a location such as a file. Used together with file virtualization, this allows applications to run on a machine without being installed on it.
Low integrity processes may also use registry virtualization. For example, Internet Explorer 7 or 8 running in 'Protected Mode' on Windows Vista and above will automatically redirect registry writes by ActiveX controls to a sandboxed location in order to frustrate some classes of security exploits.
The Application Compatibility Toolkit[47] 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 point of failure, because re-installation of the operating system was required if the registry became corrupt.[citation needed] However, Windows NT uses transaction logs to protect against corruption during updates. Current versions of Windows use two levels of log files to ensure integrity even in the case of power failure or similar catastrophic events during database updates.[48] Even in the case of a non-recoverable error, Windows can repair or re-initialize damaged registry entries during system boot.[48]
Equivalents and alternatives[edit]
In Windows, use of the registry for storing program data is a matter of developer's 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 free to use 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 plain-text files for daemon and application configuration, but group these configurations together for ease of management.
- In Unix-like operating systems (including Linux) that follow the Filesystem Hierarchy Standard, system-wide configuration files (information similar 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 (information that would be roughly equivalent to that in HKEY_CURRENT_USER) is stored in hidden directories and files (that start with a period/full stop) within the user's home directory. However XDG-compliant applications should refer to the environment variables defined in the Base Directory specification.[49] - In Mac OS X, system-wide configuration files are typically stored in the
/Library/
folder, whereas per-user configuration files are stored in the corresponding~/Library/
folder in the user's 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 thePreferences/
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 also used on the ROX Desktop for Linux.[50] This directory-based configuration also makes it possible to use different versions of the same application, since the configuration is done 'on the fly'.[51] If one wishes to remove the application, it is possible to simply delete the folder belonging to the application.[52][53] This will often not remove configuration settings which are stored independently from the application, usually within the computer's !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, e.g. when shared files are placed outside an application directory.[51]
- IBM AIX (a Unix variant) uses a registry component called Object Data Manager (ODM). The ODM is used to store information about system and device configuration. An extensive set 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 system, the Winecompatibility layer, which allows Windows software to run on a Unix-like system, also employs a Windows-like registry as text files in the WINEPREFIX folder: system.reg (HKEY_LOCAL_MACHINE), user.reg (HKEY_CURRENT_USER) and userdef.reg.[54]
See also[edit]
- LogParser â SQL-like querying of various types of log files
Notes[edit]
- ^When applications fail to execute because they request more privileges than they require (and are denied those privileges), this is known as a limited user application (LUA) bug.
Footnotes[edit]
- ^Esposito, Dino (November 2000). 'Windows 2000 Registry: Latest Features and APIs Provide the Power to Customize and Extend Your Apps'. MSDN Magazine. Microsoft. Archived from the original on 2003-04-15. Retrieved 2007-07-19.
- ^ abc'The System Registry'.
- ^'Windows 95 Architecture Components'. www.microsoft.com. Archived from the original on 2008-02-07. Retrieved 2008-04-29.
The following table shows other difficulties or limitations caused by using .INI files that are overcome by using the Registry.
- ^Raymond Chen, 'Why do registry keys have a default value?'
- ^'Designed for Windows XP Application Specification'. Microsoft. 2002-08-20. Retrieved 2009-04-08.
- ^'HKEY_LOCAL_MACHINE'. Gautam. 2009. Retrieved 2009-04-08.
- ^'Registry Keys Affected by WOW64 (Windows)'. Msdn.microsoft.com. Retrieved 2014-04-10.
- ^'Description of the Microsoft Windows registry'. Retrieved 2008-09-25.
- ^'HKEY_CURRENT_USER'. Microsoft. 2009. Retrieved 2009-04-08.
- ^'Description of the HKEY_DYN_DATA Registry Key in Windows 95, Windows 98, and Windows 98 SE'. support.microsoft.com.
- ^'A Closer Look at HKEY_DYN_DATA'. rinet.ru. Archived from the original on 2008-05-09.
- ^'Registry hives'. Retrieved 2007-07-19.
- ^Chen, Raymond (2011-08-08). 'Why is a registry file called a 'hive'?'. The Old New Thing. Retrieved 2011-07-29.
- ^'Overview of the Windows NT Registry'. Retrieved 2011-12-02.
- ^'Inside the Registry'. Retrieved 2007-12-28.
- ^ abNorris, Peter (February 2009). 'The Internal Structure of the Windows Registry'(PDF). Cranfield University. Archived from the original(PDF) on 29 May 2009.Cite journal requires
|journal=
(help) - ^'Incorrect Icons Displayed for .ico Files'. November 15, 2009. Retrieved 31 March 2012.
- ^'How to Completely Uninstall / Remove a Software Program in Windows without using 3rd Party Software? - AskVG'. www.askvg.com.
- ^'You may receive a 'STOP 0x00000035 NO_MORE_IRP_STACK_LOCATIONS' error message when you try to log on to a domain'. October 9, 2011. Retrieved 31 March 2012. This page tells the user to edit the registry when resolving the issue.
- ^key renaming is implemented as removal and add while retaining subkeys/values, as the underlying APIs do not support the rename function directly
- ^ abcd'How to add, modify, or delete registry subkeys and values by using a .reg file'. support.microsoft.com.
- ^'Applying Group Policy'. Microsoft.
- ^'Reading and Writing Registry Values with Visual Basic'. Retrieved 2007-07-19.
- ^'REG command in Windows XP'. Retrieved 2007-07-19.
- ^'registry manual page â Tcl Bundled Packages'. www.tcl.tk. Retrieved 2017-12-14.
- ^'Offline Registry Library'. Retrieved 2014-06-04.
- ^'DllInstall Function'. Microsoft. 2012-03-07. Retrieved 2012-03-22.
- ^'Regsvr32'. Microsoft. Retrieved 2012-03-22.
- ^'How to: Register Automation Servers'. Microsoft. Retrieved 2012-03-22.
- ^'How to re-register PowerPoint 2000, PowerPoint 2003, PowerPoint 2007 and PowerPoint 2010'. Microsoft. January 2012. Retrieved 2012-03-22.
- ^'RegNotifyChangeKeyValue function'. Microsoft.
- ^'Registering for Notifications'. Microsoft.
- ^'RegConnectRegistry function'. Microsoft.
- ^'How to Manage Remote Access to the Registry'. Microsoft.
- ^Gibson, Darril. 'Chapter 4: Securing Access with Permissions'. Microsoft Windows security : essentials. Indianapolis, Ind.: Wiley. ISBN978-1-118-01684-8.
- ^'Application Compatibility: Windows Resource Protection (WRP)'. Microsoft. Retrieved 8 Aug 2012.
- ^Marc Silbey, Peter Brundrett. 'Understanding and Working in Protected Mode Internet Explorer'. Retrieved 8 August 2012.
- ^'RegDelNull v1.1'. 1 November 2006. Retrieved 8 August 2012.
- ^'Unable to delete certain registry keys â Error while deleting key'. March 23, 2010. Retrieved 8 August 2012. Microsoft Support page.
- ^https://support.microsoft.com/en-us/help/183887/description-of-the-windows-registry-checker-tool-scanreg-exe
- ^https://support.microsoft.com/EN-US/help/184023
- ^'How To Backup, Edit, and Restore the Registry in Windows NT 4.0'. support.microsoft.com.
- ^'Technical Reference to the Registry: Related Resources'. Microsoft. Retrieved 2011-09-09.
- ^'Microsoft Kills Automatic Registry Backups in Windows 10'. ExtremeTech. Retrieved 2019-07-01.
- ^'How Core Group Policy Works'. Microsoft. 2 September 2009. Retrieved 13 Aug 2012.
- ^'Chapter 26 â Initialization Files and the Registry'. Microsoft. Retrieved 2008-03-03.
- ^'Microsoft Application Compatibility Toolkit 5.0'. Microsoft. Retrieved 2008-07-26.
- ^ abIonescu, Mark Russinovich, David A. Solomon, Alex. 'Registry Internals'. Windows internals (6th ed.). Redmond, Wash.: Microsoft Press. ISBN978-0-7356-4873-9.
- ^'XDG Base Directory Specification'. standards.freedesktop.org.
- ^'Application directories'. Archived from the original on 27 May 2012. Retrieved 17 May 2012.
- ^ ab'Case Studies Of The Top 132 Annoyances With Operating Systems Other Than RISC OS'. Retrieved 3 April 2012. Page from the riscos.com website. Mentioned in points 82 and 104.
- ^'RISC OS tour'. Retrieved 2007-07-19.
- ^'The RISC OS Products Directory'. 2 Nov 2006. Archived from the original on 19 February 2007. Retrieved 1 April 2012.
- ^3.2. Using the Registry and Regedit (Wine User Guide)
References[edit]
- Russinovich, Mark E.; Solomon, David A. (2005). Microsoft Windows Internals (Fourth ed.). Microsoft Press. pp. 183â236. ISBN978-0-7356-1917-3.
External links[edit]
Wikibooks has a book on the topic of: Windows registry hacks |
- Windows Registry info & reference in the MSDN Library
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Registry&oldid=916479397#HKEY_CURRENT_USER'
Comments are closed.
Author
Write something about yourself. No need to be fancy, just an overview.