Skip to main content

Whyreboot example 1: IE 5.5 patch, Windows Update

Internet Explorer 5.5 Patch, Windows Update Service

After installing a recent Internet Explorer 5.5 patch using the online Windows Update service, I was prompted to reboot my computer. I ran WhyReboot version, and received the following report:

WhyReboot Version
Exodus Development, Inc.

NOTE: These results may not reflect all pending operations,
and you should use your own good sense in deciding whether
to reboot your computer after an install.

Windows NT, 2000, XP, or variant


REGISTRY: PendingFileRenameOperations
> DELETE C:\WINNT\Temp\OLD155.tmp
> DELETE C:\WINNT\Temp\OLD154.tmp
> RENAME C:\WINNT\System32\SET169.tmp to C:\WINNT\System32\WININET.DLL
> RENAME C:\WINNT\System32\SET16B.tmp to C:\WINNT\System32\SHDOCVW.DLL
> RENAME C:\WINNT\System32\SET16D.tmp to C:\WINNT\System32\URL.DLL
> RENAME C:\WINNT\System32\SET171.tmp to C:\WINNT\System32\MSHTML.DLL
> RENAME C:\WINNT\System32\SET173.tmp to C:\WINNT\System32\URLMON.DLL
REGISTRY: PendingFileRenameOperations END.

> 012: "C:\WINNT\System32\regsvr32.exe /s C:\WINNT\System32\mshtml.dll"
in Global RunOnce registry

8 items were found and reported.


So, it's clear from the above report, that I should reboot my computer in order for the changes to take effect -- several core IE files will be renamed after rebooting. It's probably not safe to continue using the computer until a reboot has taken place.