{"id":2344,"date":"2017-02-22T10:42:57","date_gmt":"2017-02-22T09:42:57","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2344"},"modified":"2024-10-05T23:22:57","modified_gmt":"2024-10-05T21:22:57","slug":"windows10-version-1607-system-restore-error-0x80070091","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/02\/22\/windows10-version-1607-system-restore-error-0x80070091\/","title":{"rendered":"Windows 10 Version 1607: System restore error 0x80070091 [Fix]"},"content":{"rendered":"

[German<\/a>]It seems that a couple of Windows 10 users are facing system restore error 0x80070091. I've blogged about that issue within my German blog, and it seems that my solution works. Here are a few hints for my English readers how to analyze and solve this issue.<\/p>\n

<\/p>\n

\"\"I found several forum posts from December 2016 and January 2017 mentions this error code (see here<\/a>, here<\/a>, here<\/a>, here<\/a>, here for Windows 10, and here<\/a> for Windows 8). But I came across this error the first time within a German Microsoft Answers forum post<\/a>. A user describes the the error message as follows:<\/p>\n

Version 1607 (Build 14986.1001)
\nI'm using system restore to create a restore point. Then I tried to revert back to this system restore point. After a while I got an error 0x80070091.<\/p>\n

System Restore did not complete successfully. Your computer's system files and settings wern not changed.<\/p>\n

Details: System Restore failed whil restoring the directory from the restore point.
\nSource:\u00a0 AppxStaging
\nDestination: %ProgramFiles%\\WindowsApps<\/p><\/blockquote>\n

So system restore failed with error 0x80070091 due to something broken in AppxStaging<\/em>. Below is also a screenshot detailing this error.<\/p>\n

\"Fehlercode<\/p>\n

Error code 0x80070091 stands for ERROR_DIR_NOT_EMPTY (The directory isn't empty). Obviously something is broken in folder<\/p>\n

%ProgramFiles%\\WindowsApps<\/em><\/p>\n

so the AppxStaging <\/em>function drops an error and refuse to rewrite the folder from system restore.<\/p>\n

What's WindowsApps?<\/h3>\n

Windows 8 and later versions are using folder %ProgramFiles%\\WindowsApps<\/em> to store preinstalled apps Also Windows 10 is using this folder to store preinstalled apps.<\/p>\n

\"WindowsApps\"<\/p>\n

The screenshot shown above list the subfolders used to store apps. There are also folders named Deleted <\/em>or DeletedAllUserPackages<\/em> or MovedPackages <\/em>containing also entries. I guess, something during deleting, updating or moving an app went wrong, and a folder isn't left empty. Then AppxStaging <\/em>isn't able to restore the app folder from system restore and drops an error. Maybe third party tools like antivirus software is blocking, but I don't know for sure. The best, what we can do: Try to proceed the following steps \u2013 beginning with simple approaches.<\/p>\n

Feedback from my German reader of this blog post Windows 10 Version 1607: Unbekannter Fehler 0x80070091<\/a> confirms, that some solution works.<\/p><\/blockquote>\n

Addendum: How to list the WindowsApps folder as Administrator<\/h3>\n

Some user comments I received from my German blog post<\/a> are indicating, that the folder<\/p>\n

%ProgramFiles%\\WindowsApps<\/em><\/p>\n

contains some redirections (subfolders VFS<\/em> with NTFS links) and could not be deleted. Virtual File System is used by App-V to redirect folders for instance. Perhaps something went wrong during updating apps. Robert Aldwinckle has suggested at Microsoft Answers forum a solution<\/a> to list the folder's content without changing the permissions or tampering with TrustedInstaller rights. Here are the steps to proceed.<\/p>\n

    \n
  1. Press Windows+X and select Command prompt (Admin)<\/em>, and confirm UAC (see Windows 10: Open command prompt window as administrator<\/a>).<\/li>\n
  2. Enter PowerShell<\/em> in command prompt window and press the enter key .<\/li>\n
  3. If the PowerShell command prompt PS C:\\WINDOWS\\system32><\/em> is visible, use the commands below.<\/li>\n<\/ol>\n

    The command below changes the path to folder WindowsApps<\/em>.<\/p>\n

    cd $env:programfiles\\WindowsApps<\/em><\/p>\n

    Then use the following command to enlist all sub-folders and its content via PowerShell and store the results within clipboard.<\/p>\n

    (LS -Re -Fi * -Fo -Ea:Inquire).FullName | clip<\/em><\/p>\n

    <\/p>\n

    Then launch notepad using the PowerShell command notepad <\/em>and insert the clipboard content pressing Strg+V. Afterward you can inspect all sub-folders within Windows editor. Search for VFS <\/em>sub-folders for instance. My suspicion is, that some re-direction could be the cause for the system restore issue.<\/p>\n

    Fix #1: Try to remove third party tools and check your system<\/h3>\n

    If a third party antivirus software causes this issue, the most simple approach is, to uninstall this AV software and use a vendor's clean tool to remove also files and settings remaining from uninstalling.<\/p>\n

    Reboot Windows and check the system for damaged system components, using the advices given within my blog post Check and repair Windows system files and component store<\/a>. Also try to do a disk check for Windows drive (right click Windows drive, select Properties <\/em>and use the Tools <\/em>tab to start a disk scan).<\/p>\n

    Fix #2: Try system restore from Windows PE<\/h3>\n

    If third party tools blocks system restore, maybe it helps to execute system restore from Windows PE. Just click the On\/off button in start menu and select the Restart <\/em>command while the Shift<\/em> key has been pressed.<\/p>\n

    If the Windows PE<\/a> shows the page Chose an option <\/em>click Troubleshoot <\/em><\/em>and go to Advanced options <\/em><\/em>in the next page.<\/em><\/em><\/p>\n

    <\/p>\n

    Within the Advanced options <\/em>page select the System Restore <\/em>tile and let Windows PE try to execute the system restore (see also Windows 10 hangs with error code 0xc0000034<\/a> or Windows 10: Defender Offline Scan boot loop \u2013 Part 2<\/a>).<\/p>\n

    <\/p>\n

    If it goes well, system restore is successful and your machine will revert to the selected restore point.<\/p>\n

    This approach has been discussed here<\/a> and within the neosmart.net Wiki<\/a> \u2013 but I fear, it won't help in many cases.<\/p>\n

    I read also, that renaming folder WindowsApps is possible within Windows PE (in command prompt window) without further hassle. The other solution is discussed below at <\/em>Fix #5.<\/p><\/blockquote>\n

    Fix #3: Synchronize Computer settings<\/h3>\n

    There is another proposal how to fix system restore error 0x80070091 with synchronizing Windows settings. I found it within this MS Answers forum post<\/a>.<\/p>\n

      \n
    1. Go to Settings<\/em> app (via start menu), click on Accounts<\/em><\/li>\n
    2. Select Sync your settings<\/em><\/li>\n
    3. Turn off Sync settings<\/em><\/li>\n<\/ol>\n

      Then reboot Windows and check whether system restore is back in operation again. But I fear, it won't help.<\/p>\n

      Fix #4: Uninstall Windows Apps<\/h3>\n

      My idea was, to clean folder %ProgramFiles%\\WindowsApps, <\/em>because it is named as a root cause. One attempt could be to go to Settings<\/em>\u00a0 app, select System \u2013 Apps & Features <\/em>and try to uninstall all apps. But Windows 10 won't let you uninstall all pre-installed apps. So this attempt will fail.<\/p>\n

      It's possible, to use the approach discussed within this SuperUser thread<\/a>, and remove all apps via PowerShell. But that probably didn't help, if the app causing the system restore error has been partly removed. Maybe disk cleaning (via Windows drive's property <\/em>page) helps, but I'm skeptical.<\/p>\n

      Fix #5: Rename\/clean WindowsApps folder<\/h3>\n

      If you have proceeded the steps given above, and your are not successful at all, you run out of \"simple click solutions\". Then it's time for a more radical approach. We are going now to clean up the folder %ProgramFiles%\\WindowsApps<\/em> that is causing trouble.<\/p>\n

      Warning: You are at your own risk, and accessing this protected folder is a bit tricky \u2013 but feedback from my German blog readers say it works.<\/p><\/blockquote>\n

      The biggest problem is to access the folder %ProgramFiles%\\WindowsApps<\/em>, because this folder is owned by TrustedInstaller and is protected in a special manner. So you are not even able to open this folder within Windows Explorer.<\/p>\n

      You can try to obtain the ownership of this folder, following the advices given here How to Get Access to WindowsApps Folder in Windows 10<\/a> or here<\/a> or here<\/a>. But I won't recommend this solution, due to the risk of unknown side effects \u2013 and because I have a more smart solution.<\/p>\n

      This blog post How to clean up the app folder in Windows 8.1 and 10 (delete app\u00b4s)!<\/a> discusses how to use file manager Q-DIR to access the folder %ProgramFiles%\\WindowsApps<\/em>. I've used another approach: I executed the third party file manager Explorer++ portable within the Trusted Installer's context. Trusted Intaller has full access rights to %ProgramFiles%\\WindowsApps<\/em>.<\/p>\n

      The steps, how to launch Explorer++ portable with Trusted Installer credentials has been discussed within my blog post Windows 10: Execute programs as System\/ Trusted Installer<\/a>. Using this approach, enables me to create a copy of WindowsApps<\/em>, inspect sub folders and subsequently delete entries.<\/p>\n

        \n
      1. In a first approach just rename the folder WindowsApps <\/em>to WindowsApps.old<\/em>, using the approach outlined above.<\/li>\n
      2. Then reboot your Windows 10 machine and try to execute system restore and let it restore a previous state.<\/li>\n<\/ol>\n

        Some users of my German blog post confirmed, that this solution worked. One user mentioned, that some VFS subfolders contains NTFS links (for folder redirections) and couln't be deleted, but the WindowsApps<\/em> folder was renameable. System restore set the machine to a previous state, and all apps are also back. If that didn't cure the isse, your are able, to re-rename WindowsApps.old<\/em> back to WindowsApps <\/em>and try other fixes.<\/p>\n

        In case, you are not able to use process hacker and my solution above, or in case some files are locked, try to boot into\u00a0Windows PE (see Fix #2) and go to the command prompt windows. Then try to enter the following commands (press enter key to execute each command):<\/p>\n

        cd 'C:\\Program Files'
        \ntakeown \/f WindowsApps \/r \/d Y
        \nicacls WindowsApps \/grant \"%USERDOMAIN%\\%USERNAME%\":(F) \/t
        \nattrib WindowsApps -h
        \nrename WindowsApps WindowsApps.old<\/em><\/p>\n

        Note: I assumed, that logical drive C: is the Windows partition. Please check, if that's true – sometimes Windows drive is D: (tip: you can launch notepad.exe<\/em> and select File<\/em> – Open<\/em> to use Open dialog as a mini file manager). Drive X: is wrong, because this is Windows PE running in a RAM disk.\u00a0I've added the attrib command due to\u00a0GregoryLivingston's MS answers hint<\/a>, that rename fails, if the folder is hidden. If the rename command fails, or if you like to delete the folder, use the command:<\/p>\n

        rd \/s WindowsApps<\/em><\/p>\n

        The rd<\/em> command deletes the WindowsApps folder with all sub folders. It's confirmed within\u00a0this\u00a0forum post<\/a>, that the command sequence has\u00a0worked. Then close command prompt windows and try system restore again. It should work now (if not, try a reboot first).<\/p>\n

        If fix #5 fails also, it's time to reset your Windows 10 to factory settings, using the Settings <\/em>app. Hope, the hints given above helps to cure Windows 10 system restore error 0x80070091. Comments and further suggestions are welcome. If it worked for you, please let us know.<\/p>\n

        PostScript:<\/strong> There are indications, that the error could be related to January 2017 update for Windows 10. I've had a test machine with no other software installed, that fails with system restore error\u00a00x80070091. But uninstalling\u00a0KB3213986<\/a>\u00a0won't cure this (see my comment within the [German<\/a>] blog post) – you need to process the instruction of fix #5.<\/p>\n

        Addendum:<\/strong>\u00a0Well, we have nailed it down to KB3213986\u00a0(see\u00a0Windows 10 Update KB3213986 kills system restore<\/a>).<\/p>\n

        Addendum 2:<\/strong> See my new findings here\u00a0Windows 10: News about System restore error 0x80070091<\/a>.<\/p>\n

        Similar articles:
        \n        Win10 Wiki<\/a>
        \n<\/strong>        Windows: How to decode update 0x8024\u2026. errors<\/a>
        \n        Windows 10: Open command prompt window as administrator<\/a>
        \n        Check and repair Windows system files and component store<\/a>
        \n        How to fix Windows-Setup Hard Disk locked error<\/a>
        \n        Windows 10: Defender Offline Scan boot loop \u2013 Part 2<\/a>
        \n        Process Monitor: How to enable Windows 10 boot logging<\/a>
        \n        Windows 10: Execute programs as System\/TrustedInstaller<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

        [German]It seems that a couple of Windows 10 users are facing system restore error 0x80070091. I've blogged about that issue within my German blog, and it seems that my solution works. Here are a few hints for my English readers … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[680,618,76],"class_list":["post-2344","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-error-0x80070091","tag-system-restore","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2344","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=2344"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2344\/revisions"}],"predecessor-version":[{"id":36048,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2344\/revisions\/36048"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2344"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2344"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}