msoobe.exe - Application Error...Know Bug, Per Typical Microsoft N

[Guest]

I, as do MANY other MS customers get the following error after using SYSPrep
on an XP box. (I am using a legal corporate product key to install my OS.) We
have about 5,000 workstations on site all using XP Pro.

msoobe.exe - Application Error

This seems to be a Known Bug, have seen reference to it and its known causes
at least as far back as early Dec. 2006, more than adequate time for MS to
make a fix, but per typical lack of Microsoft customer care there is of
course no known fix I can find for it.

All the research I have done on it and the large number of people looking
for a fix, without finding one is just another example of Microsoft showing
what they really think of their customers. ie.. once they have your money,
you are useless to them, and why fix a known bug for someone we can't get
anymore money out of. I am sure they are thinking that the longer they leave
it unfixed the more opportunity they have to make some 1-900 cash.

Per all the research I have done this error will show up on ANY XP box that
has Sysprep run on it after letting MS updates install Media Player 11.
Needless to say this is an UNACCEPTABLE bug. Microsoft, of course, has know
about this for a long time, and in their typical greedy, we got your money
and you are no longer of any value to us way, have done nothing to fix it.

The only suggested workaround is to remove MP 11 prior to running Sysprep.
Of course this is not a fix and is totally unacceptable.

So that said I am hoping someone out there, an MVP, or heaven forbid, and
actual Microsoft rep, yeah and I bet I'll win the next big lotto to, will
prove my belief that MS (Microsoft) has my money, and I, and all my fellow MS
users, who have already paid MS their blood money, are useless and to be
ignored and forgotten, WRONG and send me the link to the permanent fix for
this error.

Thanks,

Ralph Malph

 

[stoosh]

If you've run sysprep and you've installed Media Player 11 before
hand, the only option is to do a repair from the Windows XP CD. It's
a gigantic pain in the butt, but is better than rebuilding the entire
image.

 

[Guest]

Thank you for your reply. As you know and stated, MS does not have a fix for
this well know and critical error. This is of course typical for MS and is
why the ENTIRE MS newsgroup community MUST demand that Bill respond and
justify why MS refuses to fix these kinds of critical bugs! Bill must be
GRILLED and embarrassed into doing the right thing. Someone out there in
cyberspace with some money or contacts in the "Lawyer" department needs to
SUE MS for putting out defective products/updates and refusing to fix them in
a timely manor. This should be a class action suite brought out on behalf of
the no doubt Millions of users who were sold their defective products and who
are to poor or not computer savvy enough to know that it is the moral,
(Legal, well maybe not with the current "Bush" court in session) obligation
of Microsoft to fix these issues in a timely manor. We as a community of
professional computer support engineers need to chastise and complain and
demand that MS step up to the plate and FIX all these issues, before even
having one engineer work on any other product. MS must be sued at all angles,
and embarrassed by constant UNIVERSAL complaining and demanding that MS step
up to the plate, or by default they will be admitting in "Public" (This needs
to be done in the most public mediums we can fine. i.e. I have asked PC World
to pick up this cause, it is being considered, you all need to do the same)
that they don't care and are the "EVIL GREEDY COMPANY" that their lack of
"action" shows them to be.

So come on, join me, and lets all GRILL BILL. or we can just meekly accept
his rule, and completely forget about ever having the principles of justice
and fairness applied to the Computing industry.

Ralph Malph

This, of course is just my humble opinion based on 20 years in the PC
support bus, and I could be wrong. Comments are welcome. Am I being to hard