Cannot load key into regedt32

[Knack]

Keep getting the error
"Insufficient privelege to load the key."

Yet in the key that I'm loading within I've not only added Administrators as
having full contro, but have also checked "Replace existing privileges on
all existing subkeys."

Anyone know how to get around this?

 

[Mark V]

Keep getting the error
"Insufficient privelege to load the key."

Yet in the key that I'm loading within I've not only added
Administrators as having full contro, but have also checked
"Replace existing privileges on all existing subkeys."

Anyone know how to get around this?

Path to key would help.

 

[Mark V]

Keep getting the error
"Insufficient privelege to load the key."

Yet in the key that I'm loading within I've not only added
Administrators as having full contro, but have also checked
"Replace existing privileges on all existing subkeys."

Anyone know how to get around this?

Path to key would help.

 

[Knack]

Path to key would help.

HKLM\SYSTEM\CurrentControlSet\Enum\Root

I've also tried and failed in the subkey
HKLM\SYSTEM\ControlSet001\Enum\Root
which happens to be the control set that CurrentControlSet refers to

After replacing the LEGACY_DHCP subkey in that one, I plan to also replace
other subkeys within the the following other subkeys:

HKLM\System\CurrentControlSet\Services
HKLM\System\CurrentControlSet\Services\FA3105\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NDISLoop4\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NdisWAN3\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NetBT\Parameters

DHCP client is definitely corrupted on this computer so I'm replacing only
the subkeys pertaining to DHCP with those of a known good system hive that
was backed up in the recent past.

 

[Knack]

Path to key would help.

HKLM\SYSTEM\CurrentControlSet\Enum\Root

I've also tried and failed in the subkey
HKLM\SYSTEM\ControlSet001\Enum\Root
which happens to be the control set that CurrentControlSet refers to

After replacing the LEGACY_DHCP subkey in that one, I plan to also replace
other subkeys within the the following other subkeys:

HKLM\System\CurrentControlSet\Services
HKLM\System\CurrentControlSet\Services\FA3105\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NDISLoop4\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NdisWAN3\Parameters\Tcpip
HKLM\System\CurrentControlSet\Services\NetBT\Parameters

DHCP client is definitely corrupted on this computer so I'm replacing only
the subkeys pertaining to DHCP with those of a known good system hive that
was backed up in the recent past.

 

[Matthew Mucker [MSFT]]

You must have the SE_RESTORE_NAME privilege (right).

Privileges (rights) are different from permissions.

Essentially (assuming you haven't changed things around), that means you
must be an administrator on the machine.

-Matt

 

[Matthew Mucker [MSFT]]

You must have the SE_RESTORE_NAME privilege (right).

Privileges (rights) are different from permissions.

Essentially (assuming you haven't changed things around), that means you
must be an administrator on the machine.

-Matt

 

[Knack]

I don't know VBS, and even if someone were to provide me with a script for
doing whatever needs to be changed, I don't have VB loaded on the machine.

 

[Knack]

I don't know VBS, and even if someone were to provide me with a script for
doing whatever needs to be changed, I don't have VB loaded on the machine.

 

[Dave Patrick]

From the resource kit:
Do not attempt to change the permissions on the Enum subkey. If you do, you
might damage the sequence of inherited permissions in the registry. If you
change the content of the Enum subkey, you can damage the Plug and Play
functions of Windows 2000 and prevent devices from operating. If you must
gain access to the Enum subkey, contact Microsoft Product Support Services.

To display hidden devices, non-Plug and Play devices, and devices not
attached to the computer (commonly known as "ghosted" or "phantom" devices),
type
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
at the command line. Then, use Device Manager to remove or reconfigure these
devices. Do not edit the registry.

That said you'll need to take ownership of the subkey to access.

 

[Dave Patrick]

From the resource kit:
Do not attempt to change the permissions on the Enum subkey. If you do, you
might damage the sequence of inherited permissions in the registry. If you
change the content of the Enum subkey, you can damage the Plug and Play
functions of Windows 2000 and prevent devices from operating. If you must
gain access to the Enum subkey, contact Microsoft Product Support Services.

To display hidden devices, non-Plug and Play devices, and devices not
attached to the computer (commonly known as "ghosted" or "phantom" devices),
type
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
at the command line. Then, use Device Manager to remove or reconfigure these
devices. Do not edit the registry.

That said you'll need to take ownership of the subkey to access.

 

[Knack]

I *am* Administrator. Don't understand why I don't have the necessary
privileges. Have been Admin on a few NTW PCs since v 3.51 way back in autumn
'96 and have never even heard of privileges before; perhaps because I've
never been denied anything on account of them before.

 

[Knack]

I *am* Administrator. Don't understand why I don't have the necessary
privileges. Have been Admin on a few NTW PCs since v 3.51 way back in autumn
'96 and have never even heard of privileges before; perhaps because I've
never been denied anything on account of them before.

 

[Mark V]

HKLM\SYSTEM\CurrentControlSet\Enum\Root

I've also tried and failed in the subkey
HKLM\SYSTEM\ControlSet001\Enum\Root
which happens to be the control set that CurrentControlSet refers
to

That was my guess.
Don't mess with ENUM since the source of those is determined during
system startup. You need to change/remove somewhere else and the
ENUM will folow after a reboot.

See also post by Dave P.

 

[Mark V]

HKLM\SYSTEM\CurrentControlSet\Enum\Root

I've also tried and failed in the subkey
HKLM\SYSTEM\ControlSet001\Enum\Root
which happens to be the control set that CurrentControlSet refers
to

That was my guess.
Don't mess with ENUM since the source of those is determined during
system startup. You need to change/remove somewhere else and the
ENUM will folow after a reboot.

See also post by Dave P.

 

[Mark V]

From the resource kit:
Do not attempt to change the permissions on the Enum subkey. If
you do, you might damage the sequence of inherited permissions in
the registry. If you change the content of the Enum subkey, you
can damage the Plug and Play functions of Windows 2000 and prevent
devices from operating. If you must gain access to the Enum
subkey, contact Microsoft Product Support Services.

To display hidden devices, non-Plug and Play devices, and devices
not attached to the computer (commonly known as "ghosted" or
"phantom" devices), type
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
at the command line. Then, use Device Manager to remove or
reconfigure these devices. Do not edit the registry.

Dave, unless I am mistaken you left out the part about
from the *same* window in which you issued the SET command, start
the Device Manager using devmgmt.msc

(Or set that variable persistently and globally for future use after
a reboot)

 

[Mark V]

From the resource kit:
Do not attempt to change the permissions on the Enum subkey. If
you do, you might damage the sequence of inherited permissions in
the registry. If you change the content of the Enum subkey, you
can damage the Plug and Play functions of Windows 2000 and prevent
devices from operating. If you must gain access to the Enum
subkey, contact Microsoft Product Support Services.

To display hidden devices, non-Plug and Play devices, and devices
not attached to the computer (commonly known as "ghosted" or
"phantom" devices), type
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
at the command line. Then, use Device Manager to remove or
reconfigure these devices. Do not edit the registry.

Dave, unless I am mistaken you left out the part about
from the *same* window in which you issued the SET command, start
the Device Manager using devmgmt.msc

(Or set that variable persistently and globally for future use after
a reboot)

 

[Mark V]

I *am* Administrator. Don't understand why I don't have the
necessary privileges. Have been Admin on a few NTW PCs since v
3.51 way back in autumn '96 and have never even heard of
privileges before; perhaps because I've never been denied anything
on account of them before.

There are places on disk and in the registry where being a member of
the local Administrators group is not sufficient for Full access.
This is by design. In some cases adding a NT RIGHT to your account
will suffice and in others it is a question of ACLs set by default by
the OS. All this is by design for security and to prevent users
(even Admins) from doing things that could damage the installation.

See other posts in this thread and use the available techniques to
accomplish your goal without bypassing the safety mechanisms of the
OS.

 

[Mark V]

I *am* Administrator. Don't understand why I don't have the
necessary privileges. Have been Admin on a few NTW PCs since v
3.51 way back in autumn '96 and have never even heard of
privileges before; perhaps because I've never been denied anything
on account of them before.

There are places on disk and in the registry where being a member of
the local Administrators group is not sufficient for Full access.
This is by design. In some cases adding a NT RIGHT to your account
will suffice and in others it is a question of ACLs set by default by
the OS. All this is by design for security and to prevent users
(even Admins) from doing things that could damage the installation.

See other posts in this thread and use the available techniques to
accomplish your goal without bypassing the safety mechanisms of the
OS.

 

[Matthew Mucker [MSFT]]

Can you please explain to us in detail what you're trying to do?

There is no "load key" command in regedt32. My comments apply to the "load
hive" command, which seems to be different than what you're trying to do.

As others have mentioned, you should not overwrite the ENUM key. This is
dynamic data that the OS manages.

-Matt