Windows XP Pro Newbie

[Thomas Grassi]

Last night windows update downloaded and update to windows installer



Event Type: Information
Event Source: Windows Installer 3.1
Event Category: None
Event ID: 4377
Date: 5/19/2005
Time: 3:01:13 AM
User: NT AUTHORITY\SYSTEM
Computer: TGKW001
Description:
Windows Installer Hotfix KB893803v2 was installed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

It then automatically restarted my computer. That's not cool.
Then these errors appeared while trying to restart

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 5/19/2005
Time: 3:13:17 AM
User: N/A
Computer: TGKW001
Description:
The Computer Browser service terminated with the following error:
This operation returned because the timeout period expired.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: sr
Event Category: None
Event ID: 1
Date: 5/19/2005
Time: 8:31:17 AM
User: N/A
Computer: TGKW001
Description:
The System Restore filter encountered the unexpected error '0xC000011E'
while processing the file 'Dump.ini' on the volume 'HarddiskVolume2'. It
has stopped monitoring the volume.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 00 00 00 00 04 00 4e 00 ......N.
0008: 00 00 00 00 01 00 00 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........



First any ideas on why windows restarted by itself? Second why did I get
these errors after restart? Event id 7023 I created a new check point
record after I got back on to my computer.



Thanks Tom

 

[PA Bear]

Default behavior after installing any update needing a reboot is for user
(you) to be asked if he wants to reboot now or not. You may have accepted
the prompt to reboot thinking your were just saying OK to finishing the
install...or Windows may indeed have rebooted on it's own. Stuff happens.

That being said and despite the errors you encountered upon rebooting, is
everything OK now?

 

[traxx]

Hi Robear, hi Tom

Well, we encounter the sam problem. Just to say "Stuff happens" is a
inacceptable way to deal with this problem, since we have to deplo
KB893803v2 to some thousand PCs.
And even when it's launched by script with the /norestart option, thi
darn thing reboots the machine.
We didn't get an answer from Microsoft til today, and we have to find
way to deploy.
In my eyes, it's just a new bug, ver.2, delivered by Microsoft.

By all means, if anyone has an idea how to solve this problem - i
would be highliy appreciated!

krgrds,
Michael