{"id":1509,"date":"2016-10-08T08:08:00","date_gmt":"2016-10-08T06:08:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=1509"},"modified":"2024-10-03T00:17:06","modified_gmt":"2024-10-02T22:17:06","slug":"windows-10-v-1607-fails-with-windows-update-error-0x80d05001","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2016\/10\/08\/windows-10-v-1607-fails-with-windows-update-error-0x80d05001\/","title":{"rendered":"Windows 10 V 1607 fails with Windows Update error 0x80D05001"},"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\" height=\"58\" align=\"left\" \/>Some users of Windows 10 are facing Windows Update error 0x80D05001 after moving to Version 1607 (Anniversary Update). Here are a short overview, how to diagnose and fix this issue.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/6bc31563ee114cdc93867b4e4d503e1b\" alt=\"\" width=\"1\" height=\"1\" \/>I've addressed error 0x80D05001 within my blog post <a href=\"https:\/\/borncity.com\/win\/2016\/09\/10\/windows-10-store-downloads-causes-error-0x80d05001\/\">Windows 10: Store downloads causes error 0x80D05001<\/a> for Windows 10 store. Nevertheless, the article contains some clue, what's the root cause for this error: Third party Internet Security Suites or VPN software that is using it's own proxy server.<\/p>\n<h3>Check the proxy server settings<\/h3>\n<p>One repair attempt is to check the settings for the proxy server used in Windows. Here are the steps.<\/p>\n<p>1. Press <em>Windows <\/em>+<em> R <\/em>to invoke the <em>Run <\/em>dialog box and type <em>inetcpl.cpl<\/em><strong>. <\/strong>Click <em>OK<\/em> to execute this command.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20200516164815\/https:\/\/x70.imgup.net\/IE-Settingcfe4.jpg\" \/><\/p>\n<p>2. Click the <em>Connections <\/em>tab, and then click the <em>LAN settings button<\/em>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20200516145738\/https:\/\/l65.imgup.net\/IE-Setting9ebf.jpg\" \/><\/p>\n<p>3. In <em>Local Area Network (LAN) Settings <\/em>dialog uncheck the box <em>Use a proxy server for your LAN (..)<\/em>.<\/p>\n<p>The close the dialog box and the tab using the <em>OK <\/em>button. Then try a reboot and check, if the issue has been fixed.<\/p>\n<blockquote><p>The steps to reset the proxy settings in Internet Explorer is also discussed in<a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/2289942\">KB2289942<\/a>. If your application requires a proxy server, read <a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/3175743\">KB3175743<\/a>, and set the proxy rules according to the requirements defined in the KB article.<\/p><\/blockquote>\n<h3>Same problem with a hardware firwall<\/h3>\n<p>The attempt to check the proxy settings in Windows 10 was confirmed also for Windows Update error 0x80D05001. <a href=\"https:\/\/web.archive.org\/web\/20201130091653\/https:\/\/social.technet.microsoft.com\/Forums\/en-US\/59f0b9f1-3e92-47f3-91dd-0bbc1c0ad433\/windows-update-fails-with-error-80d05001-since-upgrade-to-1607?forum=win10itprogeneral\" target=\"_blank\" rel=\"noopener noreferrer\">Here<\/a> at Technet forum a user reported the same error after moving from Windows 10 version 1511 to version 1607.<\/p>\n<blockquote><p>since upgrading to Windows 10 version 1607 updating our clients fails with error code 80d05001.<\/p>\n<p>I could narrow it down to our firewall that does http and https inspection. That seems quite weird as it was working properly with version 1511. According to the logs the issue may be caused by update delivery via file streaming.<\/p><\/blockquote>\n<p>Turning <a href=\"https:\/\/privacy.microsoft.com\/en-us\/windows-10-windows-update-delivery-optimization\" target=\"_blank\" rel=\"noopener noreferrer\">Delivery Optimization<\/a> off (p2p) doesn't help in Windows 10 Anniversary Update. The user tracked it down to:<\/p>\n<blockquote><p>It seems Windows 10 does not use standard conform MIME-types for downloading since version 1607.<\/p><\/blockquote>\n<p>The user had a hardware firewall, a Sophos appliance, that blocks the connection to the Windows update servers. The user had to set some exception in their Sophos hardware firewall. For the web filtering exceptions they used the following regex-expressions:<\/p>\n<p>^https?:\/\/([A-Za-z0-9.-]*\\.)?windowsupdate\\.com\/<br \/>\n^https?:\/\/([A-Za-z0-9.-]*\\.)?microsoft\\.com\/<\/p>\n<p>Afterward Windows Update went back to live in Windows 10 Anniversary Update.<\/p>\n<p><strong>Similar articles:<br \/>\n<\/strong><a href=\"https:\/\/borncity.com\/win\/win10-wiki\/\">Windows 10 Wiki<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2016\/07\/08\/check-and-repair-windows-system-files-and-component-store\/\">Check and repair Windows system files and component store<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2016\/09\/10\/windows-10-store-downloads-causes-error-0x80d05001\/\">Windows 10: Store downloads causes error 0x80D05001<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2016\/08\/29\/windows-10-error-0x800704cf\/\">Windows 10: Error 0x800704CF<br \/>\n<\/a><a href=\"https:\/\/web.archive.org\/web\/20180313043542\/http:\/\/borncity.com:80\/win\/2015\/07\/29\/windows-10-upgrade-error-80240020\/\">Windows 10: Upgrade error 80240020<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/08\/08\/windows10-upgrade-error-0x80200013\/\">Windows 10: Upgrade error 0x80200013<br \/>\nWindows 10: Upgrade error 0x8007002C-0x4000D<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2016\/07\/18\/windows-10-upgrade-error-0xc1900101-0x20003\/\">Windows 10: Upgrade error 0xC1900101 \u2013 0x20003<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/08\/08\/windows10-upgrade-error-0x80200013\/\"><br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/07\/31\/windows-10-upgrade-error-0xc1900101-0x20004\/\">Windows 10: Upgrade error 0xC1900101 \u2013 0x20004<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/08\/16\/windows10-upgrade-error-0xc1900101-0x2000a\/\">Windows 10: Upgrade error 0xC1900101-0x2000A<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/08\/16\/windows10-upgrade-error-0xc1900101-020017030017\/\">Windows 10: Upgrade error 0xC1900101-0\u00d720017\/0\u00d730017<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2015\/10\/19\/windows-10-upgrade-error-0xc1900101-0x2000c\/\">Windows 10: Upgrade error 0xC1900101-0x2000C<br \/>\n<\/a><a href=\"https:\/\/web.archive.org\/web\/20170925092739\/http:\/\/borncity.com:80\/win\/2016\/08\/06\/windows-10-anniversary-update-upgrade-error-0xa0000400\/\">Windows 10 Anniversary Update: Upgrade error 0xA0000400<br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2016\/08\/03\/windows-10-update-error-0x80070057\/\">Windows 10: Update error 0x80070057<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Some users of Windows 10 are facing Windows Update error 0x80D05001 after moving to Version 1607 (Anniversary Update). Here are a short overview, how to diagnose and fix this issue.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,2],"tags":[398,47,195,335],"class_list":["post-1509","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-error-0x80d05001","tag-issue","tag-update","tag-windows-10-anniversary-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/1509","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=1509"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/1509\/revisions"}],"predecessor-version":[{"id":35309,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/1509\/revisions\/35309"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=1509"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=1509"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=1509"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}