Windows Registry: Difference between revisions

From Computers Wiki
Jump to navigationJump to search
(→‎Native .REG file format: Clarify root ntoe)
(→‎REGEDT16.EXE: Add another note)
Line 28: Line 28:
*<code>REG16X2.E<em>nn</em></code> for 00-99 are created next to the file for each installation and uninstallation attempt.
*<code>REG16X2.E<em>nn</em></code> for 00-99 are created next to the file for each installation and uninstallation attempt.
*The program starts significantly more quickly than <code>REGEDIT.EXE /V</code>.
*The program starts significantly more quickly than <code>REGEDIT.EXE /V</code>.
*<code>%WINDIR%\SYSTEM\REGDATA</code> also gets created with a bunch of <code>.BIN</code> files. They are full of strings about certificate authorities. Microsoft states this directory is used for Terminal Server licensing, but the timestamps of the files show that they were created with the IE5 installation.<ref>https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/terminal-server-licensing</ref>


=== Native <code>.REG</code> file format ===
=== Native <code>.REG</code> file format ===

Revision as of 16:08, 30 October 2023

The Windows Registry is a unnecessarily nested key-value store.

Windows for Workgroups 3.11

The following things were noticed after installing the 16-bit version of Internet Explorer 5.01.

REGEDIT.EXE

This one is bundled with the operating system. Run it with the /v flag to make it actually usable.

  • It only sees the type registrations (HKEY_CLASSES_ROOT in REGEDT16.EXE).
  • In verbose mode, spaces in keys are replaced with #.
  • There is only one value per key ((Default) in REGEDT16.EXE), and it is always a string.
  • A "Revert to Last Save" menu item exists.
  • Data is stored in %WINDIR%\REG.DAT.[1]
  • Separate REGEDIT.HLP and REGEDITV.HLP files exist. The latter is used for the Help menu when running in verbose mode.
  • Verbose mode takes significantly longer to start than standard mode.

REGEDT16.EXE

This one comes with the 16-bit version of Internet Explorer 5.01.

  • This gets dumped into %WINDIR%\SYSTEM unlike the native REGEDIT.EXE
  • The About dialog states this is for both Windows 3.1 and Windows NT 3.51.
  • HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE are present too.
  • String, Binary, and DWORD are the only types.
  • Data is stored in %WINDIR%\REG16X2.DAT.[2]
  • REG16X2.Enn for 00-99 are created next to the file for each installation and uninstallation attempt.
  • The program starts significantly more quickly than REGEDIT.EXE /V.
  • %WINDIR%\SYSTEM\REGDATA also gets created with a bunch of .BIN files. They are full of strings about certificate authorities. Microsoft states this directory is used for Terminal Server licensing, but the timestamps of the files show that they were created with the IE5 installation.[3]

Native .REG file format

This section details the native format understood by Windows 3.1. 16-bit Internet Explorer 5.01 and the like instead use the newer REGEDIT4 format.

  • The first line is REGEDIT with no version afterwards. Contrast this with REGEDIT4 and Windows Registry Editor Version 5.00 present in later versions.
  • HKEY_CLASSES_ROOT is explicitly prepended to every key. Contrast this with REGEDIT.EXE /V strongly implying that the root is \ instead.
  • Every processed line has the format HKEY_CLASSES_ROOT\path\to\key = Value of key.
  • Lines that do not start with HKEY_CLASSES_ROOT are ignored; no special character is needed to start a comment.[4]
  • If the  =  and value are omitted, the key is created without a value.
  • Escape sequences are not understood.

KB articles

References