"Fix it" Life-cycle

On Thu, 21 Jun 2012 10:09:32 +0100, Dick K wrote:

Microsoft sometimes release temporary "Fix it" solutions
to urgent problems in advance of corresponding patches.
Is there any rule governing whether or at what point such
a "Fix it" should be manually disabled? Before installing
the patch? After? Unnecessary?

Before installing the patch (is what I've read). Installing a patch
won't uninstall the Fix-it...

s|b

On 21/06/2012 20:47, s|b wrote:

On Thu, 21 Jun 2012 10:09:32 +0100, Dick K wrote:

Microsoft sometimes release temporary "Fix it" solutions
to urgent problems in advance of corresponding patches.
Is there any rule governing whether or at what point such
a "Fix it" should be manually disabled? Before installing
the patch? After? Unnecessary?

Before installing the patch (is what I've read). Installing a patch
won't uninstall the Fix-it...

Many thanks. I'll just have to scrutinize each important patch
until the right one comes along. FWIW this is the offending
vulnerability:

http://technet.microsoft.com/en-us/...ry/2719615


Regards,

Dick K

On 6/22/2012 12:16 AM, Dick K wrote:

On 21/06/2012 20:47, s|b wrote:

On Thu, 21 Jun 2012 10:09:32 +0100, Dick K wrote:

Microsoft sometimes release temporary "Fix it" solutions
to urgent problems in advance of corresponding patches.
Is there any rule governing whether or at what point such
a "Fix it" should be manually disabled? Before installing
the patch? After? Unnecessary?

Before installing the patch (is what I've read). Installing a patch
won't uninstall the Fix-it...

Many thanks. I'll just have to scrutinize each important patch
until the right one comes along. FWIW this is the offending
vulnerability:

http://technet.microsoft.com/en-us/...ry/2719615

This gets a bit messy.

If the "fix" replaces or changes code that a later update also replaces,
the "fix" sort of goes away in favor of the update.

On the other hand, the fix may disable or change something elsewhere.
In this case, hopefully, the update senses that the "fix" was previously
implemented, and does what is necessary to bring the configuration to a
"normal" condition.

There are a lot of variables for the second example, and, as a result,
some concern is warranted.

In article <jruoc9$vch$, says...

Microsoft sometimes release temporary "Fix it" solutions
to urgent problems in advance of corresponding patches.
Is there any rule governing whether or at what point such
a "Fix it" should be manually disabled? Before installing
the patch? After? Unnecessary?

Since the FixIt is a program, it does show up in Programs and Features.
For the recent XML one, it shows up as 3 entries for CVE-2012-1889.
Hopefully, a patch could recoginize that it's installed and uninstall it
if necessary.

If there is a no_junk in my address, please REMOVE it before replying!
All junk mail senders will be prosecuted to the fullest extent of the
law!!
http://home.comcast.net/~andyross

On 21/06/2012 10:09, Dick K wrote:

Microsoft sometimes release temporary "Fix it" solutions
to urgent problems in advance of corresponding patches.
Is there any rule governing whether or at what point such
a "Fix it" should be manually disabled? Before installing
the patch? After? Unnecessary?

Thank you charlie and Andrew for responding. I too hoped
that a patch would recognize and undo a previous Fix-it.
However absent a citation from Microsoft to that effect
better safe than sorry.


Regards,

Dick K