KB977816 fails to apply to 2000 server
in [Windows Update]
|
From: azntch on 18 May 2010 15:00 That doesn't seem to make sense as this kb977816 is listed as a security update by Microsoft yet see: http://www.microsoft.com/technet/security/Bulletin/MS10-026.mspx. It says its related to codecs: This security update resolves a privately reported vulnerability in Microsoft MPEG Layer-3 audio codecs. The vulnerability could allow remote code execution if a user opened a specially crafted AVI file containing an MPEG Layer-3 audio stream. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003 (except Itanium-based editions), and Windows Server 2008 (except Itanium-based editions). For all supported editions of Windows Vista, this security update is rated Important. Itanium-based editions of Windows Server 2003 and Windows Server 2008, and all supported editions of Windows 7 and Windows Server 2008 R2, are not affected by the vulnerability. For more information, see the subsection, Affected and Non-Affected Software, in this section. The security update addresses the vulnerability by correcting the way that the Microsoft MPEG Layer-3 audio codecs decode the MPEG Layer-3 audio stream in specially crafted AVI files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information. -- thanks for your help "Peter Foldes" wrote: > Then you have the same issue and the same answer from me. > > Microsoft lost the case which was brought against them by Sun Microsystems for using > their technology. The agreement was that MS will discontinue Support (which was done > at a very early stage ) and stop all aspects of Windows 2000 including updates. This > was completed at some point last year by MS. In essence Windows 2000 in all flavors > is dead as far as updating among others > > -- > Peter > > Please Reply to Newsgroup for the benefit of others > Requests for assistance by email can not and will not be acknowledged. > http://www.microsoft.com/protect > > "John" <a> wrote in message news:%23aFxPRq9KHA.5592(a)TK2MSFTNGP02.phx.gbl... > > > > "Peter Foldes" <maci252211(a)hotmail.com> wrote in message > > news:uM7kv0j9KHA.508(a)TK2MSFTNGP06.phx.gbl... > >> You can see this yourself if you try and download that file manually. It will not > >> download. > > > > I just downloaded it from here: > > http://www.microsoft.com/downloads/details.aspx?familyid=F6394FC2-B9D0-46CF-9265-A0D4AEB1448F&displaylang=en > > > > Apparently the update is still available. I'm having the same problem as OP but > > mine is a Win2000 Pro machine. > > > >> Windows 2000 and all updates for it in essence is dead. Microsoft pulled it from > >> their sites according to the agreement between Sun and the DOJ > > > > What agreement? > > > > . >
From: Robert Aldwinckle on 18 May 2010 17:19 "azentech2" <azentech2(a)discussions.microsoft.com> wrote in message news:186E9874-EF9D-4DAE-BD85-E306812B328A(a)microsoft.com... > KB977816 fails to apply to 2000 server. After server reboots, update > reappears and asks to be installed. I have noted that tech support has > asked > for the windowsupdate.log and the updateshandler.log in other incidents. > The > windows update.log is below, however I did not find an updateshandler.log > (or > anything close) on the server. > I did find the KB977816.log and that also follows. Did you try opening a support case for this yet? (PA Bear's advice.) Otherwise, I don't think there is enough information in these logs. FWIW what I would do is run ProcMon to supplement whatever diagnostics you can force the install to give you, e.g. add a /verbose switch (if there is one) and do a manual install. http://www.microsoft.com/technet/security/bulletin/MS10-026.mspx There is one. Expand. [-] Security Update Deployment [-] Windows 2000 (all editions) [-] Deployment Information A small puzzle is why all these switches are so different from the ones which are documented? ; ) > 0.062: Hotfix started with following command line: -q -z -er http://support.microsoft.com/kb/262841 -z would imply /norestart so why were you getting a reboot? > The following is from the windowsupdate.log : > 2010-04-21 03:07:11:866 1156 488 AU Clearly from the wrong end. ; ) Hint: if you do a manual install you won't need to consider this log. Tip: before you do the reboot check what it is going to do for you. E.g. check the install log, the Event log (e.g. using Event Viewer) and the registry value PendingFileRenameOperations. Check the versions of all of the files implied by those diagnostics and confirm that they make sense. After the reboot check again using the same information to confirm that the update has completed. Good luck Robert Aldwinckle ---
From: Harry Johnston [MVP] on 19 May 2010 19:16 On 2010-05-18 3:50 p.m., Peter Foldes wrote: > This has been reported many times in different newsgroups. The Update or > any Update for Windows 2000 will not install since the install file has > been pulled.It still shows but it is an empty file .You can see this > yourself if you try and download that file manually. It will not > download. Windows 2000 and all updates for it in essence is dead. > Microsoft pulled it from their sites according to the agreement between > Sun and the DOJ I think you're thinking of a different update. Harry. -- Harry Johnston http://harryjohnston.wordpress.com
From: azntch on 21 May 2010 14:28
What is odd is all the switches etc - were just from the sus client doing the automatic update. We didn't tell it to do anything in particular. Just to do the downloads and reboots at a certain time each week. I have opened a support case but have not received much in response yet. Will post when I do. The problem I run into is that these are vital servers, so I need to schedule the work well in advance, So probably will be trying something this coming week - judy not exactly sure what yet. Am hoping I will get a response from support - if so I will post the relevant detail here. thank you "Robert Aldwinckle" wrote: > > > "azentech2" <azentech2(a)discussions.microsoft.com> wrote in message > news:186E9874-EF9D-4DAE-BD85-E306812B328A(a)microsoft.com... > > > KB977816 fails to apply to 2000 server. After server reboots, update > > reappears and asks to be installed. I have noted that tech support has > > asked > > for the windowsupdate.log and the updateshandler.log in other incidents. > > The > > windows update.log is below, however I did not find an updateshandler.log > > (or > > anything close) on the server. > > > I did find the KB977816.log and that also follows. > > > Did you try opening a support case for this yet? (PA Bear's advice.) > > Otherwise, I don't think there is enough information in these logs. FWIW > what I would do is run ProcMon to supplement whatever diagnostics you can > force the install to give you, e.g. add a /verbose switch (if there is one) > and do a manual install. > > http://www.microsoft.com/technet/security/bulletin/MS10-026.mspx > > There is one. Expand. > [-] Security Update Deployment > [-] Windows 2000 (all editions) > [-] Deployment Information > > A small puzzle is why all these switches are so different from the ones > which are documented? ; ) > > > 0.062: Hotfix started with following command line: -q -z -er > > > http://support.microsoft.com/kb/262841 > > -z would imply /norestart so why were you getting a reboot? > > > > The following is from the windowsupdate.log : > > > 2010-04-21 03:07:11:866 1156 488 AU > > > Clearly from the wrong end. ; ) Hint: if you do a manual install you > won't need to consider this log. > > Tip: before you do the reboot check what it is going to do for you. E.g. > check the install log, the Event log (e.g. using Event Viewer) and the > registry value PendingFileRenameOperations. Check the versions of all of > the files implied by those diagnostics and confirm that they make sense. > After the reboot check again using the same information to confirm that the > update has completed. > > > Good luck > > Robert Aldwinckle > --- > > > . > |