Wsus windows 21h1 update

%3CLINGO-SUB%20id%3D%22lingo-sub-2427486%22%20slang%3D%22en-US%22%3EWsus%20windows%2021h1%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2427486%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%2C%3C%2FP%3E%3CP%3Emy%20wsus%20server%20(server%202016)%20synced%20the%20feature%20update%20to%2021H1%20but%20every%20client%20(all%2020H2)%20is%20reporting%20not%20needed.%3C%2FP%3E%3CP%3EI%20noticed%20that%20it%20synced%20only%20the%20full%20update%20and%20not%20the%20enablement%20package.%3C%2FP%3E%3CP%3EAnyone%20have%20the%20same%20problem%20or%20know%20something%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2427486%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWSUS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2431276%22%20slang%3D%22en-US%22%3ERe%3A%20Wsus%20windows%2021h1%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2431276%22%20slang%3D%22en-US%22%3EAre%20they%20old%20devices%20or%20new%20one%3F%3CBR%20%2F%3ESometimes%2C%20there%20might%20be%20a%20blocking%20issue%20like%20there%20is%20compatibility%20issue%20and%20the%20update%20is%20not%20applicable%20yet.%3CBR%20%2F%3EDo%20a%20quick%20test%20and%20try%20check%20for%20update%20in%20one%20of%20the%20device%20manually%20and%20see%20if%20it%20offers%20the%20update%20to%2021H1%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2433800%22%20slang%3D%22en-US%22%3ERe%3A%20Wsus%20windows%2021h1%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2433800%22%20slang%3D%22en-US%22%3EI%20tried%20to%20check%20online%20updates%20on%20two%20clients%20with%20completely%20different%20hardware%20and%20it%20not%20offered%20the%20update%20so%20I%20suppose%20you%20are%20right%20and%20the%20clients%20could%20not%20be%20ready.%3CBR%20%2F%3EBut%20you%20have%20any%20guess%20on%20why%20wsus%20didn't%20sync%20the%20enablement%20package%20update%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello everyone,

my wsus server (server 2016) synced the feature update to 21H1 but every client (all 20H2) is reporting not needed.

I noticed that it synced only the full update and not the enablement package.

Anyone have the same problem or know something?

 

Thank you

2 Replies
Are they old devices or new one?
Sometimes, there might be a blocking issue like there is compatibility issue and the update is not applicable yet.
Do a quick test and try check for update in one of the device manually and see if it offers the update to 21H1?
I tried to check online updates on two clients with completely different hardware and it not offered the update so I suppose you are right and the clients could not be ready.
But you have any guess on why wsus didn't sync the enablement package update?