{"id":4414,"date":"2017-12-04T19:24:23","date_gmt":"2017-12-04T18:24:23","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=4414"},"modified":"2024-10-05T23:07:02","modified_gmt":"2024-10-05T21:07:02","slug":"windows7-error-0x80248015-in-update-search-dec-4-2017","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/12\/04\/windows7-error-0x80248015-in-update-search-dec-4-2017\/","title":{"rendered":"Windows 7: Error 0x80248015 in Update Search (Dec. 4, 2017)"},"content":{"rendered":"

\"Windows[German<\/a>]Microsoft has successfully killed Windows Update search in Windows 7 SP1. Since December 4, 2017 Windows Update search stalls with 0x80248015. Here are a few details and some workarounds. <\/p>\n

###<\/strong> It seems that Microsoft has fixed this issue – see this MS answers forum post<\/a>\u00a0– and I reveived similar feedback from my German blog readers – see also my blog post\u00a0Windows 7: Fix broken Update (Error 0x80248015) 12\/4\/17<\/a>\u00a0###\"\"<\/strong><\/p>\n

A couple of hours a German blog reader send me a mail, that informed me about an issue with Windows 7 update. The reader wrote:<\/p>\n

I am an enthusiastic (daily) reader of your IT blog. This is very helpful, especially when it comes to MS updates. Since today I have the problem that the Windows Update function seems to be corrupt on ALL Windows 7 machines I am maintaining, because the service is supposedly not running.<\/p>\n

There are all different computers at different locations, but all win 7 (Home or Prof.)<\/p>\n

According to \"ReportingEvents. log\", the search or sync of the update client still worked yesterday on all computers. Not since today.
\nI tried to repair an update agent on a computer using MS Tool: Result – the update search is working again, but shortly after it terminates with the following error code:\"Code 80248015 – Unknown error on Windows Update\".<\/p>\n

Maybe this would be worth an own article on your site? Can you also detect the error on your systems?<\/p><\/blockquote>\n

I got this error too<\/h2>\n

After reading his mail, I decided to do a short check on my Windows 7 production machine. I received the following error message after a few seconds.<\/p>\n

\"Update<\/p>\n

Error 0x80248015 has been dropped, and I see the information, that the last update search was on December 3, 2017 01:53. The update history showed me, that a definition update KB2310138 for Microsoft Security Essentials has been installed as a last update.<\/p>\n

\"MSE-Update\"<\/p>\n

Could that be the root cause?<\/p>\n

What stands the error for?<\/h2>\n

If you search for the error on the Internet, you can quickly find indications that time, date or the time zone are incorrect (see e. g. here<\/a>). But I was able to rule it out very quickly.\u00a0 Then I visited my blog post Tip: Windows Update error code 0x8024xxxx list<\/a> to decode error 0x80248015. It stands for WU_E_DS_SERVICEEXPIRED<\/em> – An operation did not complete because the registration of the service has expired. <\/em><\/p>\n

Testing a 2nd system<\/h2>\n

Before I begun to repair my production machine, I decided to boot a 2nd machine with Windows 7. A netbook that hasn't been used for weeks was my test candidate. After booting, I received the update message shown below.<\/p>\n

\"Windows<\/p>\n

Windows Update could not search automatically and informed me, that I shall start update search. Clicking the search button ended with the dialog box below.<\/p>\n

\"Update<\/p>\n

The information says, that the search is not possible because the service is not running. Exactly what the blog reader told me within his mail. It is also not possible to display the update history. A restart is useless.<\/p>\n

My first idea was, that something like a certificate has been expired. So setting the data to a previous day may help. After doing so, Windows Update was indeed able to search again.<\/p><\/blockquote>\n

We are not alone \u2013 Microsoft messed it up<\/h2>\n

After I noticed, that setting the date to December 3, 2017 enables Windows Update search, I was sure, that it has something to do with an expired certificate. Then German blog reader Matthias pointed me to Woody Leonhard's ComputerWorld article Windows Update for Win7 broken, throwing error 80248015<\/a>. A reader of Woody's blog has informed him, that in:<\/p>\n

c:\\Windows\\SoftwareDistribution\\AuthCabs\\authcab.cab<\/p>\n

the expire dates for updates are stored:<\/p>\n

<IssuedDate>2013-12-03T11:59:25.5067616-08:00<\/IssuedDate>
\n<ExpiryDate>2017-12-03T11:59:25.5067616-08:00<\/ExpiryDate><\/p>\n

There is a thread<\/a> in MS Answers forum where the issue has been discussed also. It's Microsoft's fault. Well done.<\/p>\n

Addendum:<\/strong> Lawrence Abrams has published this article<\/a> at Bleeping Computer, decribing a few background details, why the update search fails.<\/p><\/blockquote>\n

.NET-Framwork update isn't the root cause<\/h2>\n

Blog reader Ralf Lindemann left a comment<\/a> within my German blog, supposing, that the revised .NET-Framework Update KB4049016 (2017-11 Security and Quality Rollup for .NET Framework\u2026) for Windows 7 messed it up. The WindowsUpdate.log <\/em>in Windows folder showed some failures after installing this update. But this is just coincidence. Because I checked my netbook, that hasn't been booted since weeks. .NET-Framework Update KB4049016 isn't mentioned within WindowsUpdate.log<\/em>.<\/p>\n

### Below are some workarounds – but they have side effects (options are missing afterward, Microsoft Security Essentials don't got updates anymore). I suggest to wait, until Microsoft releases a hot fix to overcom this issue ###<\/strong><\/p><\/blockquote>\n

Workaround #1: Set your date back in time<\/h2>\n

The most simple workaround, some users testet: The change the system date back to December 3, 2017. Then the file mentioned above is valid and update still searches for (old updates). But this workaround may has some other implications – from certificate issues up to auto time update.<\/p>\n

Workaround #2: Disable Microsoft update options<\/h2>\n

The a German blog reader left a comment, saying: Just go in control panel to the update settings, and uncheck Give me updates for Microsoft products \u2026. update Windows<\/em> (see below).<\/p>\n

\"Update<\/p>\n

I tried that, and voila, my Windows Update client was able to search again for updates. Thanks to my blog readers for support. Hope it helps to same some admins some extra work today.<\/p>\n

Note: After unchecking the option Give me updates for Microsoft …, Windows will remove the two lower options 'Microsoft Updat' and 'Software notifications'. I've published a while ago a German blog post\u00a0Windows 7\/8.1: Optionen fehlen in Windows Update \u2013 Teil 1<\/a>\u00a0– where I explain, how to get those options back. But overall: Microsoft has messed it up and they have to fix that mess. I'm only able to deliver some workarounds.<\/p>\n

And Microsoft Security Essentials stops receiving updates.<\/p>\n

BTW: I've posted an article within the\u00a0\u00a0MS Answers forum<\/a>\u00a0and escalated it to all moderators. Let's hope, they will forward it to Microsoft's developers.<\/p><\/blockquote>\n

Overall my suggestion is: Just wait, until Microsoft release some kind of hot fix to bring Windows Update back to life.<\/p>\n

Similar articles
\n<\/strong>Windows 10: What are 'Feature on Demand' Updates?<\/a>
\nWindows 10 V1709: Store broken (wrong manifest layout)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Microsoft has successfully killed Windows Update search in Windows 7 SP1. Since December 4, 2017 Windows Update search stalls with 0x80248015. Here are a few details and some workarounds.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22],"tags":[1176,4,47,195,17],"class_list":["post-4414","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","tag-0x80248015","tag-error","tag-issue","tag-update","tag-windows-7"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/4414","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=4414"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/4414\/revisions"}],"predecessor-version":[{"id":35945,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/4414\/revisions\/35945"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=4414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=4414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=4414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}