reg 811493..

  • Thread starter Thread starter Robbie
  • Start date Start date
R

Robbie

Hi guys

A while ago, there was a lot of upset people posting here
about Window Updates 811493...
Because of this, I didn't download that patch..
I noticed that the patch is still there yesterday...
The dissatisfaction of 811493 on this forum has died down a
lot..does this mean the problem patch has been fixed, or
are you guys just ignoring the patch totally.
Is the patch OK to download...
Thanks in advance..
 
Microsoft has re-issued 811493, which seems to have fixed the problems for
the majority of the users. I've seen a few people say that they're still
having the slowdown problems with the original patch, but it's nothing like
the original amount of complaints.

I have it installed on 3 PCs (1 of which was originally effected), and I
don't have the issues anymore.
 
A while ago, there was a lot of upset people posting here
about Window Updates 811493...
Because of this, I didn't download that patch..
I noticed that the patch is still there yesterday...
The dissatisfaction of 811493 on this forum has died down a
lot..does this mean the problem patch has been fixed,
Click to expand...


Yes, it was fixed several weeks ago.
 
Microsoft has re-issued 811493, which seems to have fixed the problems
for the majority of the users. I've seen a few people say that they're
still having the slowdown problems with the original patch, but it's
nothing like the original amount of complaints.

I have it installed on 3 PCs (1 of which was originally effected), and I
don't have the issues anymore.
Click to expand...

The problem I am having with the new version 811493 is not a slowdown. It
is that it crashes my PC after a few hours!

Install 811493 and the PC will suddenly lock solid (CPU crash) after a
random one, two, three hours use, even if it is just "doing nothing". Re-
boot the PC and it will crash again a few hours later, and so on.

Remove 811493 and the PC will run for days on end without crashing. The
culprit seems clear to me, although some people (I don't mean you Mike)
seem to want to insist that 811493 has been unconditionally fixed. Maybe
it has for some...

I can happily live without the fix, but I am concerned as to what will
happen when it eventually gets rolled-up into SP2.

Ted.
 
Hi Ted,
I'm sorry to hear that you're still having a problem with 811493. I agree
that it seems to be the culprit... or atleast the catalyst for your system
troubles.

As far as SP2 goes, I believe fixes that get rolled into service packs are
normally put into a much more extensive regression testing cycle than the
QFE hotfixes from WindowsUpdate. (That's not to say that QFEs aren't
tested, or are tested inadequately...) It's not uncommon to have the final
(SP) version of a hotfix be slightly different that the actual hotfix...
hopefully, that will be the case with 811493
 
Hi Ted,
I'm sorry to hear that you're still having a problem with 811493. I
agree that it seems to be the culprit... or atleast the catalyst for
your system troubles.

As far as SP2 goes, I believe fixes that get rolled into service packs
are
normally put into a much more extensive regression testing cycle than
the
QFE hotfixes from WindowsUpdate. (That's not to say that QFEs aren't
tested, or are tested inadequately...) It's not uncommon to have the
final
(SP) version of a hotfix be slightly different that the actual hotfix...
hopefully, that will be the case with 811493
Click to expand...

Let's hope so! :-)

Maybe by the time SP2 appears enough other thing will have changed to
remove the problem.

Ted.
 
Robbie said:
A while ago, there was a lot of upset people posting here
about Window Updates 811493...
Because of this, I didn't download that patch..
I noticed that the patch is still there yesterday...
The dissatisfaction of 811493 on this forum has died down a
lot..does this mean the problem patch has been fixed, or
are you guys just ignoring the patch totally.
Click to expand...

There is now a revised version which is OK (I have seen a couple of
people associating trouble with it, but their position is not that of a
controlled test).

But I would leave it, together with several other fixes, unless you are
running a company network. It addresses a problem by which someone *who
is able to logon* [or connect] with Limited rights can then promote
himself to full control. This may matter to a company which needs to
defend against potential disaffected employees seeking to wreak havoc,
but not on a stand alone machine or a family net (unless just perhaps
there is a very clued up but intransigent teenager around :-)) )
 
Back
Top