Critical Updates Failure / An SEB ???
From: WebDBX.COM Inc (info@WEBDBX.COM)Date: 04/22/02
- Previous message: Mark Boyden: "Non-MS Remote Access to XP Violates License (?!?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 22 Apr 2002 11:48:56 -0400 From: "WebDBX.COM Inc" <info@WEBDBX.COM> To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
An SEB is defined at NTBugTraq as "...Windows NT to react in anything but an expected fashion". As a subscriber to this list, I try to keep the systems for which I am accountable up to par.
The inability to successfully complete installation of a "Critical Windows Update" on Win2K Serv boxes is a bug, leaving a significant exploit. The statement "The following updates were not installed. To try again, click the Back button below" returned by "http://windowsupdate.microsoft.com/" does not benefit the user / administrator. Upon dozens of attempts such a basic message only offers frustration. Did I miss the News Release that Critical Updates were to be used from now on only as forms of entertainment to those whom can be gratified by watching a progress bar?
There must become a method in forcing critical updates to occur. If it is requested, it happens - PERIOD!!!
- Previous message: Mark Boyden: "Non-MS Remote Access to XP Violates License (?!?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]