New
#21
I wonder if MicroSoft is planning on fixing this problem any time soon. It seems to be wide spread and it's a definite problem. I'm hesitant to rename or delete the windowsapps folder as I don't want to mess anything else up.
I have never seen folders that a system administrator can not see in to before, but that seems totally messed up to me.
I can create a restore point fine, but when I try to restore to that point it fails just like on this thread with a error "0x80070091".
I am trying to understand is this a windows bug, I just installed windows 10 fresh and system restore worked but them after a few updates it stopped working and I get this same error again.
Is this an issue that effects every currently updated version of Windows 10? Maybe test on other PC's to see if they are having the same issue? create restore point then right away restore to that new point and see if you get the same issue?
Last edited by jsdeprey; 22 Feb 2017 at 22:07.
I assume this is all because of the way windows 10 handles safe mode now, namely that it goes in to a "recovery environment" that doesn't require a "user" log in.
Good news. No you do not. If everything is working then I would leave it as it is.
If you want to though (for completeness for example) then you can do it like this...
This only removes the authority explicity granted to your profile which you added before. Other authorities will remain as they were. It doesn't add any "deny" authority for your profile so don't worry about that.Code:icacls "C:\Program Files\WindowsApps" /remove:g "%USERDOMAIN%\%USERNAME%" /t
You can then reset the owner to TrustedInstallerYou can then check the authority - it should look like this (type the bit in red and then see if the other looks the same)Code:icacls "C:\Program Files\WindowsApps" /setowner "NT SERVICE\TrustedInstaller"HTHCode:Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\Windows\system32>icacls "C:\Program Files\WindowsApps" C:\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F) NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(GR,GE) NT AUTHORITY\SYSTEM:(F) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(CI)(RX) NT AUTHORITY\LOCAL SERVICE:(OI)(CI)(RX) NT AUTHORITY\NETWORK SERVICE:(OI)(CI)(RX) BUILTIN\Users:(Rc,S,RD,REA,X,RA) Mandatory Label\Low Mandatory Level:(OI)(CI)(NW) Successfully processed 1 files; Failed processing 0 files C:\Windows\system32>
Hey, many thanks! I am 73 years old and mostly blind now and use a text-to-speech screenreader these days to navigate and listen to the Internet, et al. I was able to follow most of this thread and resolve my problem with System Restore and the windowsApp folder. I did not use the CMD prompt however. I gained control of the folder using the prompts in Windows 10 and then was finally able to rename the folder by using cntrl-alt-del and signing out and then back in (instead of using exit and restarting in Safe Mode). Anyway, once I renamed the windowsApp folder, System Restore started working again and a new WindowsApp was created with all the apps restored. Many thanks for leading me in the right direction to fix this problem without needing to do a full system image restore. You are the best!!!
After this fix is applied does System Restore continue to work indefinitely or does it mess up again?