Update138464,960225

We have several computer that will no longer logon the domain after these two
updates were applied. The updated don't seem to affect all computers. The
way we worked around this is to boot to the local machine with the network
cable unpluged uninstall 138464 and 960225, disjoin the computer from the
network resart then rejoin the computer to the network. We have one computer
that will not log onto the local machine at all. This works until the next
restart. I also noticed that ms has an update 938464v2. appling this does not
change anything

Please state your full Windows version(s) (e.g., WinXP SP3; Vista SP1) when
posting to this newsgroup.

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB938464).

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.net

John Hilton wrote:
> We have several computer that will no longer logon the domain after these
> two updates were applied. The updated don't seem to affect all computers.
> The way we worked around this is to boot to the local machine with the
> network cable unpluged uninstall [938464] and 960225, disjoin the computer
> from the network resart then rejoin the computer to the network. We have
> one computer that will not log onto the local machine at all. This works
> until the next restart. I also noticed that ms has an update 938464v2.
> appling this does not change anything

all are xppro two have sp2 the rest sp3

"PA Bear [MS MVP]" wrote:

> Please state your full Windows version(s) (e.g., WinXP SP3; Vista SP1) when
> posting to this newsgroup.
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
>
> For home users, no-charge support is available by calling 1-866-PCSAFETY in
> the United States and in Canada or by contacting your local Microsoft
> subsidiary. There is no-charge for support calls that are associated with
> security updates. When you call, clearly state that your problem is related
> to a Security Update and cite the update's KB number (e.g., KB938464).
>
> Support for Windows Update:
> http://support.microsoft.com/gp/wusupport
>
> For more information about how to contact your local Microsoft subsidiary
> for security update support issues, visit the International Support Web
> site: http://support.microsoft.com/common/international.aspx
>
> For enterprise customers, support for security updates is available through
> your usual support contacts.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin; DTS-L.net
>
> John Hilton wrote:
> > We have several computer that will no longer logon the domain after these
> > two updates were applied. The updated don't seem to affect all computers.
> > The way we worked around this is to boot to the local machine with the
> > network cable unpluged uninstall [938464] and 960225, disjoin the computer
> > from the network resart then rejoin the computer to the network. We have
> > one computer that will not log onto the local machine at all. This works
> > until the next restart. I also noticed that ms has an update 938464v2.
> > appling this does not change anything
>
>

Repost, in case you overlooked it:
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527

John Hilton wrote:
> all are xppro two have sp2 the rest sp3
>
> "PA Bear [MS MVP]" wrote:
>> Please state your full Windows version(s) (e.g., WinXP SP3; Vista SP1)
>> when
>> posting to this newsgroup.
>>
>> Start a free Windows Update support incident request:
>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>
>> For home users, no-charge support is available by calling 1-866-PCSAFETY
>> in
>> the United States and in Canada or by contacting your local Microsoft
>> subsidiary. There is no-charge for support calls that are associated
>> with
>> security updates. When you call, clearly state that your problem is
>> related to a Security Update and cite the update's KB number (e.g.,
>> KB938464).
>>
>> Support for Windows Update:
>> http://support.microsoft.com/gp/wusupport
>>
>> For more information about how to contact your local Microsoft subsidiary
>> for security update support issues, visit the International Support Web
>> site: http://support.microsoft.com/common/international.aspx
>>
>> For enterprise customers, support for security updates is available
>> through
>> your usual support contacts.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE, OE, Security, Shell/User)
>> AumHa VSOP & Admin; DTS-L.net
>>
>> John Hilton wrote:
>>> We have several computer that will no longer logon the domain after
>>> these
>>> two updates were applied. The updated don't seem to affect all
>>> computers.
>>> The way we worked around this is to boot to the local machine with the
>>> network cable unpluged uninstall [938464] and 960225, disjoin the
>>> computer
>>> from the network resart then rejoin the computer to the network. We
>>> have
>>> one computer that will not log onto the local machine at all. This
>>> works
>>> until the next restart. I also noticed that ms has an update 938464v2.
>>> appling this does not change anything

I start a support incident this am and have not hear word one. That is why I
posted here. I had this am only four pc doing this but as of now I have 11

"PA Bear [MS MVP]" wrote:

> Repost, in case you overlooked it:
> > Start a free Windows Update support incident request:
> > https://support.microsoft.com/oas/de...spx?gprid=6527
>
> John Hilton wrote:
> > all are xppro two have sp2 the rest sp3
> >
> > "PA Bear [MS MVP]" wrote:
> >> Please state your full Windows version(s) (e.g., WinXP SP3; Vista SP1)
> >> when
> >> posting to this newsgroup.
> >>
> >> Start a free Windows Update support incident request:
> >> https://support.microsoft.com/oas/de...spx?gprid=6527
> >>
> >> For home users, no-charge support is available by calling 1-866-PCSAFETY
> >> in
> >> the United States and in Canada or by contacting your local Microsoft
> >> subsidiary. There is no-charge for support calls that are associated
> >> with
> >> security updates. When you call, clearly state that your problem is
> >> related to a Security Update and cite the update's KB number (e.g.,
> >> KB938464).
> >>
> >> Support for Windows Update:
> >> http://support.microsoft.com/gp/wusupport
> >>
> >> For more information about how to contact your local Microsoft subsidiary
> >> for security update support issues, visit the International Support Web
> >> site: http://support.microsoft.com/common/international.aspx
> >>
> >> For enterprise customers, support for security updates is available
> >> through
> >> your usual support contacts.
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-Windows (IE, OE, Security, Shell/User)
> >> AumHa VSOP & Admin; DTS-L.net
> >>
> >> John Hilton wrote:
> >>> We have several computer that will no longer logon the domain after
> >>> these
> >>> two updates were applied. The updated don't seem to affect all
> >>> computers.
> >>> The way we worked around this is to boot to the local machine with the
> >>> network cable unpluged uninstall [938464] and 960225, disjoin the
> >>> computer
> >>> from the network resart then rejoin the computer to the network. We
> >>> have
> >>> one computer that will not log onto the local machine at all. This
> >>> works
> >>> until the next restart. I also noticed that ms has an update 938464v2.
> >>> appling this does not change anything
>
>

I understand your frustration but MS PSS will be your best bet, John. No
one here works for or represents MS, including MVPs.

John Hilton wrote:
> I start a support incident this am and have not hear word one. That is
> why
> I posted here. I had this am only four pc doing this but as of now I have
> 11
>
> "PA Bear [MS MVP]" wrote:
>
>> Repost, in case you overlooked it:
>>> Start a free Windows Update support incident request:
>>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>
>> John Hilton wrote:
>>> all are xppro two have sp2 the rest sp3
>>>
>>> "PA Bear [MS MVP]" wrote:
>>>> Please state your full Windows version(s) (e.g., WinXP SP3; Vista SP1)
>>>> when
>>>> posting to this newsgroup.
>>>>
>>>> Start a free Windows Update support incident request:
>>>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>>>
>>>> For home users, no-charge support is available by calling
>>>> 1-866-PCSAFETY
>>>> in
>>>> the United States and in Canada or by contacting your local Microsoft
>>>> subsidiary. There is no-charge for support calls that are associated
>>>> with
>>>> security updates. When you call, clearly state that your problem is
>>>> related to a Security Update and cite the update's KB number (e.g.,
>>>> KB938464).
>>>>
>>>> Support for Windows Update:
>>>> http://support.microsoft.com/gp/wusupport
>>>>
>>>> For more information about how to contact your local Microsoft
>>>> subsidiary
>>>> for security update support issues, visit the International Support Web
>>>> site: http://support.microsoft.com/common/international.aspx
>>>>
>>>> For enterprise customers, support for security updates is available
>>>> through
>>>> your usual support contacts.
>>>> --
>>>> ~Robear Dyer (PA Bear)
>>>> MS MVP-Windows (IE, OE, Security, Shell/User)
>>>> AumHa VSOP & Admin; DTS-L.net
>>>>
>>>> John Hilton wrote:
>>>>> We have several computer that will no longer logon the domain after
>>>>> these
>>>>> two updates were applied. The updated don't seem to affect all
>>>>> computers.
>>>>> The way we worked around this is to boot to the local machine with the
>>>>> network cable unpluged uninstall [938464] and 960225, disjoin the
>>>>> computer
>>>>> from the network resart then rejoin the computer to the network. We
>>>>> have
>>>>> one computer that will not log onto the local machine at all. This
>>>>> works
>>>>> until the next restart. I also noticed that ms has an update 938464v2.
>>>>> appling this does not change anything