July Microsoft Update issues

[Steve Garry]

Seems that there's a major problem with this month's updates. 2 machines
done, and problems with both. Only another 10 or so to sort out now.

The first machine was frozen when I got to it this morning, and required a
cold boot to get it back working. That's on XP Home.

The next machine here this evening (XP Pro with multiple user sign on's)
appeared to update and restart correctly, but the fire wall (Zone Alarm)
crashed while loading and produced an error report for onward submission.

Another restart did not clear the problem. I then tried a power down and
restart from cold, which appears to have allowed the machine to load whatever
it needed into the right place, as it did eventually restart and load
correctly.

Based on what I've seen of this, a warm restart is not clearing memory, and
there's something being used without being reloaded, and it's in the wrong
place after the update, and that's screwing things big time. The cold boot
seems to have fixed it, which is not exactly helpful, or productive!


Steve

 

[Merlin]

"Steve Garry" <sgarry@simpilotdotnet> wrote in message
news:42CF7E2A-CFE0-47D3-9E9A-5D2DC08EF0B7@microsoft.com...
> Seems that there's a major problem with this month's updates. 2 machines
> done, and problems with both. Only another 10 or so to sort out now.
>
> The first machine was frozen when I got to it this morning, and required a
> cold boot to get it back working. That's on XP Home.
>
> The next machine here this evening (XP Pro with multiple user sign on's)
> appeared to update and restart correctly, but the fire wall (Zone Alarm)
> crashed while loading and produced an error report for onward submission.
>
> Another restart did not clear the problem. I then tried a power down and
> restart from cold, which appears to have allowed the machine to load
> whatever
> it needed into the right place, as it did eventually restart and load
> correctly.
>
> Based on what I've seen of this, a warm restart is not clearing memory,
> and
> there's something being used without being reloaded, and it's in the wrong
> place after the update, and that's screwing things big time. The cold boot
> seems to have fixed it, which is not exactly helpful, or productive!
>
>
> Steve


No problems here on 2 desktops and 1 laptop.

 

[Uncle Grumpy]

Steve Garry <sgarry@simpilotdotnet> wrote:

>Seems that there's a major problem with this month's updates. 2 machines
>done, and problems with both

Only one done here... and no problems at all.

 

[Lil' Dave]

"Steve Garry" <sgarry@simpilotdotnet> wrote in message
news:42CF7E2A-CFE0-47D3-9E9A-5D2DC08EF0B7@microsoft.com...
> Seems that there's a major problem with this month's updates. 2 machines
> done, and problems with both. Only another 10 or so to sort out now.
>
> The first machine was frozen when I got to it this morning, and required a
> cold boot to get it back working. That's on XP Home.
>
> The next machine here this evening (XP Pro with multiple user sign on's)
> appeared to update and restart correctly, but the fire wall (Zone Alarm)
> crashed while loading and produced an error report for onward submission.
>
> Another restart did not clear the problem. I then tried a power down and
> restart from cold, which appears to have allowed the machine to load
> whatever
> it needed into the right place, as it did eventually restart and load
> correctly.
>
> Based on what I've seen of this, a warm restart is not clearing memory,
> and
> there's something being used without being reloaded, and it's in the wrong
> place after the update, and that's screwing things big time. The cold boot
> seems to have fixed it, which is not exactly helpful, or productive!
>
>
> Steve

Saw only 2 critical updates. One for the newer cpus with microcode
revision. The other, this month's malicious software removal tool. Both
updates worked fine in one PC. Other one, the malicious software removal
tool installation failed. Windows update is downloading it again as I write
this.
Dave