LEGACY registry keys

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In (our) Windows 2000 Server registry, there are a great
number of keys that begin with the word 'LEGACY'. For
example:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
\Enum\Root\LEGACY_DFS
(or ... DMLOAD or ... FIPS or ... CQMGHOST or ... - where
each of these is the final qualifier, in place of 'DFS' in
the first key noted).

The above sample purposefully references keys from many
different programs to demonstrate the scope of 'LEGACY'
keyset. I can recognize many of the keys for what they
represent, but have no context for the 'LEGACY'
designation. Also, these keys, though they appear to be
entirely superfluous, cannot be deleted.

Any feedback anyone?

/.dz
 
In said:
In (our) Windows 2000 Server registry, there are a great
number of keys that begin with the word 'LEGACY'. For
example:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
\Enum\Root\LEGACY_DFS
(or ... DMLOAD or ... FIPS or ... CQMGHOST or ... - where
each of these is the final qualifier, in place of 'DFS' in
the first key noted).

The above sample purposefully references keys from many
different programs to demonstrate the scope of 'LEGACY'
keyset. I can recognize many of the keys for what they
represent, but have no context for the 'LEGACY'
designation. Also, these keys, though they appear to be
entirely superfluous, cannot be deleted.

Any feedback anyone?
Click to expand...

They relate to installed drivers or services in the ...\CCS\Services
\ key.
"FIPS" for example.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fips
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fips\Enum
"0"="Root\LEGACY_FIPS\0000"

Some come in the OS. Some are for installed drivers/services.
CurrentControlSet is the only one to be concerned with in most cases.

They just exist and are required so long as the actual service or
driver is installed. Do not try to delete them.
In a rare case they might require deletion after and un-install if
and only if they same program cannot be re-installed because it's own
"ENUM, LEGACY" key exists. Ususally at a vendor's specific
direction. Regedt32.exe will allow you change the Permissions (ACLs)
on a key, but don't do it execpt to delete it and only if required.
Changing registry permissions in the "ENUM" keys can really hose
things.
 
In said:
In (our) Windows 2000 Server registry, there are a great
number of keys that begin with the word 'LEGACY'. For
example:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
\Enum\Root\LEGACY_DFS
(or ... DMLOAD or ... FIPS or ... CQMGHOST or ... - where
each of these is the final qualifier, in place of 'DFS' in
the first key noted).

The above sample purposefully references keys from many
different programs to demonstrate the scope of 'LEGACY'
keyset. I can recognize many of the keys for what they
represent, but have no context for the 'LEGACY'
designation. Also, these keys, though they appear to be
entirely superfluous, cannot be deleted.

Any feedback anyone?
Click to expand...

They relate to installed drivers or services in the ...\CCS\Services
\ key.
"FIPS" for example.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fips
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fips\Enum
"0"="Root\LEGACY_FIPS\0000"

Some come in the OS. Some are for installed drivers/services.
CurrentControlSet is the only one to be concerned with in most cases.

They just exist and are required so long as the actual service or
driver is installed. Do not try to delete them.
In a rare case they might require deletion after and un-install if
and only if they same program cannot be re-installed because it's own
"ENUM, LEGACY" key exists. Ususally at a vendor's specific
direction. Regedt32.exe will allow you change the Permissions (ACLs)
on a key, but don't do it execpt to delete it and only if required.
Changing registry permissions in the "ENUM" keys can really hose
things.
 
Thank you for the info. I'm just trying to understand the
architecture of the registry (in my spare time so to
speak); but there was some overlap with a more 'real'
situation in which some previously installed s/w was
questinably de-installed. Although I still don't have a
great deal of comfort in the registry, every little bit
helps.

/.dz
 
Thank you for the info. I'm just trying to understand the
architecture of the registry (in my spare time so to
speak); but there was some overlap with a more 'real'
situation in which some previously installed s/w was
questinably de-installed. Although I still don't have a
great deal of comfort in the registry, every little bit
helps.

/.dz
 
Back
Top