Registry error, cannot be opened

While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter?

But i'm curious, is this the sort of key Registry cleaners would delete?

On 08/04/2017 11:48 AM, micky wrote:
7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened.



If your machine is running OK I'd leave it alone.

More than likely you will ruin something

On Fri, 04 Aug 2017 12:48:09 -0400, micky
wrote:

While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter?

But i'm curious, is this the sort of key Registry cleaners would delete?



I don't know, but stay away from registry cleaners.

micky wrote:
While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter?

But i'm curious, is this the sort of key Registry cleaners would delete?

The key in question is owned by SYSTEM. This article uses Sysinternals
psexec to give access (it runs Regedit using the SYSTEM account, so the
actual owner of the key is in charge). The other account of
interest is TrustedInstaller. But SYSTEM is usually good enough
for hammering pesky keys. Don't let the details get in the
way of a good time...

https://www.tenforums.com/windows-up...n-offline.html

Paul

Ken Blake wrote:

micky wrote:

While going up a line at a time in the registry, I got this
{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Probably owned exclusively by TrustedInstaller

There are ways and means to alter permissions, but I wouldn't without
good reason.

But i'm curious, is this the sort of key Registry cleaners would delete?

stay away from registry cleaners.

+1

micky wrote:

While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter?

But i'm curious, is this the sort of key Registry cleaners would delete?

You don't have permissions on the registry key. Registry entries have
permissions just like files (under NTFS) have permissions.

A registry cleaner runs under your Windows account so it gets the same
permissions. Even if you log under an admin-level Windows account,
administrators do not always get permissions to files or registry
entries. You have to go into permissions, make yourself the owner, and
then change permissions as you want. You better know what your doing.

In alt.comp.os.windows-10, on Fri, 4 Aug 2017 14:26:08 -0500, VanguardLH
wrote:

micky wrote:

While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter?

But i'm curious, is this the sort of key Registry cleaners would delete?

You don't have permissions on the registry key. Registry entries have
permissions just like files (under NTFS) have permissions.

A registry cleaner runs under your Windows account so it gets the same
permissions. Even if you log under an admin-level Windows account,
administrators do not always get permissions to files or registry
entries. You have to go into permissions, make yourself the owner, and
then change permissions as you want. You better know what your doing.

Thanks all. I promise, no registry cleaning. (Just curious.)

micky wrote:

VanguardLH wrote:

micky wrote:

While going up a line at a time in the registry, I got this

{7746D80F-97ED-4E26-9543-26B41FC22F79} cannot be opened. An error is
preventing this key from being opened. Details: access is denied.

Apparently this error doesn't really matter? But i'm curious, is
this the sort of key Registry cleaners would delete?

You don't have permissions on the registry key. Registry entries have
permissions just like files (under NTFS) have permissions.

A registry cleaner runs under your Windows account so it gets the same
permissions. Even if you log under an admin-level Windows account,
administrators do not always get permissions to files or registry
entries. You have to go into permissions, make yourself the owner, and
then change permissions as you want. You better know what your doing.

Thanks all. I promise, no registry cleaning. (Just curious.)

The other problem is that often you cannot recurse the permission
changes into the subkeys. You don't have permission on them although
you gave permission to the parent. You have to change ownership and
permission on the parent, F5 to refresh the registry (which may show up
new subkeys you didn't see before because you didn't have read
permission), select the subkey (get the permission error prompt), and
repeat the ownership and permissions changes, and repeat many times
until you get down to the last subkey. If there is more than one branch
under a key, you then have to repeat the same procedure on that branch,
and for every other branch and sub-branch. Eventually you get ownership
and permissions configured on all subkeys in all branches so you can
finally delete the parent key.

I remember having to do this on some ENUM (enumerator) keys for USB
entries. Took around 1 hour to do each branch under a USB enum key
before I could delete that USB enum key, then had to repeat for the
other USB enumerations for the same device when it had been plugged into
other USB ports. It was hours before I eradicated all registry entries
for that USB device.

Registry cleaners (and only those that show their proposed changes
before making them) are okay *if* the user is expert in editing the
registry. The cleaner is used as a quick check to identify what might
get changed or deleted but the *user* is still the admin with the
responsibilities in making the decisions of what to change by the tool.
Blind cleanup is done by boobs who then later wonder why some features
or programs no longer function or why new problems cropped up.

Many users claim that cleaning the registry will reduce its memory
consumption. Yes, by maybe a real huge total of ... wait for it ...
maybe 100 MB. Some users claim Windows will load faster because it
takes less time to load the registry files into memory. Yes, by maybe
17 ms, and that's an exaggeration, which is done in parallel with other
startup tasks so the user won't notice a difference in load time.

Many users claim that there are orphans in the registry that need to be
eradicated. Orphans are just that: orphans. Being an orphan means the
registry key and its data items will never be accessed (read or
written). There is no speed loss in having orphans in the registry
because, well, remember your system RAM is Random Access Memory: takes
as long to read one block as for another. Orphans do not block or slow
down access to other registry entries in RAM.

Other than the want to cleanup, the only time a registry cleaner will
help to fix anything is when there are non-orphaned entries in the
registry, like for shell objects, that cause problems because their
target handler no longer exists. The cleaner will trace dependencies
and find an entry is missing its handler.

Alas, be aware that some of those type of registry entries (handler is
missing) are deliberately added by some software, like anti-virus
software, to provide for handling in their sandbox. They are entries
for use at some later time. The user or the cleaner they use might
delete those entries but the AV program will just restore them.

CCleaner tries to do safe registry cleanup. That means it doesn't delve
very deep in tracing interdependencies the result of which is that there
will still be some superfluous registry entries after using Ccleaner.
Revo Uninstaller uses a database to define to it what to remove (and an
install monitor in the payware version to record the install-time
changes -- which may NOT be all due to the installer). The simple
cleanup of Revo Uninstaller that uses its database is a relatively safe
cleaner. It's when you use its more aggressive cleanup modes that you
can screw over your system. Just like with other cleanup tool, the
ultimate responsibility is with you. Revo's aggressive cleanup requires
you review the proposed changes and authorize them or edit the log to
remove entries that should not be changed or removed.

Alas, registry cleaners are typically used more often by ignorants that
let the tool do whatever it wants rather than registry-editing
experienced users that use the tool as a quick reference to have the
*USER* decide what to do. When using a registry cleaner, the user is
still responsible for all changes the tool makes. Blaming the tool
shows an ignorant used it.

In alt.comp.os.windows-10, on Fri, 4 Aug 2017 18:36:02 -0500, VanguardLH
wrote:

Important stuff snipped.


Alas, registry cleaners are typically used more often by ignorants that
let the tool do whatever it wants rather than registry-editing
experienced users that use the tool as a quick reference to have the
*USER* decide what to do. When using a registry cleaner, the user is
still responsible for all changes the tool makes. Blaming the tool
shows an ignorant used it.

I had a friend who bought a new (to them) house from an old couple, and
maybe that's why he had a need to clean it up, but I learned that soon
after, he found on top of a closet some wiring etc. with no clear
purpose so he removed it.

Later he gradually figured out that the double floodlights on all four
corners of the house were connected to a switch in the closet and there
was also a remote that could turn the lights on from the car. It's a
pretty safe n'hood but wives especially worry about such things. I
bought some kind of universal receiver and it burned up within a few
seconds (even though the circuit just controlled a relay in the
basement.) The vendor gave me a second one for free but that failed
right away too. So I bought something bigger at sears, for garage door
openers, and when I left his house, I had tried the remote and it worked
10 times over 10 minutes from up to 100 feet from his front door.(when
30 feet was enough)

When I didnt' hear how his wife liked it, I finally asked and it was
like a white house press conference. I don't know what the answer was,
but I guess my thing isn't working anymore. I'm curious but I don't
know why.