Another problems with KB825732

[Dan]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

Hi...

I'm not here to insult Microsoft or any of the hard working MPV's. But I
wanted to know if there was anyway of fixing this problem. I run a network
of about 75-80 machines all mixed 2000 and XP on an NT 4 domain. After the
update KB825732 (along with the other 4 that were released), people logging
in from an XP machine have certain mapped drives changed. For example all
users should have an S: drive. This drive is changed after the update on XP
machines to S:\ideas\users\*username* . This affects everyone who uses a
piece of CAD software called I-DEAS. The user can remap the drive back to
just S: (ticking the box reconnect at logon) but then when he next logs in
the drive is remapped back again.

Uninstalling KB825732 on an XP machine fails. Tried it on a number of
machines and it ends up missing a file and being unable to continue. Then
when you reboot having tried and then failed to UNINSTALL this patch you
simply get a blue screen and Windows needs to be completely
rebuilt/repaired. The only way I've found of removing this patch is to do a
system restore (which surely leaves unused files all over the place).

Once removed./restored all users are back to normal and everyone keeps the
correctly mapped drives.

Does this update mess around with mapped drives?

If it does is there a workaround that people should be using?

Why doesn't it simply UNINSTALL?

This update doesn't seem to affect any of the Win2000 users only XP.

Thanks for your help


Dan

 

[agent_c]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

"Dan" <danielfeldman@pdd.co.uk> wrote in message news:<ORpEtCFKEHA.3304@TK2MSFTNGP10.phx.gbl>...
> Hi...
>
> I'm not here to insult Microsoft or any of the hard working MPV's. [...]

It wouldn't be my propensity either, but some criticism of Microsoft
and their MVP's may be in order. This Hot[fix?](KB825732)is damaging
computers all over the world... has been for over 6 days... and
Microsoft has yet to issue an acknowledgement, or fix.

Even the most cursory research would reveal this, but the MVP's (Most
Valuable Pinheads?) seem to be the *least* aware and are offering the
most convoluted advice.

A_C

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

Give me a break. My machines aren't affected by this and none of my clients
have had any issues. Is there a possible problem? Maybe. Is it happening to
everyone? No. Does something occur almost everytime a patch is released?
Typically Did you test this before rolling it out to the network? No. Did
I test this before rolling it out to my network? No. I use SUS services and
this is done automatically. Have I been lucky? Maybe but I also do not use a
lot of specialty software in my environment and have never had issues.
Anyways, Agent_C, MVP's do not work for MS typically and do this on our own
to help with issues and also to learn from these newsgroups. If you don't
like the advice please do not come here. Get a local consultant or someone
with more technical knowledge than yourself. There is certainly no need to
bag on people helping out here because we are all in the same boat.
Sometimes these issue are totally related to your environment and basic
troubleshooting is in order and a lot of times some issues are just too
complex and there are too many details and unknowns for anyone to help in a
newsgroup.

Now for some ideas on the problem for Dan.

How are these drives being mapped? Login scripts? Local mappings?

Are wildcards used in the scripts? Does this affect a machine that does not
have this CAD software installed?

What kind of blue screen errors are you getting when rebooted after a failed
install?

Are these users local admin? Does it happen to every user that logs in to
these systems?

Does this only occur on this one particular drive mapping? Do different
drive mappins to other machines have the same results?


--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server


"Agent_C" <Agent-C-hates-spam@nyc.rr.com> wrote in message
news:20df5aaa.0404220535.700e1603@posting.google.com...
> "Dan" <danielfeldman@pdd.co.uk> wrote in message
news:<ORpEtCFKEHA.3304@TK2MSFTNGP10.phx.gbl>...
> > Hi...
> >
> > I'm not here to insult Microsoft or any of the hard working MPV's. [...]
>
> It wouldn't be my propensity either, but some criticism of Microsoft
> and their MVP's may be in order. This Hot[fix?](KB825732)is damaging
> computers all over the world... has been for over 6 days... and
> Microsoft has yet to issue an acknowledgement, or fix.
>
> Even the most cursory research would reveal this, but the MVP's (Most
> Valuable Pinheads?) seem to be the *least* aware and are offering the
> most convoluted advice.
>
> A_C

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

I also assume you mean KB835732 not 825732?!?!

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Agent_C" <Agent-C-hates-spam@nyc.rr.com> wrote in message
news:20df5aaa.0404220535.700e1603@posting.google.com...
> "Dan" <danielfeldman@pdd.co.uk> wrote in message
news:<ORpEtCFKEHA.3304@TK2MSFTNGP10.phx.gbl>...
> > Hi...
> >
> > I'm not here to insult Microsoft or any of the hard working MPV's. [...]
>
> It wouldn't be my propensity either, but some criticism of Microsoft
> and their MVP's may be in order. This Hot[fix?](KB825732)is damaging
> computers all over the world... has been for over 6 days... and
> Microsoft has yet to issue an acknowledgement, or fix.
>
> Even the most cursory research would reveal this, but the MVP's (Most
> Valuable Pinheads?) seem to be the *least* aware and are offering the
> most convoluted advice.
>
> A_C

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

Scott,
Although I understand where you are coming from, it is not reasonable for an
objective observer NOT to agree that this current situation is not normal.
Granted, the windows update KB835732 does not cause problems with all
computers - but it is clearly causing problems with ENOUGH computers that
both Microsoft and the appropriate MVPs should be able to agree - that
something is wrong here.

So far, the responses I have seen from the MVPs in response to this
"KB835732" issue - have generally been the type of advice that is given to
non-techies - which in this case is far from helpful and is probably what is
causing Agent_C (and quite a few other posters) to be blowing off a bit of
steam. Perhaps it would be possible to make the leap of faith that ALL of
the problems being reported in regard to KB835732 - are in fact NOT ALL
caused by user error.

Just a thought.

Tim.

"Scott Harding - MS MVP" <scrockel@**NO_SPAM**hotmail.com> wrote in message
news:%23gIk19IKEHA.2884@TK2MSFTNGP12.phx.gbl...
> Give me a break. My machines aren't affected by this and none of my
clients
> have had any issues. Is there a possible problem? Maybe. Is it happening
to
> everyone? No. Does something occur almost everytime a patch is released?
> Typically Did you test this before rolling it out to the network? No.
Did
> I test this before rolling it out to my network? No. I use SUS services
and
> this is done automatically. Have I been lucky? Maybe but I also do not use
a
> lot of specialty software in my environment and have never had issues.
> Anyways, Agent_C, MVP's do not work for MS typically and do this on our
own
> to help with issues and also to learn from these newsgroups. If you don't
> like the advice please do not come here. Get a local consultant or someone
> with more technical knowledge than yourself. There is certainly no need to
> bag on people helping out here because we are all in the same boat.
> Sometimes these issue are totally related to your environment and basic
> troubleshooting is in order and a lot of times some issues are just too
> complex and there are too many details and unknowns for anyone to help in
a
> newsgroup.
>
> Now for some ideas on the problem for Dan.
>
> How are these drives being mapped? Login scripts? Local mappings?
>
> Are wildcards used in the scripts? Does this affect a machine that does
not
> have this CAD software installed?
>
> What kind of blue screen errors are you getting when rebooted after a
failed
> install?
>
> Are these users local admin? Does it happen to every user that logs in to
> these systems?
>
> Does this only occur on this one particular drive mapping? Do different
> drive mappins to other machines have the same results?
>
>
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
>
>
> "Agent_C" <Agent-C-hates-spam@nyc.rr.com> wrote in message
> news:20df5aaa.0404220535.700e1603@posting.google.com...
> > "Dan" <danielfeldman@pdd.co.uk> wrote in message
> news:<ORpEtCFKEHA.3304@TK2MSFTNGP10.phx.gbl>...
> > > Hi...
> > >
> > > I'm not here to insult Microsoft or any of the hard working MPV's.
[...]
> >
> > It wouldn't be my propensity either, but some criticism of Microsoft
> > and their MVP's may be in order. This Hot[fix?](KB825732)is damaging
> > computers all over the world... has been for over 6 days... and
> > Microsoft has yet to issue an acknowledgement, or fix.
> >
> > Even the most cursory research would reveal this, but the MVP's (Most
> > Valuable Pinheads?) seem to be the *least* aware and are offering the
> > most convoluted advice.
> >
> > A_C
>
>

 

[Malke]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

Timothy Madsen wrote:

> Scott,
> Although I understand where you are coming from, it is not reasonable
> for an objective observer NOT to agree that this current situation is
> not normal. Granted, the windows update KB835732 does not cause
> problems with all computers - but it is clearly causing problems with
> ENOUGH computers that both Microsoft and the appropriate MVPs should
> be able to agree - that something is wrong here.
>
> So far, the responses I have seen from the MVPs in response to this
> "KB835732" issue - have generally been the type of advice that is
> given to non-techies - which in this case is far from helpful and is
> probably what is causing Agent_C (and quite a few other posters) to be
> blowing off a bit of
> steam. Perhaps it would be possible to make the leap of faith that
> ALL of the problems being reported in regard to KB835732 - are in fact
> NOT ALL caused by user error.
>
> Just a thought.
>
Of course no one thinks it is all just "user error". However, we MVP's
don't have any sekrit information that you don't have that we are
purposely not posting. We are not Microsoft employees and are not privy
to special informaton regarding the patches. This is also the Windows
XP General group, and so most of the questions posted here, and most of
the answers, tend not to be specialized. Although many of us who post
in this group have sysadmin experience (and I'm not one of those), the
best place to find MVP's who do systems administration for a living is
in the server groups.

Also, if a systems administrator user such as the OP is seriously having
problems with one of MS's patches (and no one is saying he isn't), then
he really should be calling up Microsoft tech support. I can tell you
from first-hand experience that they have a server-specific team and
they are great. Of course one may have to pay for it (although a
certain number of free tech support calls are included in the
licensing, I believe), but that's part of the cost of doing business.
I've paid the $245 myself when I needed help setting up a domain server
for a client and it was well worth it.

To trash and insult us MVP's as a group because somehow we're not
providing the OP exactly what he wants is, frankly, rude and
counter-productive.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

This fix has caused problems with a couple of PC's on our site, out of
around 250. The symptoms are that the System process grabs 100% of CPU
usage, making it VERY time consuming to remove the fix, going through
add/remove programs takes for ever. There must be a specific set of fixes,
SP numbers and IE versions installed that causes the problem. Both affected
machines were IE5.5 SP2 w2k SP4, but so are probably around 25% of our PC's.
I've now unauthorised the fix in SUS so its not deployed to anymore PC's.

Kerry
"Scott Harding - MS MVP" <scrockel@**NO_SPAM**hotmail.com> wrote in message
news:%23nJLmBJKEHA.3472@TK2MSFTNGP09.phx.gbl...
> I also assume you mean KB835732 not 825732?!?!
>
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
>
> "Agent_C" <Agent-C-hates-spam@nyc.rr.com> wrote in message
> news:20df5aaa.0404220535.700e1603@posting.google.com...
> > "Dan" <danielfeldman@pdd.co.uk> wrote in message
> news:<ORpEtCFKEHA.3304@TK2MSFTNGP10.phx.gbl>...
> > > Hi...
> > >
> > > I'm not here to insult Microsoft or any of the hard working MPV's.
[...]
> >
> > It wouldn't be my propensity either, but some criticism of Microsoft
> > and their MVP's may be in order. This Hot[fix?](KB825732)is damaging
> > computers all over the world... has been for over 6 days... and
> > Microsoft has yet to issue an acknowledgement, or fix.
> >
> > Even the most cursory research would reveal this, but the MVP's (Most
> > Valuable Pinheads?) seem to be the *least* aware and are offering the
> > most convoluted advice.
> >
> > A_C
>
>

 

[Jerry]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

Kerry Hoskin wrote:
> This fix has caused problems with a couple of PC's on our site, out of
> around 250. The symptoms are that the System process grabs 100% of CPU
> usage, making it VERY time consuming to remove the fix, going through
> add/remove programs takes for ever. There must be a specific set of fixes,
> SP numbers and IE versions installed that causes the problem. Both affected
> machines were IE5.5 SP2 w2k SP4, but so are probably around 25% of our PC's.
> I've now unauthorised the fix in SUS so its not deployed to anymore PC's.
>
> Kerry

Try this on one of the problem machines:

1. Uninstall KB825732.
2. Download and install latest versions for all hardware drivers
(display adapters, sound cards, network cards, motherboard resources,
BIOS) directly from the hardware vendors' web sites.
3. Install the KB825732 patch.

This may very well solve your problems. It has in most situations I've
seen or heard about.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain,microsoft.public.windowsupdate,microsoft.public.windowsxp.general (More info?)

I am not saying that there is nothing wrong with patching in general and I
certainly understand the frustrations but the MVP's have absolutely nothing
to do with this. I agree that maybe MS needs to update this patch or
something. I understand the need to vent but bagging on MS or MVP's or
anyone else is just so inappropriate that it makes me laugh I am not
saying that the admins are to blame for actually applying these patches. I
guess in general there needs to be a better solution. Until then we all have
to deal with this carp of patching......

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Jerry" <jheidtke@ameritech.net> wrote in message
news:u2hBnLKKEHA.2704@TK2MSFTNGP10.phx.gbl...
> Kerry Hoskin wrote:
> > This fix has caused problems with a couple of PC's on our site, out of
> > around 250. The symptoms are that the System process grabs 100% of CPU
> > usage, making it VERY time consuming to remove the fix, going through
> > add/remove programs takes for ever. There must be a specific set of
fixes,
> > SP numbers and IE versions installed that causes the problem. Both
affected
> > machines were IE5.5 SP2 w2k SP4, but so are probably around 25% of our
PC's.
> > I've now unauthorised the fix in SUS so its not deployed to anymore
PC's.
> >
> > Kerry
>
> Try this on one of the problem machines:
>
> 1. Uninstall KB825732.
> 2. Download and install latest versions for all hardware drivers
> (display adapters, sound cards, network cards, motherboard resources,
> BIOS) directly from the hardware vendors' web sites.
> 3. Install the KB825732 patch.
>
> This may very well solve your problems. It has in most situations I've
> seen or heard about.
>