# wsus...........ugh

**URL:** <https://forums.suse.com/t/wsus-ugh/28146>\
**Category:** Chatting over the Back Fence\
**Created:** [May 7, 2016, 1:28am UTC](https://forums.suse.com/t/wsus-ugh/28146 "2016-05-07T01:28:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)\
**Post date:** [May 7, 2016, 1:28am UTC](https://forums.suse.com/t/wsus-ugh/28146/1 "2016-05-07T01:28:20Z")

</div>

Ok, so I was an idiot apparently and installed m$'s latest wsus patch  
(3159706), following their instructions, and now my client machines  
cannot get updates from my wsus server.

I can get into the wsus console and look at stuff, but clients always  
error out with 80244008, or 8024401F.

Haven’t been able to find anything via google yet, any suggestions?

Aside from the standard “fdisk the server and build it again”

–  
Stevo

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [May 7, 2016, 3:16am UTC](https://forums.suse.com/t/wsus-ugh/28146/2 "2016-05-07T03:16:05Z")

</div>

> [@](#):
>
> On Fri 06 May 2016 10:28:20 PM CDT, Stevo wrote:
> 
> Ok, so I was an idiot apparently and installed m$'s latest wsus patch  
> (3159706), following their instructions, and now my client machines  
> cannot get updates from my wsus server.
> 
> I can get into the wsus console and look at stuff, but clients always  
> error out with 80244008, or 8024401F.
> 
> Haven’t been able to find anything via google yet, any suggestions?
> 
> Aside from the standard “fdisk the server and build it again”

[http://www.infoworld.com/article/3060241/microsoft-windows/botched-wsus-patch-kb-3148812-still-throws-errors-80244019-80244008-and-8024401f.html](http://www.infoworld.com/article/3060241/microsoft-windows/botched-wsus-patch-kb-3148812-still-throws-errors-80244019-80244008-and-8024401f.html)  
[http://www.vmwareandme.com/2014/02/Windows-8.1-Update-Fails-Code-8024401F-WSUS-Not-Yet-Reported.html](http://www.vmwareandme.com/2014/02/Windows-8.1-Update-Fails-Code-8024401F-WSUS-Not-Yet-Reported.html)

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
openSUSE Leap 42.1|GNOME 3.16.2|4.1.20-11-default  
If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below… Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [May 9, 2016, 5:06pm UTC](https://forums.suse.com/t/wsus-ugh/28146/3 "2016-05-09T17:06:02Z")

</div>

malcolmlewis sounds like they ‘said’:  
[color=blue]

> [/color]  
> [http://www.infoworld.com/article/3060241/microsoft-windows/botched-wsus-patch-kb-3148812-still-throws-errors-80244019-80244008-and-8024401f.html](http://www.infoworld.com/article/3060241/microsoft-windows/botched-wsus-patch-kb-3148812-still-throws-errors-80244019-80244008-and-8024401f.html)[color=blue]  
> [/color]  
> [http://www.vmwareandme.com/2014/02/Windows-8.1-Update-Fails-Code-8024401F-WSUS-Not-Yet-Reported.html](http://www.vmwareandme.com/2014/02/Windows-8.1-Update-Fails-Code-8024401F-WSUS-Not-Yet-Reported.html)

So my response to malcolmlewis’s comment is…

Tried the suggestion of the second link, that doesn’t work… :-/

–  
Stevo

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [May 9, 2016, 6:40pm UTC](https://forums.suse.com/t/wsus-ugh/28146/4 "2016-05-09T18:40:15Z")

</div>

So got it figured, I thought I had added the  
multipleSiteBindingsEnabled=“true” setting to the web.config, but  
apparently it didn’t save properly so that setting was not active.

Seems to be working now.

–  
Stevo
