Windows 10: WSUS Client on Windows 1607 not seeing updates to 1803

Hello,


This is my first post here, well first ever post that I was not able to solve with searching.


At my organization we have workstations and a WSUS server that is not connected to the internet. We have two machines that were able to receive the windows 1803 update. The 18 other machines are on 1607 (build 14393) and did not receive the update and report being up to date.


we ran -


net stop bits

net stop wuauserv

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f

reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIdValidation /f

<!-- we renamed Software Distribution to SoftwareDistribution.old -->

net start bits

net start wuauserv

wuauclt /resetauthorization /detectnow


Nothing changed.


We checked all group and local policies and they are the same. All of the machines are able to hit http://wsusIPort/SelfUpdate/wuident.cab and attempt to download the file.


We checked the registry keys for Windows Update and they all match.


Another group manages WSUS so we can't make changes to that.


What else can we do other than reimage the machines?

:)

 

WSUS clients are not able to get an updates. WSUS is reporting different version of client.

Hello guys,

We have issues across our company that 1709 users with Windows 10 are not getting updates from our WSUS server (2012 R2).

We tried known hot fixes such as deleting SoftwareDistribution folder, forcing service to stop and run again, manually find updates, restarting clients, restarting WSUS, downloading all avaiable updates
for WSUS, run diag tool downloaded from Microsoft on clients but nothing helps.

We are also tried to run new 2016 WSUS server but situation did not changed. I think maybe problem is in client version 1709?

Windows 10 1709 (16299.309) (WSUS is reporting 10.0.16299.248)

Windows 2016 (14393.2125)

We have around 150 clients with this issue.

Issues:

1. WSUS server is reporting that clients need updates but clients are not getting any.

2. Some clients are not reporting back but they are reachable. (F.E. Last report 25.2.2018)

3. When we are connected remotely to client PC and run WU manually, WU is telling us that PC has all needed updates and none are available.

4. We can see different version in WSUS than client's version really is (agent version - maybe this is the issue?)

I hope my description is enough, I saw many forums / users / companies are dealing with same issue but there is not a fix for this yet and also I did not saw a thread on Microsoft about this exact problem
yet. I am already googling this for 3 days...

Thanks for answering,

Best regards

Ondrej

 

WSUS Update from 1511 to 1607 MUI: Missing Languages


Hi all!

Currently we're updating the Windows 10 (x64 Ent 1511) clients in a multilingual VMware Mirage environment. Unfortunately the update from 1511 to 1607 is not supported/possible with VMware Mirage therefore we're planning to use WSUS.

The testing group consists of 3 Windows 10 Enterprise x64 1511 clients. The base Windows 10 image is English with three additional language packs (German, French, Italian).

After enabling language packs in the WSUS console we've assigned the anniversary update and all three language packs to the testing group. The anniversary update is being installed successfully while the language packs cannot be applied - without feedback.

Therefore, after the update from 1511 to 1607, on the next start-up we're facing an English UI instead of the GPO defined language - whether it's German, French or Italian.

Does anyone have any suggestions how to fix this?

I thank you very much!

Kind regards
Horst

 

WSUS not working want to remove client computers from dependency on WSUS

My server SBS2011 is not repairable in terms of WSUS. I inherited this system and am not sure the disks to reinstall are available. I have given up on SBS2011 especially WSUS 3.0. Seems to me my best option is to divorce my client computers from WSUS
control. I have only four client computers and they are on Windows 10. I read an interesting technet blog about Windows peer client update for the local network, but it does not tell me how to divorce WSUS on the server. The client computers do not allow
me an option to turn off server WSUS control. They simply give me the message "Some features are managed by your organization" on the Advance Settings page for updates.

There are no options for divorcing WSUS on the client. On the server management console the Updates option crashes. I have turned off WSUS services.

Please do not try to tell me to fix WSUS. It is not repairable trust me, nothing has worked. We can not upgrade to the Server Essentials 2016 because our hardware does not support certain new core functions required. Plus, my research of documentation
indicates 2016 does not support Windows 10 clients which I find odd. Previously I had found a modification to add Windows 10 clients to SBS2011.

I find that Windows is getting harder to manage with it's restrictive option control. I would have liked the option on the client to go directly to windows update. Why doesn't the client recognize that WSUS is off or broken on the server and present me
with the option to go to Windows Update. With Windows being so vulnerable to attack, I need those updates.

Thanks for your help. You get points if you provide a solution.