KB937287 Status?

[Julian]

The MS Windows Vista Blog said on 19 Feb that following a number or problem
reports with the SP1 pre-requisite KB937287 update MS had decided to
"suspend the automatic distribution" of this update (see
http://windowsvistablog.com/blogs/w...-windows-vista-sp1-prerequisite-kb937287.aspx)

Having just installed some other updates, 937387 turned up this morning as
an important update, but I can find no announcement that the problems had
been resolved...

(http://support.microsoft.com/kb/937287 was last updated 12 Feb - the same
"date" as that on the update offered)

Anyone know what the official position is/where to watch for news?
(Definitely NOT going to install an update with known problems until I hear
the all-clear)

TIA

 

[Ronc]

FWIW, I installed the update on patch Tuesday. No problems yet!

The link you provided says:
"So far, we've been able to determine that this problem only affects a small
number of customers in unique circumstances. We are working to identify
possible solutions and will make the update available again shortly after we
address the issue.

Customers who may be experiencing this issue can use system restore to
correct it or contact 1-866-PC-Safety for help troubleshooting. Additional
guidance will be available via Microsoft's free Update Support Center soon."

There is an even scarier update to the blog at the top of the page. I don't
blame you for being concerned. You could note the blog's original reference
to "small number..." and "unique circumstances" and take the plunge with the
knowledge that there is always System Restore.

 

[Julian]

[and see the "WTF!" at the end]

The KB article referred to in the update is indeed scary, since by telling
you how to "repair" your system it is essentially saying the update has well
and truly Fubar'd your system!

My implicit points were that the update mechanism makes no provision for
distinguishing between the originally posted update and any re-release, that
the direct KB article makes no reference to the update having been withdrawn
and so gives no grounds for confidence it would say when it was re-released
etc. etc. etc.

A small number of users in "unique circumstances" - pity they didn't share
the nature of those circumstances so that we could consider whether they
applied to us; I wonder whether they really know what those "unique
circumstances" are and just how "small" the number of affected users
actually is given that they actually chose to withdraw the update.

In other words, I'm glad your install went OK but I feel stuck since one
can't simply back out of the update and I can't tell whether it's safe to
install it.

WTF! Suddenly I look at the systray and see the Updates Available
notification has gone (despite specifically NOT clicking the "shutdown and
install" button when I restarted the system yesterday) and lo and behold
KB93728 was installed last night... because like an idiot I left the system
set to install automatically...

But since it installed OK, it seems I must not be one of the few and the
rest of the debate becomes academic... though I remain deeply unhappy about
the transparency of the update release - recall - ?re-release process.

I think I shall think about turning off automatic updates...

FWIW, I installed the update on patch Tuesday. No problems yet!

The link you provided says:
"So far, we've been able to determine that this problem only affects a
small number of customers in unique circumstances. We are working to
identify possible solutions and will make the update available again
shortly after we address the issue.

Customers who may be experiencing this issue can use system restore to
correct it or contact 1-866-PC-Safety for help troubleshooting.
Additional guidance will be available via Microsoft's free Update Support
Center soon."

There is an even scarier update to the blog at the top of the page. I
don't blame you for being concerned. You could note the blog's original
reference to "small number..." and "unique circumstances" and take the
plunge with the knowledge that there is always System Restore.