Device properties registry permissions

Hello,

What are the "correct" Win7 registry permission and ownership settings for
device properties?

When I try to view device Properties keys (e.g. enum\PCI) in Regedit a popup
says: "Properties cannot be opened. An error is preventing this key from
being opened. Details: Access is denied" even though I'm a machine
administrator. When I try to view permissions a popup says: "You do not have
permission to view the current permission settings for Properties, but you
can make permissions changes." I can't even view the owner of the key. So I
can't view permissions without changing them first.

"ThomasMc07" <> wrote in message
news:89D0C559-3970-4712-AB5E-...
> Hello,
>
> What are the "correct" Win7 registry permission and ownership settings for
> device properties?
>
> When I try to view device Properties keys (e.g. enum\PCI) in Regedit a
> popup
> says: "Properties cannot be opened. An error is preventing this key from
> being opened. Details: Access is denied" even though I'm a machine
> administrator. When I try to view permissions a popup says: "You do not
> have
> permission to view the current permission settings for Properties, but you
> can make permissions changes." I can't even view the owner of the key. So
> I
> can't view permissions without changing them first.

What you see is correct. The enum tree is by default NOT accessible for
any user including administrator -
even though administrator can change permissions.

-pa

OK, how do I reset permissions after I've modified them? I don't know what
they were before I changed them.

-Thomas

"Pavel A." wrote:

> "ThomasMc07" <> wrote in message
> news:89D0C559-3970-4712-AB5E-...
> > Hello,
> >
> > What are the "correct" Win7 registry permission and ownership settings for
> > device properties?
> >
> > When I try to view device Properties keys (e.g. enum\PCI) in Regedit a
> > popup
> > says: "Properties cannot be opened. An error is preventing this key from
> > being opened. Details: Access is denied" even though I'm a machine
> > administrator. When I try to view permissions a popup says: "You do not
> > have
> > permission to view the current permission settings for Properties, but you
> > can make permissions changes." I can't even view the owner of the key. So
> > I
> > can't view permissions without changing them first.
>
> What you see is correct. The enum tree is by default NOT accessible for
> any user including administrator -
> even though administrator can change permissions.
>
> -pa
>
>
> .
>

Just leave it as is, it should work.
Restoring the permissions to original state is a bit difficult, because
there's no way
to give ownership away - you can only take it.
This is so exactly to let the original owner easily detect tampering with
security
The original owner of enum branch is not human, it won't mind.
--pa


"ThomasMc07" <> wrote in message
news:7583250D-F391-4349-A563-...
> OK, how do I reset permissions after I've modified them? I don't know what
> they were before I changed them.
>
> -Thomas
>
> "Pavel A." wrote:
>
>> "ThomasMc07" <> wrote in message
>> news:89D0C559-3970-4712-AB5E-...
>> > Hello,
>> >
>> > What are the "correct" Win7 registry permission and ownership settings
>> > for
>> > device properties?
>> >
>> > When I try to view device Properties keys (e.g. enum\PCI) in Regedit a
>> > popup
>> > says: "Properties cannot be opened. An error is preventing this key
>> > from
>> > being opened. Details: Access is denied" even though I'm a machine
>> > administrator. When I try to view permissions a popup says: "You do not
>> > have
>> > permission to view the current permission settings for Properties, but
>> > you
>> > can make permissions changes." I can't even view the owner of the key.
>> > So
>> > I
>> > can't view permissions without changing them first.
>>
>> What you see is correct. The enum tree is by default NOT accessible for
>> any user including administrator -
>> even though administrator can change permissions.
>>
>> -pa
>>
>>
>> .
>>

I see. On my Win7 x64 development machine, owner of the enum branch shows as
the machine adminstrators group, it's just the various properties branches
that have the mystery owner. Just as a point of curiosity, is it supposed to
be Local System (S-1-5-18)?

"Pavel A." wrote:

> Just leave it as is, it should work.
> Restoring the permissions to original state is a bit difficult, because
> there's no way
> to give ownership away - you can only take it.
> This is so exactly to let the original owner easily detect tampering with
> security
> The original owner of enum branch is not human, it won't mind.
> --pa
>
>
> "ThomasMc07" <> wrote in message
> news:7583250D-F391-4349-A563-...
> > OK, how do I reset permissions after I've modified them? I don't know what
> > they were before I changed them.
> >
> > -Thomas
> >
> > "Pavel A." wrote:
> >
> >> "ThomasMc07" <> wrote in message
> >> news:89D0C559-3970-4712-AB5E-...
> >> > Hello,
> >> >
> >> > What are the "correct" Win7 registry permission and ownership settings
> >> > for
> >> > device properties?
> >> >
> >> > When I try to view device Properties keys (e.g. enum\PCI) in Regedit a
> >> > popup
> >> > says: "Properties cannot be opened. An error is preventing this key
> >> > from
> >> > being opened. Details: Access is denied" even though I'm a machine
> >> > administrator. When I try to view permissions a popup says: "You do not
> >> > have
> >> > permission to view the current permission settings for Properties, but
> >> > you
> >> > can make permissions changes." I can't even view the owner of the key.
> >> > So
> >> > I
> >> > can't view permissions without changing them first.
> >>
> >> What you see is correct. The enum tree is by default NOT accessible for
> >> any user including administrator -
> >> even though administrator can change permissions.
> >>
> >> -pa
> >>
> >>
> >> .
> >>
> .
>

ThomasMc07 <> wrote:
>
>I see. On my Win7 x64 development machine, owner of the enum branch shows
>as the machine adminstrators group, it's just the various properties
>branches that have the mystery owner. Just as a point of curiosity, is
>it supposed to be Local System (S-1-5-18)?

Yes.
--
Tim Roberts,
Providenza & Boekelheide, Inc.