Office 16 Click-to-Run Extensibility Component could not modify 137 protected registry keys during installation or update of Office 365

To readers - I have a clue how to a fix, but need your suggestions.  I am now looking for "Scrub" that will truly UNinstall Office and O365 from my PC, including the registry keys that cannot be modified during the REinstall process.  A MS tech suggested this "Scrub" but only if he runs it on my machine - not something he'll send me.

Do you know what he means?  Do you believe what he tells me, that it will actually delete those 60 - 70 non-modifiable registry keys?  Where can I get this on my own (or at least research it before he wrecks my PC and kills two of my work days)? 

After the call with the tech, I found something on the web about "Offscrub", and it might be helpful.  It also might be very helpful when you are UNinstalling Office.  Go to the following great article and then please come back here to comment:

https://www.deploymentmadscientist.com/2016/02/08/deploying-microsoft-office-2016-removing-old-versions/

After you read the above, here are my questions:

If I open cmd as administrator, what would be the single command line (from that article) to run either O15CTRRemove.diagcab (easier for me) or offscrub?.vbs (more work for me) in the strongest flavor?  (I assume I would first have to create the CScriptNative.cmd described in that article.)

I am hoping this approach will delete those 60 - 70 registry keys as well, so I can then do a REinstall without the Warnings.

(By the way, before I got to the article above, the MS office tech called me this morning.  His first recommendation was to Repair or Reset my operating system, Win 7 Pro 64-bit.  Instead of telling him what I thought about that (and him), I bit my tongue and asked him (a) whether he'd read my txt files with copies of the Event Viewer Warnings and (b) whether an OS Repair or Reset would focus on those keys.  I continued to ask questions, and he eventually mentioned "Scrub" as the answer, which later inspired me to the link above.  Anyway, I asked him to call me back in two weeks when I would have time to do this, and he promised to do so.   I don't trust this guy's knowledge, and I would prefer to find a more reliable solution.)

Thanks, and I hope you all find this link helpful.

More info:

I went to one of the registry keys in the Warnings and found that its Permissions are Read Only and its Owner is TrustedInstaller.

There are way too many of these keys for me to try to change Owner and Permissions (and then change Owner back).

What is MS doing if its own installation program doesn't deal with this?

Still not answered.

StanySteve - thanks for interesting links.  You found stuff I couldn't.

However, FYI, I have installed O365 only on my Win 7 Pro 64-bit, not my Win 10 Pro 64-bit.

Your links are interesting, esp. the lennytech, but I have NOT had the worse app-crash issues described in those links.  As far as I can tell, my Office 365 Home (which gave me Office 16) is working.  But I certainly don't like the numerous Warnings in Event Viewer I describe above.

What's interesting about the lennytech is that when I first installed the O365 with the help of the MS call-in team, the MS tech installed the 32-bit version of O365.  I asked him to uninstall and re-install the 64-bit version, and he did.  Maybe that first install set up those registry keys and locked them somehow.  They have apparently remained locked even though I ran the DEEP O365 uninstall twice. 

Not yet ready to try the regedit and uninstall surgery described at lennytech.  But it might be an experiment next weekend if no luck elsewhere.

Please do comment more if anything occurs.

And I hope others comment also!

Thanks.

It seems this might be a problem associated with Windows 10. This website might offer some solutions.

http://answers.microsoft.com/en-us/o...99e1e43?page=1

 Some info here as well:

https://lennytech.wordpress.com/2013...ity-component/