Prevent specific updates from instllaling

Hello, I've seen multiple post for this topic but no one seems to find a
programmatic answer. Everyone suggest WSUS or something similar. In my
environment we have many clinical applications some which seem to have
negative affects from different updates. I do not have this list on hand so I
am unable to share. What I'm looking to do is find a way to
block/simulate/fake (be it registry hack, script whatever) an update so that
going forward automatic updates or installing an update via .exe thinks that
the update is already there.

Can this be done or is it wishful thinking?

 

Flash1212 wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hello, I've seen multiple post for this topic but no one seems to find a
> programmatic answer. Everyone suggest WSUS or something similar. In my
> environment we have many clinical applications some which seem to have
> negative affects from different updates. I do not have this list on hand so I
> am unable to share. What I'm looking to do is find a way to
> block/simulate/fake (be it registry hack, script whatever) an update so that
> going forward automatic updates or installing an update via .exe thinks that
> the update is already there.
>
> Can this be done or is it wishful thinking? <!--colorc--><!--/colorc-->

I think it very unlikely that you can fake the presence of an update.

Of course, you could turn automatic updates off, or just hide the updates in
question. Or use WSUS. I don't understand why you need to block people from
installing the updates manually - is this likely to happen?

Harry.

 

"Harry Johnston [MVP]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Flash1212 wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Hello, I've seen multiple post for this topic but no one seems to find a
> > programmatic answer. Everyone suggest WSUS or something similar. In my
> > environment we have many clinical applications some which seem to have
> > negative affects from different updates. I do not have this list on hand so I
> > am unable to share. What I'm looking to do is find a way to
> > block/simulate/fake (be it registry hack, script whatever) an update so that
> > going forward automatic updates or installing an update via .exe thinks that
> > the update is already there.
> >
> > Can this be done or is it wishful thinking? <!--colorc--><!--/colorc-->
>
> I think it very unlikely that you can fake the presence of an update.
>
> Of course, you could turn automatic updates off, or just hide the updates in
> question. Or use WSUS. I don't understand why you need to block people from
> installing the updates manually - is this likely to happen?
>
> Harry.
> .<!--colorc--><!--/colorc-->
Thanks for the reply Harry. My goal is not to block users from installing
updates in general just certain ones. I didn't think about setting the
updates to hidden. That's a good start though it doesn't help if a manual
install is done. This will work for now though. Thanks!