Windows 10 clients not showing correct OS build after receiving updates (again)

Question

Hello,

So my other thread was locked and moved to archive, but we are still having the issue even after upgrading to 2004. Here is the link to the original thread - https://social.technet.microsoft.com/Forums/ie/en-US/87e01bb4-e6e7-4843-8558-d9415f0100b9/windows-10-clients-not-showing-correct-os-build-after-receiving-updates?forum=winserverwsus&prof=required

I'll keep this short and simple. We patch our systems with WSUS. I manually approve them each month for our different groups. The patches install, WSUS says the patch is installed, clients think the patch is installed, but the build number does not update.

Our experience this past year when clients get to this state is that on one of the next CU updates we will get a BSOD and have to reset or re-image. I can't say for sure this will happen on 2004, as this is the first CU that has been updated for our test site, but it looks like we are off to a bad start already.
We need a way to resolve this immediately, as there is no way I will be able to babysit our 300+ systems every month like this. The only way I've found to resolve is to unistall the CU and then reinstall. This is extremely disruptive to the users and really takes a toll on myself for having to reach out to all the users to schedule time to fix this.

Please someone help us!!
-Steve

Answer 1

Hi,

I noticed you have installed KB4566782, so the corresponding system version should be 19041.450, but your existing system version still persists as 19041.421.

Did you join Windows Insiders program as your existing system version 19041.421 which is released by Microsoft to the Beta Channel of the Windows Insiders program that brings all the features that were detailed earlier in the Dev Channel Build 20161.

So if you join machines to Windows Insiders program, we should exit Windows insider, and check system version build again. If it persists, try to uninstall package KB4566782, and reinstall it again to check if corresponding system version build occur.

Bests,

Answer 2

Hi JoyQiao,

Sorry for the delay in responding. The Feature update to 2004 has not gone well and has required a lot of manual work to accomplish. I've never seen an update that needed to retry, install, download so many times. In regards to the Insider program, we are just part of the regular channel, so no beta channels here. The .421 version is what we saw when we did the 2004 Feature update to those systems, which remained version .421after the KB4566782 update for August. We only use WSUS for the updates as well.

But you are correct in that the way to fix this is to unistall and reinstall the update, which we've had to do each month for a large number of systems. This is the exact issue that we need to have resolved. If we don't correct the version number, usually with the next CU update or a reboot the system will BSOD and go into automatic repair loop, which needs a system reset or a re-image. It's also random clients this happens to, so it's not the same ones each month, which is making this extremely difficult to troubleshoot. Also, at least 4 of the PC's in our test group that are showing the .421 version were just recently re-imaged, so this should technically be a fresh system.

Please let me know if you can think of anything else we can look at or any other details I can provide for this issue.

Thanks!
Steve