-=PCTechTalk=- Re: Reg key access denied
- From: GuitarMan <gman.pctt@xxxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Sat, 7 Jul 2007 16:12:16 -0400
Doc,
The ability for keys to be 'locked' like this can only occur under NTFS.
Fat, Fat16 & Fat32 formatting doesn't support this feature. It's great to
be able to 'lock' a key so the kids (home system) or general public (kiosks)
can't mess up a system set up specifically for them. Unfortunately,
software companies have discovered that they can use it to their advantage
as well (although I'll never understand the advantage of putting you through
what you just went through).
Still, Give some props to John for bringing up the Safe Mode idea.
That's what reminded me that the Policy Editor can capture keys as well.
:O)
Peace,
GMan
"The only dumb questions are the ones that are never asked!"
----- Original Message -----
From: "Dr. Benway" <benwaydr@xxxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Saturday, July 07, 2007 3:36 PM
Subject: -=PCTechTalk=- Re: Reg key access denied
> Thanks gman,
>
> I found the little rodent with your help. Yet another
> thing I did not know. I had no idea that registry keys
> could have access rights defined and that they could
> be defined by a software install without my knowledge.
> This came about by an attempt to get data from an old
> app that ran under Access 97. Acch!!! May Linux and
> Open Source live long and prosper.
>
>
> --- GuitarMan <gman.pctt@xxxxxxxxx> wrote:
>
>> Doc B,
>> While "Move on Boot" won't help a registry
>> entry, Safe mode may allow
>> you to remove the offending key. Of course, all
>> Registry editing cautions
>> apply here (Backup the registry first, don't remove
>> anything you're not
>> absolutely sure of, reboot when you're finished,
>> etc.).
>>
>> If it doesn't delete in Safe Mode, you may have
>> a security policy in
>> place preventing its removal. In this case, you'll
>> need to boot normally
>> and then invoke the Policy Editor and hunt
>> for/change the 'rule' that
>> governs that entry. Unfortunately, there's not much
>> I can do to help direct
>> you to the proper location for this control (perhaps
>> try searching for that
>> specific registry string and see if anyone else has
>> encountered this and
>> posted how they fixed it). Policy editing cautions
>> need to be in effect
>> here, as well. Don't change anything unless you're
>> absolutely sure that you
>> have found the correct entry/control you wish to
>> modify. You should also
>> write down the path to that particular entry so you
>> can change it back if it
>> doesn't perform as expected.
>>
>> To access the Policy Editor, go to Start > Run,
>> type in the following
>> and press Enter.
>>
>> secpol.msc
>>
>> Good Hunting! :O)
>>
>> Peace,
>> GMan
--
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To unsubscribe or change your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
Other related posts:
