Service Pack Upgrade Issues

 Last reviewed: May 16, 1997
Article ID: Q115161
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SUMMARY

This article addresses effects to system enhancements, third-party software, and unexpected results after you upgrade your system with a Microsoft U.S. Service Pack for Windows NT.

MORE INFORMATION

System Enhancements

The upgrade to a Service Pack should have no effect on post-installation enhancements of Windows NT services, such as FTP Server. No special considerations are required for Microsoft-supplied optional features for Windows NT.

Third-party Software

On the contrary, special considerations are required for third-party software that replaces or adds files with the same name as Windows NT system files.

The only known instance of this is vendor-provided Hardware Abstraction Layers (HALs). When you have a special HAL from an original equipment manufacturer (OEM), you need to reinstall that HAL after you run the Service Pack Update program. UPDATE.EXE reads the SETUP.LOG file and if it sees that the system used HALSP.DLL, for example, when it was originally set up, it will copy that file from the Service Pack over the top of the HAL.DLL resident on the hard disk. In this situation, install the Service Pack and copy the HAL supplied by the third party back onto the hard disk before you shut down and restart your computer.

Unexpected Results

As with any modification of system software, proper care should be taken in preparing for unexpected problems. For Windows NT, this includes having the following before you make any modifications:

  • A tape backup of the machine's data.
  • A backup of the disk configuration.
  • A backup of the Registry.

If a serious problem arises after you install a Service Pack, do the following:

  1. Use the Emergency Recovery Disk. This returns Windows NT to the original condition ("as installed" format).

  2. Restore the Registry.

  3. If necessary, restore the disk configuration.

  4. If appropriate, reinstall the Service Pack and any additional software.

This can be done in situations where the problem is not believed to be inherent to the Service Pack itself. An example of this kind of situation would be neglecting to reinstall third-party software after you install the Service Pack and before system shutdown. Another example would be a power failure when you are installing a Service Pack.

Additional query words: prodnt ntas sp1 sp2
Keywords : kbother ntdistrib
Version : 3.1
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.