Denying problematic updates

%3CLINGO-SUB%20id%3D%22lingo-sub-2277828%22%20slang%3D%22en-US%22%3EDenying%20problematic%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277828%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20computer%20is%20co%20managed%20with%20SCCM%20and%20it%20gets%20updates%20from%20an%20Intune%20update%20ring.%3C%2FP%3E%3CP%3EYesterday%20the%20computer%20had%20a%20BSOD%20because%20of%20update%205000808%20which%20is%20caused%20when%20attempting%20to%20print%20to%20certain%20drivers.%3C%2FP%3E%3CP%3EThe%20thing%20is%2C%20I%20didn't%20receive%20any%20fixes%20that%20were%20published%20as%20out%20of%20band%20updates.%3C%2FP%3E%3CP%3EMy%20question%20is%3A%20I%20know%20I%20can't%20control%20windows%20updates%20the%20same%20way%20I%20control%20them%20in%20WSUS.%20But%20I%20understand%20that%20pausing%20the%20ring%20might%20help.%20So%2C%20if%20my%20ring%20is%20set%20to%20run%20after%203%20of%20patch%20Tuesday%20weeks%20and%20I%20want%20to%20pause%20it%2C%20how%20long%20do%20I%20need%20to%20pause%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERahamim.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2277828%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278822%22%20slang%3D%22en-US%22%3ERe%3A%20Denying%20problematic%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278822%22%20slang%3D%22en-US%22%3EMy%20approach%20is%20to%20control%20it%20from%20the%20source%20rather%20than%20the%20destination.%20For%20example%2C%20In%20WSUS%20%5C%20SCCM%20you%20can%20deny%20an%20update%20from%20being%20deployed.%20You%20don't%20need%20to%20run%20a%20script%20on%20each%20computer%20to%20stop%20the%20deployment.%20I%20want%20to%20do%20the%20same%20thing%20in%20this%20case%20since%20this%20is%20not%20just%20my%20computer%20but%20all%20enrolled%20devices.%20In%20this%20case%2C%20only%20I%20was%20affected%20from%20this%20bug%20but%20as%20an%20IT%20admin%20I%20want%20to%20make%20sure%20I%20can%20verify%20the%20update%20and%20not%20accidentally%20deploy%20problematic%20updates%20to%20end%20users.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278805%22%20slang%3D%22en-US%22%3ERe%3A%20Denying%20problematic%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278805%22%20slang%3D%22en-US%22%3EHi%2C%20I%20did%20not%20test%20it%20lately.%20But%20it%20works%20when%20you%20want%20to%20hide%20an%20update.%3CBR%20%2F%3EWhat%20are%20the%20main%20reasons%20you%20don't%20want%20this%20module%20to%20be%20pushed%20to%20your%20endpoints%3F%3CBR%20%2F%3EIf%20you%20don't%20blocked%20powershell%2C%20It%20could%20be%20a%20reason%20of%20course...%3CBR%20%2F%3ETake%20a%20look%20for%20some%20ideas%2C%20how%20to%20prevent%20the%20use%20of%20powershell%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fcall4cloud.nl%2F2021%2F04%2Fpowershell-the-killer-queen%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcall4cloud.nl%2F2021%2F04%2Fpowershell-the-killer-queen%2F%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278731%22%20slang%3D%22en-US%22%3ERe%3A%20Denying%20problematic%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278731%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20idea%2C%20did%20you%20test%20this%3F%20Another%20problem%20I%20have%20is%2C%20I%20need%20to%20distribute%20the%20module%20to%20all%20computers.%20I%20would%20rather%20avoid%20that.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277981%22%20slang%3D%22en-US%22%3ERe%3A%20Denying%20problematic%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277981%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EJust%20another%20idea....%3CBR%20%2F%3EMaybe%20instead%20of%20pausing%20the%20update%20ring...%20maybe%20trying%20to%20exclude%2Fhide%20the%20update%20itself%20with%20a%20PowerShell%20script%3F%3CBR%20%2F%3E%3CBR%20%2F%3EInstall-Module%20-Name%20PSWindowsUpdate%20-force%20-confirm%3A%24False%3CBR%20%2F%3EHide-WindowsUpdate%20-KBArticleID%20%22kb%22%20-Confirm%3A%24false%3C%2FLINGO-BODY%3E
Frequent Contributor

Hi everyone,

 

My computer is co managed with SCCM and it gets updates from an Intune update ring.

Yesterday the computer had a BSOD because of update 5000808 which is caused when attempting to print to certain drivers.

The thing is, I didn't receive any fixes that were published as out of band updates.

My question is: I know I can't control windows updates the same way I control them in WSUS. But I understand that pausing the ring might help. So, if my ring is set to run after 3 of patch Tuesday weeks and I want to pause it, how long do I need to pause it?

 

Rahamim.

4 Replies
Hi,

Just another idea....
Maybe instead of pausing the update ring... maybe trying to exclude/hide the update itself with a PowerShell script?

Install-Module -Name PSWindowsUpdate -force -confirm:$False
Hide-WindowsUpdate -KBArticleID "kb" -Confirm:$false
Thanks for the idea, did you test this? Another problem I have is, I need to distribute the module to all computers. I would rather avoid that.
Hi, I did not test it lately. But it works when you want to hide an update.
What are the main reasons you don't want this module to be pushed to your endpoints?
If you don't blocked powershell, It could be a reason of course...
Take a look for some ideas, how to prevent the use of powershell

https://call4cloud.nl/2021/04/powershell-the-killer-queen/
My approach is to control it from the source rather than the destination. For example, In WSUS \ SCCM you can deny an update from being deployed. You don't need to run a script on each computer to stop the deployment. I want to do the same thing in this case since this is not just my computer but all enrolled devices. In this case, only I was affected from this bug but as an IT admin I want to make sure I can verify the update and not accidentally deploy problematic updates to end users.