SOLVED

Windwos 10 2004 spreading ... how can I stop it?

%3CLINGO-SUB%20id%3D%22lingo-sub-1746720%22%20slang%3D%22en-US%22%3EWindwos%2010%202004%20spreading%20...%20how%20can%20I%20stop%20it%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1746720%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%2C%3C%2FP%3E%3CP%3ECurrently%20we%20do%20not%20have%20Windows%2010%20Servicing%20for%202004%2C%20therefore%20there%20is%20no%20reason%20why%202004%20should%20be%20spreading%20through%20my%20environment%2C%20but%20it%20is.%20As%20of%20today%2C%20I%20came%20to%20find%20out%20that%20we%20have%2024%20installations%20for%202004.%20My%20users%20aren't%20local%20administrators%2C%20yet%20I%20have%20a%20feeling%20that%20it's%20being%20installed%20through%20Windows%20Updates.%20Is%20there%20a%20way%20to%20stop%20the%20spreading%20of%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1746720%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESystem%20Center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1755915%22%20slang%3D%22en-US%22%3ERe%3A%20Windwos%2010%202004%20spreading%20...%20how%20can%20I%20stop%20it%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1755915%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20able%20to%20fix%20this%20by%20using%26nbsp%3BSelect%20when%20Private%20Builds%20and%20Feature%20Updates%20are%20received%20policy...set%20this%20to%20365%20days%20and%20apply%20to%20all%20Windows%2010%20devices%20and%20took%20care%20of%20it.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI'm%20still%20baffled%20as%20it%20seems%20that%20this%20feature%20update%20is%20'force'%20down%20to%20devices%20-%20all%20my%20users%20(all%2039%20devices%20who%20go%20the%20update)%20reported%20that%20they%20didn't%20manually%20go%20to%20Windows%20Updates%20and%20approved%20the%20installation.%20Even%20some%20of%20my%20kiosk%20devices%2C%20which%20have%20no%20active%20users%20logged%20on%2C%20got%20this%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1771561%22%20slang%3D%22en-US%22%3ERe%3A%20Windwos%2010%202004%20spreading%20...%20how%20can%20I%20stop%20it%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1771561%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658097%22%20target%3D%22_blank%22%3E%40Ed_Gonz%3C%2FA%3E%26nbsp%3BCould%20this%20update%20have%20been%20approved%20directly%20in%20WSUS%20on%20your%20SUP%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello everyone,

Currently we do not have Windows 10 Servicing for 2004, therefore there is no reason why 2004 should be spreading through my environment, but it is. As of today, I came to find out that we have 24 installations for 2004. My users aren't local administrators, yet I have a feeling that it's being installed through Windows Updates. Is there a way to stop the spreading of it?

 

Thanks!

2 Replies
Best Response confirmed by Ed_Gonz (Occasional Contributor)
Solution

I was able to fix this by using Select when Private Builds and Feature Updates are received policy...set this to 365 days and apply to all Windows 10 devices and took care of it.


I'm still baffled as it seems that this feature update is 'force' down to devices - all my users (all 39 devices who go the update) reported that they didn't manually go to Windows Updates and approved the installation. Even some of my kiosk devices, which have no active users logged on, got this update.

@Ed_Gonz Could this update have been approved directly in WSUS on your SUP server?