Re: 4 patches won't install - 835732, 840987, 828035, 824105

From: Steve Burkett (NetService_at_Configuration.sucks)
Date: 02/15/05 

Date: Tue, 15 Feb 2005 16:18:06 -0000

Have managed to replicate the 840987 problem on an HP DL380 G4, 1 proc,
running Win 2003 Standard (non-upgrade), joined to domain but not a DC,
running Terminal Services and Kaspersky Antivirus 4.5.

Am now trying to track down what the problem is.

Did find on another post though that if you install kb840315 and kb841533
and then reboot, the kb840987 patch disappears from the available critical
patches list.

"Ronald Nissley" <Ronald Nissley@discussions.microsoft.com> wrote in message
news:53BE16A2-CCDE-4CBF-A018-227EC258F5D0@microsoft.com...
> In early January, our two servers were upgraded from Windows 2000 Server
> Standard to Windows 2003 Server Standard. They are both Dell Poweredge
> 2600
> servers with similar hardware configurations. Both are configured as
> domain
> controllers (same domain). After upgrading, I ran windows update to check
> for/install critical updates. On the one server, the updates installed
> with
> no problems. On the other, I've been able to install all patches but 4:
>
> 835732 - MS04-011
>
> This patch includes an update to schannel.dll, but freezes when installing
> this file. A hard shutdown is necessary, and upon restart, the file is
> missing. It can be restored from the server CD and requires a reboot.
>
> 840987 - MS04-032
>
> Same deal as above, but this time it's ntoskrnl.exe that goes AWOL. Also,
> to
> restore this file, I have to boot to the recovery console...the os has a
> bit
> of a problem booting without a kernel. :-) For this one, I restore
> I386\ntkrnlmp.ex_ to winnt\system32\ntoskrnl.exe.
>
> 828035 - MS03-043
>
> Again, same deal except this time it's wkssvc.dll. This is required by the
> workstation service and causes lots of problems since a lot of other
> services
> depend on the workstation service.
>
> 824105 - MS03-034
>
> I'm getting repetitive stress syndrome! This time it's a file needed by
> NetBIOS, c:\winnt\system32\drivers\netbt.sys.
>
> For each of these patches, and entry shows up in add/remove programs. I
> haven't attempted to remove, then re-install these patches. I have tried
> to
> install the patches several times with the same results.
>
> The installation logs can be viewed here:
>
> http://e.1asphost.com/ronaldnissley/835732.txt
> http://e.1asphost.com/ronaldnissley/840987.txt
> http://e.1asphost.com/ronaldnissley/828035.txt
> http://e.1asphost.com/ronaldnissley/824105.txt
>
> If you've experienced this and found a workaround, please let me know.
> Suggestions are also welcome. For the Microsoft folks out there, I've done
> a
> bit of searching on the Net and it doesn't appear that I'm alone in my
> troubles, so however you can help me may very well help others as well.
>
> Thank you,
>
> Ronald Nissley

Relevant Pages

  • Re: SBS 2003 will not boot up
    ... Then I reboot the server BEFORE installing any patches, ... Then I install patches. ...
    (microsoft.public.windows.server.sbs)
  • Re: changing root password with Knoppix?
    ... You WILL backup ONLY the files you MUST keep from this server. ... You WILL install all vendor patches before running any services (preferably ... to the Slackware lists alerting me of new patches with the new server ...
    (comp.os.linux.security)
  • Re: Install Ent as Standard, on Win2K or WinXPro Ive Does this before... but
    ... the Standard Edition won't install on Windows XP Pro ... Windows Server 2003, Standard Edition ...
    (microsoft.public.sqlserver.setup)
  • Re: Sharepoint Error: Cannot connect to the configuration database error
    ... It looks like you have a standard version with only have MSDE ... When you go to START/PROGRAMS do you see a SQL Server reference? ... full SQL CD you can also install the tools on your SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Actual differences between Standard and SBS
    ... No biggie but SBS comes in two flavours ... Possibly by referring to vanilla W2K with the term 'standard' we'll ... of processes which more than likely ned to run on the only server these guys ... > install Standard on all servers and then change some of them to SBS to ...
    (microsoft.public.windows.server.sbs)