{"id":2390,"date":"2017-03-02T00:52:00","date_gmt":"2017-03-01T23:52:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2390"},"modified":"2020-12-13T00:25:59","modified_gmt":"2020-12-12T23:25:59","slug":"windows-10-update-kb3213986-kills-system-restore","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/03\/02\/windows-10-update-kb3213986-kills-system-restore\/","title":{"rendered":"Windows 10 Update KB3213986 kills system restore"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" align=\"left\" height=\"58\">Microsoft's cumulative January 2017 update KB3213986 seems to cause a serious issue in Windows 10 Anniversary Update. After installing this update, system restore fails with error 0x80070091.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/7aeedd8375174717a6a6f5ba757b993b\" width=\"1\" height=\"1\">I've addressed this error within my blog post <a href=\"https:\/\/borncity.com\/win\/2017\/02\/22\/windows10-version-1607-system-restore-error-0x80070091\/\" target=\"_blank\" rel=\"noopener\">Windows 10 Version 1607: System restore error 0x80070091 [Fix]<\/a> a few days ago. Trying to execute a system restore ends after a \"long time\" with error message 0x80070091. <\/p>\n<p><img decoding=\"async\" title=\"Fehlercode 0x80070091\" alt=\"Fehlercode 0x80070091\" src=\"https:\/\/web.archive.org\/web\/20170621082800\/https:\/\/p33.imgup.net\/Error-0x808503.jpg\">  <\/p>\n<p>During investigating this issue, I came to a conclusion, that update KB3213986 is involved. Some of my German readers came back with a comment, that NTFS links within <em>WindowsApps <\/em>subfolders may be the cause for this issue. One user mentioned VFS sub folders as the root cause (couldn't be deleted). I searched the web and found some mention of VFS for App-V, desktop brigde and Hyper-V. The <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4009938\/windows-10-update-kb3213986\" target=\"_blank\" rel=\"noopener\">changelog<\/a> for cumulative January 2017 update KB3213986 mentions also fixes in Hyper-V and App-V. <\/p>\n<p>Last weekend I spended several hours to test some things. As a conclusion, I identified KB3213986 as involved into this issue, but It's not sufficient to uninstall this update to fix the bug. The advices given within my blog post <a href=\"https:\/\/borncity.com\/win\/2017\/02\/22\/windows10-version-1607-system-restore-error-0x80070091\/\" target=\"_blank\" rel=\"noopener\">Windows 10 Version 1607: System restore error 0x80070091 [Fix]<\/a> are still required. At this point I gave up to do further tests (I ran out of time). <\/p>\n<p>But I've posted my assumptions within <a href=\"https:\/\/answers.microsoft.com\/en-us\/windows\/forum\/windows_10-update\/win-10-system-restore-fail-0x80070091\/7f690ec3-a3da-4c14-90fd-3eb0ba83f4ac?tab=question&amp;status=AllReplies&amp;status=AllReplies#tabs\" target=\"_blank\" rel=\"noopener\">MS Answers forum<\/a>, and Gegory Livingston confirmed now the following.  <\/p>\n<ul>\n<li>It is update KB3213986 that causes the problem to occur in the first instance.\n<li>Rolling back the update does not correct the problem.\n<li>Performing the known fix returns System Restore functionality.\n<li>For how long, we don't yet know.<\/li>\n<\/ul>\n<p>Well, that's odd. As I wrote within the MS answers forum thread: System restore seems to be terrible broken from time to time; Windows backup isn't reliable; and I came across forum posts, where restoring Windows 10 using recovery fails also with error 0x80070091. So as a Windows 10 user, you are forced to use a third party backup tool (Macrium reflection, ToDo Backup etc.) to create system backups on a periodical base, in the hope, that you are able to restore a damaged OS. Happy new Windows 10 world \u2013 isn't it?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft's cumulative January 2017 update KB3213986 seems to cause a serious issue in Windows 10 Anniversary Update. After installing this update, system restore fails with error 0x80070091.<\/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,47,618,690,335],"class_list":["post-2390","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-error-0x80070091","tag-issue","tag-system-restore","tag-update-kb3213986","tag-windows-10-anniversary-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2390","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=2390"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2390\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}