Taking ownership of windowsapps folder - failed to process?

So ive taken ownership without much of an issue on two of my pc's. my 3rd is fighting me tooth n nail. When i go to take ownership, it fails to process some stuff.

I know when this happened on one of the other pc's, instead of the context menu item to take ownership, I had to use the command line and

Code:

takeown /f <folder> /r

after that the context menu processed everything (i imagine because the former already took care of that, but posterity :P)

This isnt the case on my final pc. ive used the context menu method. ive used the cmd line method above. its still failing on some files.

how to i rectify that?

Some folders are protected and owned by system as making any changes in those folders can screw up the system and most likley folders that virus would try and infect

must be something added with 20H1 then or something, as both my 1909 machines have no problem processing every solitary folder and file in WindowsApps.

hrm. If that is in fact the case - im fine with it. I'm more alarmed by the discrepancy and what caused it than the fact i cant actually process 8 files.

I try to keep 100% parity between my machines and that one being an outlier frustrated me enough to inquire in case someone knew why and/or had a means i could use of brute forcing it :P

i actually think most are owned by system before the taking over begins

The one in program files, i havent dug far enough to find out which files specifically8 are hanging it up. Out of ~30,000 its not processing 8. Problem is all the other pc's process all with 0 failed so it irks me :P

normally i dont take ownership of anything as its bitten me waaaay in the past, but with windowsapps i needed to get inside to steal an icon for a shortcut and thats was the quick n dirty. ever since then ive been doing it more or less to keep my pc's on an even keel with one another.

it can certainly prevent apps from working if done incorrectly - but the standard take ownership context entry you get from here, or from winaero tweaker has never done me wrong. (outside of whatevers going on with these files)

even in days gone by, when it did happen (an app breaks due to getting too crazy with permissions stuff) a reinstall of said app, or waiting for a windows update always buttoned it back up. or if you keep backups theres always that.

whats scary is the extensive registry key ownership saga im about to partake because microsoft in their infinite wisdom has locked down the userchoice key for file extensions tighter than <insert analogy here>

thats another topic for another post though :P