Do NOT remove security update kb917422 to play BF 2142!

[Smilin]

Not restarting after an update that requires it is a bad idea. You can end up with codependent code being mismatched due to one in memory (noted in the pendingrilerename registry key) remaining unchanged while the other on disk (and later loaded in memory) being updated.

So try the update AND restart. If that doesn't do the trick, try kb924066 then. If that doesn't do the trick, don't play 2142. Wait for EA to release a patch (hehe actually they'll probably release lots of patches...wait for the one that addresses this issue).

 

[archcommus]

Originally posted by: Smilin
Not restarting after an update that requires it is a bad idea. You can end up with codependent code being mismatched due to one in memory (noted in the pendingrilerename registry key) remaining unchanged while the other on disk (and later loaded in memory) being updated.

So try the update AND restart. If that doesn't do the trick, try kb924066 then. If that doesn't do the trick, don't play 2142. Wait for EA to release a patch (hehe actually they'll probably release lots of patches...wait for the one that addresses this issue).

Well for me, we were talking about Chaos Theory, which he has already beaten heh, so he can put the patch back in.

But for all you EA folk, how do you even know they're GOING to patch it? Or in a reasonable time frame?

 

[bob4432]

Originally posted by: jbourne77
Regardless of who's fault it is, the whole BF2142 debacle gets better and better every day.

QFT!!

i wonder what their bf2142 1.01 messed up.....:laugh: