Any issues with this month's patches?

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

I installed this month's patches on my desktop running XP Pro SP2. Upon
reboot after installing the patches my desktop goes into a perpetual reboot.
I get this even with all of the Safe Mode settings. I get the XP splash
screen and then it shows the color of my desktop and reboots.

On my laptop, XP Pro SP2, I installed the patches and saw the same issue.
Fortunately it booted into safe mode and I was able to do a restore.

Anyone else seen this? These are company machines with legit licenses.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Hi Guys

I have a user name problem with XP
I added my wife’s profile to the start up along with mine, if I log into my
account .all is find…..but when I want to log into her account……XP windows
allows this for a slit second and than automatically goes back to the user
accounts at the start up…then I cant get back into either accounts…..only
thing to do is reboot..All is find again. Same thing her end…log into her
profile and I have the same problems going back to mine

Any one knows how to rectify this
All help appreciated

 

[map]

Archived from groups: microsoft.public.windowsxp.general (More info?)

The Frustrated Monk wrote:
> I installed this month's patches on my desktop running XP Pro SP2.
> Upon reboot after installing the patches my desktop goes into a
> perpetual reboot. I get this even with all of the Safe Mode settings.
> I get the XP splash screen and then it shows the color of my desktop
> and reboots.
>
> On my laptop, XP Pro SP2, I installed the patches and saw the same
> issue. Fortunately it booted into safe mode and I was able to do a
> restore.
>
> Anyone else seen this? These are company machines with legit licenses.

It is best to wait a week or two before you install the lastest patches,you
have just figured out why.

--
Mike Pawlak

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Hmmmm..

>
> It is best to wait a week or two before you install the lastest
patches,you
> have just figured out why.
>
> --
> Mike Pawlak
>

It is my impression that industry Best Practices related to security pretty
much require that you implement (or at least evaluate) security patches
right away or else risk giving a hacker/cracker more than ample time to
exploit the flaw you are ignoring in the interim.

For this reason, we try it first (hopefully in a lab environment) ASAP, and
then ask questions to those 'in-the-know' when it creates issues. Usually
waiting is NOT an option in a security-minded atmosphere, and I believe that
no systems professional should be advocating a 'wait-and-see-approach' to
security.

Just my 2 cents.

Keith C. Jakobs, MCP

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

This is my first issue with any MS patch ever.

Still trying to figure this one out.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

"Keith Jakobs, MCP" <elohir@NOSPAM.hotmail.com> wrote in message
news:Oi2rNOenFHA.1204@tk2msftngp13.phx.gbl...
> Hmmmm..
>
>>
>> It is best to wait a week or two before you install the lastest
> patches,you
>> have just figured out why.
>>
>> --
>> Mike Pawlak
>>
>
> It is my impression that industry Best Practices related to security
> pretty
> much require that you implement (or at least evaluate) security patches
> right away or else risk giving a hacker/cracker more than ample time to
> exploit the flaw you are ignoring in the interim.
>
> For this reason, we try it first (hopefully in a lab environment) ASAP,
> and
> then ask questions to those 'in-the-know' when it creates issues. Usually
> waiting is NOT an option in a security-minded atmosphere, and I believe
> that
> no systems professional should be advocating a 'wait-and-see-approach' to
> security.
>
> Just my 2 cents.
>
> Keith C. Jakobs, MCP
>
>

You might head off some trouble by subscribing to the Windows Secrets
newsletter (by Brian Livingston). If he publishes a report about a bad patch
before you get bitten, it'll be worth the price of the newsletter, which, by
the way, if free.
www.windowssecrets.com

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

"=?Utf-8?B?VGhlIEZydXN0cmF0ZWQgTW9uaw==?=" <TheFrustratedMonk@discussions.microsoft.com> writes:
>I installed this month's patches on my desktop running XP Pro SP2. Upon
>reboot after installing the patches my desktop goes into a perpetual reboot.
>I get this even with all of the Safe Mode settings. I get the XP splash
>screen and then it shows the color of my desktop and reboots.

>On my laptop, XP Pro SP2, I installed the patches and saw the same issue.
>Fortunately it booted into safe mode and I was able to do a restore.

>Anyone else seen this? These are company machines with legit licenses.

Last night the ITsafe team,

ITsafe Team
Making IT safe for You
http://www.itsafe.gov.uk
The UK Alerting and Advisory Service for Information and Communications
Technologies (ICT) Security

sending out warnings about security threats to Microsoft Windows
installations, told of three critical updates to Windows.

A few hours later they reversed their advice with:

ITsafe Bulletin 2005/013A - UPDATE Number 1

What is it?
===========
Bulletin 2005-BUL-013 was issued on Tuesday 9th August, and related to
Microsoft Security Bulletin MS05-038 - a problem with "Microsoft Internet
Explorer" browser. Since then Microsoft have reported there have been
problems experienced with downloading the updates, and that they have been
temporarily removed. In addition, our UNIRAS partners report that
attempts are being made to use the problem fixed by this vulnerability to
attack computers.

What do I do?
================
Hold off updating your copy of Internet Explorer until the revised
download becomes available from Microsoft. ITsafe will issue an update
when this is available, and Microsoft's various automated update services
if enabled on your computer will detect the new update once re-released.

 

[map]

Archived from groups: microsoft.public.windowsxp.general (More info?)

>I believe that
>no systems professional should be advocating a 'wait-and-see-approach' to
>security.

In the two years that I've been coming to this group I have NEVER stated
that I was anykind of systems pro, are you one of those people that add or
remove words to fit what you want to here instead of what was said?

For the average pc user such that I am, a good firewall,disabling unneeded
services and praticing safe hex,will carry you the few weeks my advice will
take,sometimes these fixes are worst than what their trying to patch!
Case in point is this thread.

Mike Pawlak



Keith Jakobs, MCP wrote:
> Hmmmm..
>
>>
>> It is best to wait a week or two before you install the lastest
>> patches,you have just figured out why.
>>
>> --
>> Mike Pawlak
>>
>
> It is my impression that industry Best Practices related to security
> pretty much require that you implement (or at least evaluate)
> security patches right away or else risk giving a hacker/cracker more
> than ample time to exploit the flaw you are ignoring in the interim.
>
> For this reason, we try it first (hopefully in a lab environment)
> ASAP, and then ask questions to those 'in-the-know' when it creates
> issues. Usually waiting is NOT an option in a security-minded
> atmosphere, and I believe that no systems professional should be
> advocating a 'wait-and-see-approach' to security.
>
> Just my 2 cents.
>
> Keith C. Jakobs, MCP

 

[map]

Archived from groups: microsoft.public.windowsxp.general (More info?)

I want to thank you for being one of the guinea pigs that test out the
newest hotfixes for me!

--
Mike Pawlak




Keith Jakobs, MCP wrote:
> Hmmmm..
>
>>
>> It is best to wait a week or two before you install the lastest
>> patches,you have just figured out why.
>>
>> --
>> Mike Pawlak
>>
>
> It is my impression that industry Best Practices related to security
> pretty much require that you implement (or at least evaluate)
> security patches right away or else risk giving a hacker/cracker more
> than ample time to exploit the flaw you are ignoring in the interim.
>
> For this reason, we try it first (hopefully in a lab environment)
> ASAP, and then ask questions to those 'in-the-know' when it creates
> issues. Usually waiting is NOT an option in a security-minded
> atmosphere, and I believe that no systems professional should be
> advocating a 'wait-and-see-approach' to security.
>
> Just my 2 cents.
>
> Keith C. Jakobs, MCP

 

[kelly]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Try the updates group.

> I installed this month's patches on my desktop running XP Pro SP2.

1. Why?
2. news:microsoft.public.windowsupdate

--

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com



"The Frustrated Monk" <TheFrustratedMonk@discussions.microsoft.com> wrote in
message news:27623709-3178-4265-A531-3E8CCD44E57D@microsoft.com...
>I installed this month's patches on my desktop running XP Pro SP2. Upon
> reboot after installing the patches my desktop goes into a perpetual
> reboot.
> I get this even with all of the Safe Mode settings. I get the XP splash
> screen and then it shows the color of my desktop and reboots.
>
> On my laptop, XP Pro SP2, I installed the patches and saw the same issue.
> Fortunately it booted into safe mode and I was able to do a restore.
>
> Anyone else seen this? These are company machines with legit licenses.