Windows 10: unable to take ownership of registry keys in Current_User - Win 10

Got a fun little problem that I can't wrap my head around...

Using Regedit to expand the allowed size of outlook .ost folders, but ended up having to create some sub keys because they did not exist yet to put the D_word entries in

However, when I try to create new keys under HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft I get the following:




Usually I would just take ownership of the parent key in the Advanced Security settings at this point, but when I try to do that it won't allow me to change the owner, even after supplying admin credentials as needed:




Running Regedit as the admin doesn't help, as I specifically need the current user keys... and I can't figure out what is blocking me from taking ownershp currently SYSTEM. I've never had this issue before, having done the same entry edits on dozens of other workstations in the last ocuple of years... help?


the goal is to create two D_word entries under KEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\PST

:)

 

Take Ownership and Delete Registry Key

I have a brand new PC with a brand new clean install of Windows 10 with most current build.

Despite this, I am continually seeing a Warning Event ID 1534:

Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details.

If the Events Viewer. Perhaps this is an inconsequential Warning and can be ignored, but the supposed process for resolving it has triggered the fundamental question. How to take ownership of a registry key?

If found on line with several people confirming the fix that the process is (or should be) simple:

Open the registry, navigate to, export, delete the following two keys then reboot:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileNotification\TDL

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsNT\CurrentVersion\ProfileNotification\TDL

Unfortunately there is a caveat: "You'll need to take ownership of the TDL key to be able to delete it."

Well despite following to the letter no less than 3 articles for "Taking ownership of a registry" key, after following those steps and clicking "Apply" I keep getting a Windows Security popup:

Unable to save permission changes on TDL. Access is denied.

It is almost infuriating. I'm, I can take a sledge hammer to this PC and smash it to pieces, but Windows wants to tell me that as both the owner and administrator, that I can't have access to and delete a file.

It must be possible, as several people have apparently done it and resolved this warning.

Appreciate any guidance a more experienced person may provide.

 

Take Ownership and Delete Registry Key

Sarah,

Thanks for the reply and thanks for suggestions. However, you haven't answered the question asked :-(. The issue that I am having with my computer is "Ownership." I am the administrator and supposedly the owner but Windows thinks that it is :-(.

It has taken days to set up the PC like I want it to look and feel. I certainly don't want to create another local administrator account and go through that ringer again.

At this point, the Warning and Event ID 1534 is a point of principle. I don't want to ignore it. I want to fix it. According to information posted and confirmed by several others, the way to do this is to take ownership and delete two registry keys.
If the whole computer blows up as a result that is fine.

How do I "Take ownership" of this TLD key and delete it?

 

Unable to delete Bluetooth driver related Registry Keys

Hello,

I've been unable to use Bluetooth related services since the upgrade to the Creators Update(1703). The device manger returns a Code19 error saying "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged". I've since tried various workarounds but have had no luck so far. So, I'm hoping a complete reset of anything Bluetooth related in the registry will fix the issue.

As suggested here I've manged to delete all the relevant keys except for one particular key named BTHENUM. As you can see in the screenshot attached, the key contains a number of subkeys. Even more show up upon taking ownership of 'properties'. Since there are close to a hundred keys (maybe more), I've tried using the command line tool (subInacl.exe) to take ownership/make necessary changes to the keys but the command fails with some keys working and the rest not. The only way out for now is to take ownership/delete individually which is a nightmare.

I would like to know if there's a quicker way to get this done other than a clean install.

Note: I've tried deleting the keys in safe mode and via the built-in administrator account without success. I've also uninstalled all hidden BT drivers from Device Manager.


Any advice is appreciated.

Thanks