I don't mind a challenge myself but as long as I know why I am taking on the challenge.
I have installed the operating system every which way that I could think of, and it always ends-up the same way., Aren't, you curious to know why? The fact that happens every time must mean that somewhere along the way the same thing happens that it shouldn't.
I mean if this must have solid underlying reasons, otherwise it wouldn't happen with such consistency. It is almost as if something is designed to render the two most important accounts in the operating system impotent.
If this is not a conspiracy theory, then it must be result of some most exquisite kind of stupidity not considered at some stage of the development.
I have had a detailed look at your suggestion but I am still not sure why it should make any different to running icacls.exe from the command module under Administrators rights.
If administrators have not right on a specific folder, how can it be allowed to carry out an operation on the same folders and files?
While some argue that PowerShell has access to .net and therefore is stronger than command line it still doesn't make logical sense.
While I take your point about takeown.exe command and can see that it could have been superfluous, but it shouldn't have caused damage. The problem is that when you run icacls.exe it keeps failing and at the end you have a message reporting many failures because of denial of access.
This was not under any ordinary administrator but under the inbuilt administrator which as least in Linux is supposed to be the ultimate authority and is created with absolute rights to every object.
Unless this is a fundamental flaw in the system the only other reason that I can imagine for it existing is the fact that we are talking about a system where the Administrator has been deliberately disabled and hidden because the Home edition was supposed to be used by non-technical people and may be they went a bit too far in restricting rights just to make sure that users could not damage the integrity of the system even if they tried.
Then by some freak of circumstances a specific parameter in my kind of hardware by accident removed more rights that it was supposed to and it was left hidden until I installed additional languages and Intel gave up supporting drivers for this model and given the fact that support for this version is to end soon, I happened to be one of the unlucky ones who decided to look into this issue rather than buy a new machine. In other words, I was the idiot who took on the challenge and given the lack of support shown by Microsoft it makes my theory more believable.
This is why I have decided to upgrade to Windows 10 Pro as I think under that version it might be easier to solve the problem and restore my data.
I think I did ask you if you are using a pro version or are you too using a home Edition.
In any case, unfortunately I have even run into problem with that. I finally realised that the upgrade takes place locally rather than dependent on downloading additional stuff from a server. Staying connected to the web makes it more difficult to upgrade and runs into errors. Illogical but hardly unexpected from Microsoft.
Anyway, I finally managed to upgrade but now I am asked to activate Windows again. The final insult is that when I try to activate Windows as requested, I am asked to downgrade to Windows 10 Home Edition which seems insanity, or this particular part of the code has not been updated to recognise that upgrading to PRO no longer requires purchase of additional licence for $145.00.
If you know of how to get round this then please let me know as I am not investing in any hope of a response from Microsoft Support based in the sub-continent somewhere given the accent of the person who last spoke to me a weeks ago. I have tried calling him and he claims to have tried to call me, but I have had no indication of such attempts registered on my phone.