WSUS deploying out to Win10 LTSB

[Sw0rd]

Hi everyone,

I'm having a few issues with our WSUS server deploying updates out to Windows 10 LTSB. On some clients we're getting Error code 0x80244019. Which leads me down one rabbit hole, but then I have some clients that are seeing the updates but it's getting stuck at 0% which is sending me down another rabbit hole. I have attempted multiple things at this point to try and fix it, most of them I've kinda forgot since it's now day 3 of fixing it. We have a GPO in place that sets the alternate server to the local WSUS Server, and all updates are saved onto the C: Drive of the server. The server is a 2012 R2 hosted on a HyperV, fully up to date and the WSUS Version is 6.3.9600.18694. We still have the majority of Windows 7 clients on site and they're getting the updates fine. Any help would be a godsend

 

Thanks

Edited June 14, 2018 by Sw0rd

[Michael]

On the GPO (where you specify the intranet location of WSUS), make sure all three fields are populated (even if they're all the same) -

 

http://servername:8530

[AJWhite1970]

Have you got the WSUS server listed as a Direct exception in your proxy settings on the PC's (assuming one is set)? Had very similar problems until I did that with my W10 workstations, W7 wasn't as fussy...

[Sw0rd]

How could I forget about Proxy Exceptions.... That fixed the Error code issue, but still having the downloads sticking at 0%. Regarding the GPO, Yeah both boxes have been filled out with the "server.domain.local" as I've found that just having the server name in Windows 10 can be a bit picky