Wsus client not updating status
It likes to get stuck downloading updates and never go anywhere.
We understand why you might not want to pull such a large file from the Internet once for each of your clients, and are figuring this out as soon as we can.
We'll share further updates on the investigation as they become available.
Just for once, I wish that one of these 6mth updates could go off without some sort of major hitch! ) that were removed in 1607 and there is not currently away to have both ADMX loaded at one time.
Haven't seen the issue with the test machines I've been building. You may want to check what you're using before sucking in 1607.
Problem #4 is if you apply all the GPO's to a Windows 10 machine, for some unknown reason they can't be removed, replaced, or updated even if you leave the domain altogether. So while part of the team works with Microsoft to attempt to untangle that cluster, we're going the opposite way and put in the basics we need like drive mappings, app settings, proxies and the like, make sure that works, then add the recommended settings until something breaks.
I've tried setting the GPO option here to bypass with the intent of making sure the box gets updates straight from WSUS and not from other clients.https://blogs.technet.microsoft.com/mni ... If ($Result.reboot Required) I don't know about this issue, just trying to assist.s-10-1607/Adding KB3176495 as a preinstall package for one of my deployments via MDT seemed to help but it isn't working now. Have you considered using Fiddler2 to validate the machine is reaching out to the correct WSUS and not any peers?
Clients have upgraded to 1706 using Anniversary Update, but cannot get Cumulative Updates This is a bug in the Windows client that will be fixed in an upcoming cumulative update.This thread seems to better outline the behavior I'm seeing.https://social.technet.microsoft.com/Fo ...itprosetup Seems there is something to do with Cumulative Updates getting stuck.(Granted I run/test a lot of MS OS's and apps, but 600GB wasn't enough.) Once I move it to v Sphere I'll be able to give it more space. They're (to our eternal frustration) trying be as close to the STIG recommendations as possible, and asked us to setup GPOs based on that for testing.Problem #1 is whoever is making those STIG recommendations has never, tried to use a PC bound by those settings, because it leaves machines unusable.If you google the issue, it appears that Windows 1607 doesn't play nice with WSUS.