Document:Windows NT 4.0 build 1381.4 (rc 1.83) Documentary

=
=========================================================             Microsoft Windows NT 4.0 Workstation and Windows NT 4.0 Server Service Pack 3

=
=========================================================

Contents

1.0 Introduction 1.1 What's New in Service Pack 3 1.2 Support for PowerPC Platform 1.3 Downloading and Extracting the Service Pack

2.0 Installation Instructions for Windows NT 4.0 Service Pack 3 2.1 Before you Install the Service Pack 2.2 Installing the Service Pack 2.3 Service Pack Uninstall

3.0 User Notes 3.1 Emergency Repair Disk 3.2 Adding New Components to the System 3.3 Installing Symbol Files from the Compact Disc 3.4 Remote Access Service PPP CHAP MD5 Authenticator Support 3.5 Microsoft DHCP Server 3.6 Unencrypted Passwords No Longer Sent By Default 4.0 List of Bugs Fixed in Windows NT 4.0 Service Pack 3

5.0 Additional Fixes and Work-Arounds 5.1 Tape Drive Not Recognized by Windows NT	5.2 File Sharing Problems with Windows 95

6.0 Notes for Users of the 128-bit Version of Windows NT

7.0 How to Obtain the North American (128-bit) Version of Service Pack 3

1.0 Introduction - Service Pack 3 for Microsoft Windows NT 4.0 is easy to apply from within Windows NT and changes only those files that were originally set up on the Windows NT Workstation or Windows NT Server system. Service Pack releases are cumulative: they contain all previous fixes and any new fixes made to the system.

1.1 What's New in Service Pack 3 - RPC Transport

This service pack includes new versions of the remote procedure call (RPC) run-time dynamic-link library (DLL) and the RPC subsystem service (Rpcss.exe). These changes provide enhanced support for RPC message queuing, which is a feature of the upcoming Microsoft Message Queue Server (MSMQ). In order to use message-queuing in an RPC client/server application on Windows NT 4.0, you must have Service Pack 3 installed on both the client machine and the server machine. You also need Beta 2 or later of MSMQ installed on both the client machine and the server machine.

If you are developing RPC applications that support MSMQ, you need the new RPC run-time DLL, the new RPC subsystem service, and the new RPC header files and MIDL compiler (available in the Win32 SDK). Also, RPC applications must support message queuing in order to use the following new features:

The MIDL [message] attribute.

The ncadg_mq protocol sequence.

The RPC_C_MQ_* endpoint flags in the RPC_POLICY data structure.

The RpcBindingInqOption and RpcBindingSetOption functions.

For more information on using message queuing in your RPC applications, see RPC Message Queuing in the Service Pack 3 SDK Help file (see "Win32 APIs and SDK in Service Pack 3" below), or refer to the documentation in the upcoming MSMQ SDK.

CAPI 2.0

The Microsoft Cryptography application programming interface (CAPI) provides developers with core cryptographic and certificate functions. CAPI 1.0 supports public-key and symmetric-key operations, such as key generation, key management, key exchange, encryption, decryption, hashing, digital signatures, and verification of signatures. CAPI 2.0 (the upgrade contained in this service pack) includes this core cryptographic functionality as well as certificate-based functionality, which is required for developers who want to use certificates with these public-key operations and perform the necessary encapsulations and encoding to apply certificates within their applications.

CAPI 2.0 uses a service-provider model in which cryptography is provided by Cryptographic Service Providers (CSPs). This model allows developers to easily adapt their applications to evolving cryptographic technologies and government export policies. One CSP is provided with this service pack (the Microsoft RSA Base Provider), which gives users and developers access to exportable cryptography.

CAPI 2.0 supports existing standards, such as X.509 v.3 certificate formats, ASN.1 encoding, and both PKCS #7 and #10 for encapsulation. This allows applications using CAPI to interoperate with other certificate-based systems that adhere to these standards.

The release version of CAPI 2.0 includes several updates to the developer's release version of 9/96, including both parameter changes and naming changes. These changes are reflected in the Crypt32.dll and Wincrypt.h files. Please consult the CAPI 2.0 documentation for details.

DirectX 3.0

Service Pack 3 contains a complete software implementation of DirectX 3.0 as well as ongoing hardware support for the DirectDraw component of DirectX 3.0. This translates into the following major feature changes since the release of DirectX 2.0 as supported in Windows NT 4.0:

DirectDraw Access to all 256 entries in the palette when in exclusive mode and some surface alignment changes to support the Direct3D software MMX driver.

DirectSound Software-based 3D localization of audio (Direct3DSound APIs.)

DirectInput COM interface supporting mouse and keyboard data with documentation and sample programs.

DirectPlay IDirectPlayLobby - an interface that allows an external application to launch a DirectPlay 3.0 application and provide it with all information necessary to connect to a session. Internet TCP/IP service provider for multi-player applications over the Internet.

Direct3D Software emulation for the Direct3D 3.0 API. (In Windows NT 4.0, we provide a beta version of the software drivers for Direct3D 2.0.)

ODBC 3.0

This service pack includes the latest version of Microsoft Open Database Connectivity (ODBC) API. ODBC 3.0 provides an updated ODBC Control Panel and ODBC Administrator interface that uses tabbed controls and provides more information about the ODBC components installed and in use on your system. It also introduces the concept of a file data source that can be shared or placed on a central server and used by any user who has the appropriate drivers installed. This new version of ODBC is fully aligned with both the American National Standards Institute (ANSI) and the International Standards Organization (ISO). It is also backward compatible with previous versions of the ODBC API. For more information on ODBC 3.0, refer to the documentation included with the ODBC 3.0 SDK.

SMB Signing

This Service Pack includes an updated version of the Server Message Block (SMB) authentication protocol, also known as the Common Internet File System (CIFS) file sharing protocol. The updated protocol has two main improvements: it supports mutual authentication, which closes a "man-in-the-middle" attack, and it supports message authentication, which prevents active message attacks. SMB signing provides this authentication by placing a digital security signature into each SMB, which is then verified by both the client and the server.

In order to use SMB signing, you must either enable it or require it on both the client and the server. If SMB signing is enabled on a server, then clients that are also enabled for SMB signing will use the new protocol during all subsequent sessions and clients that are not enabled for SMB signing will use the older SMB protocol. If SMB signing is required on a server, then a client will not be able to establish a session unless it is enabled for SMB signing. SMB signing is disabled by default on a server system when you apply the Service Pack; it is enabled by default on a workstation system when you apply the Service Pack.

Note: SMB signing will not work with the direct host IPX protocol. This is because the direct host IPX protocol modifies SMBs in a way that is incompatible with signature-enabled SMBs. This incompatibility will be most obvious when you have direct host IPX clients and you require SMB signing on the server. Requiring SMB signatures on the server will cause the server to not bind to the direct host IPX interface, forcing all connections to the server to be signed. If you disable the NWLink binding on the server then you will be able to use SMB signing.

Also, SMB signing will impose a performance penalty on your system. Although it doesn't consume any more network bandwidth, it does use more CPU cycles on the client and server side.

To configure SMB signing on a server, you must make the following registry changes using Regedt32.exe:

WARNING: Using the registry editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT. Microsoft cannot guarantee that any problems resulting from the use of the registry editor can be solved. Use this tool at your own risk.

1. Go to

HKeyLocalMachine\System\CurrentControlSet\Services\LanManServer\Parameters

2. Add the following values:

Value Name: EnableSecuritySignature Data Type: REG_DWORD Data: 0 (disable), 1 (enable) Note: The default is 0 (disable)

Name: RequireSecuritySignature Type: REG_DWORD Value: 0 (disable), 1 (enable) Note: The default is 0 (disable)

To configure SMB signing on a workstation, you must make the following registry changes:

1. Go to

HKeyLocalMachine\System\CurrentControlSet\Services\Rdr\Parameters

2. Add the following values:

Value Name: EnableSecuritySignature Data Type: REG_DWORD Data: 0 (disable), 1 (enable) Note: The default is 1 (enable)

Name: RequireSecuritySignature Type: REG_DWORD Value: 0 (disable), 1 (enable) Note: The default is 0 (disable)

For more information on SMB signing, see the Microsoft FTP site at ftp://ftp.microsoft.com/developr/drg/CIFS/sec.htm. For general information on the CIFS protocol, see the Microsoft Web site at http://www.microsoft.com/intdev/cifs/.

Win32 APIs and SDK for Service Pack 3

Service Pack 3 includes several new APIs, including two Win32 APIs pertaining to spin counts on critical sections (InitializeCriticalSectionAndSpinCount and SetCriticalSectionSpinCount). To develop applications that take advantage of these new APIs, a Service Pack 3 SDK will be available on the Microsoft Web site at:

http://www.microsoft.com/msdn/sdk

1.2 Support for PowerPC-Based Systems - Microsoft is in the process of phasing out all Windows NT-related development for the PowerPC architecture. Because of this, there are no PowerPC files included in Service Pack 3 for Windows NT 4.0. Microsoft plans to continue providing technical support for customers who use Windows NT 4.0 on the PowerPC architecture.

1.3 Downloading and Extracting the Service Pack --- If you have downloaded this Service Pack from an FTP site or a Web site, you should read the release notes completely before you extract and install the Service Pack.

After downloading the Service Pack, you will have a compressed executable file (nt4sp3.exe) on your hard drive. To extract this file and begin the installation process, type nt4sp3.exe on the command line or double-click the file from NT Explorer. You can also extract the file into the current directory without launching the installation program by using the command line switch /x (for example, on the command line, type nt4sp3.exe /x).

2.0 Installation Instructions for Windows NT Service Pack 3

2.1 Before you Install the Service Pack --- Please close all active debugging sessions before installing this Service Pack, otherwise the Update program will be unable to replace system files that are in use. If a file is in use when you install the Service Pack, a dialog box will appear in which you can choose to cancel the installation or skip the file copy. We recommend you choose to cancel the installation, and then run Update.exe again, being sure to select the uninstall option. Close all active sessions on the system and then rerun Update.exe to install the Service Pack.

Also, to maximize the ability to recover the system in the event of installation failure, it is recommended that you do the following before applying the Service Pack:

1. Update the system Emergency Repair disk using the Rdisk.exe command. 2. Perform a full backup of the system, including the system registry files. 3. Disable any non-essential third-party drivers and/or services (that is, drivers and services that are not required to boot  the system). 4. Contact the Original Equipment Manufacturer (OEM) that provided the driver or service for the updated versions of the file(s).

2.2 Installing the Service Pack --- To install the Service Pack from the compact disc:

1. Insert the Service Pack compact disc into your CD-ROM drive. 2. If a Web page opens in your browser after you insert the compact disc, click Windows NT Service Pack, and then click Install Service Pack. When you are asked whether you want to open the file Spsetup.bat or save it to disk, click Open and then follow the instructions that appear on the screen.

Note: We recommend that you choose to create an uninstall directory the first time you apply the Service Pack. Also, if you are reapplying the Service Pack after installing new software or hardware, you must choose to create a new uninstall directory. To indicate this, you must click "Yes,    I want to create an Uninstall directory" when you are prompted. For further information, see Section 2.3 and 3.2.

3. If a Web page doesn't automatically open when you insert the compact disc, open the Command Prompt window and change the directory to the drive letter associated with the CD-ROM drive. 4. Change the directory to \i386 or \ALPHA (depending     upon whether you have an Intel or ALPHA CPU), and type UPDATE. 5. Follow the instructions that appear on the screen.

Note: We recommend that you choose to create an uninstall directory the first time you apply the Service Pack. Also, if you are reapplying the Service Pack after installing new software or hardware, you must choose to create a new uninstall directory. To indicate this, you must click "Yes,    I want to create an Uninstall directory" when you are prompted. For further information, see Section 2.3 and 3.2.

To install the Service Pack from a network drive:

1. At the Command Prompt, type the command to connect to the network drive on which the Service Pack files reside. 2. Change the drive letter to that network drive. 3. Change directory to \i386 or \ALPHA (depending     upon whether you have an Intel or ALPHA CPU), and then type UPDATE. 4. Follow the instructions that appear on the screen.

Note: We recommend that you choose to create an uninstall directory the first time you apply the Service Pack. Also, if you are reapplying the Service Pack after installing new software or hardware, you must choose to create a new uninstall directory. To indicate this, you must click "Yes,    I want to create an Uninstall directory" when you are prompted. For further information, see Section 2.3 and 3.2.

2.3 Service Pack Uninstall --- This Service Pack contains an uninstall feature that you use to remove the Service Pack from your system. It will restore your system to its previous bootable state.

To enable the uninstall option, you must create an uninstall directory the first time you run Update.exe. To do this, when prompted, click "Yes, I want to create an Uninstall directory." A subdirectory in your Windows NT directory will be created; this requires at least 60 MB of free space on the drive on which Windows NT is installed.

To uninstall the Service Pack, run Update.exe and click "Uninstall a previously installed Service Pack." After your system has rebooted, the Update.exe program will have replaced the files updated by the Service Pack with the files from the previous installation and will have returned your registry settings to what they were before Service Pack 3 was installed.

Note: If you install any applications that require Service Pack 3 or have bug fixes contained in Service Pack 3, performing an uninstall could adversely affect those applications.

3.0 User Notes ---

3.1 Emergency Repair Disk - If it is necessary to use the Windows NT Emergency Repair Disk to repair your Windows NT system at some time after you apply the Service Pack, you will need to reapply the Service Pack after the repair is completed. This is because the Emergency Repair Disk repairs your system by restoring your original Windows NT 4.0 setup. After the repair has completed, simply follow the Installation Instructions (section 2.0 above) to reapply the Service Pack.

3.2 Adding New Components to the System --- If you change or add new software or hardware components to your system after you have applied the Service Pack, you need to reapply the Service Pack. This is because the files taken from the original Windows NT 4.0 disk set may not be the same as the files on the Service Pack disk set. You cannot install new components directly from the Service Pack media (such as a new keyboard or printer driver). You must install new components from the original product media and then reapply the Service Pack.

Note: If you are reapplying the Service Pack after installing new software or hardware, you must choose to create a new uninstall directory. To indicate this, you must click "Yes, I want to create an Uninstall directory" when you are prompted.

3.3 Installing Symbol Files from the Compact Disc - Each program file in Windows NT has a corresponding symbol file that is used to find the cause of kernel STOP errors. To install the symbol files corresponding to the new binaries in Service Pack 3, do the following (assuming your CD-ROM drive is D:, your symbol files are located in the C:\WINNT\SYMBOLS directory, and you are installing the files for an x86 machine):

XCOPY /S /U /D D:\SUPPORT\DEBUG\I386\SYMBOLS C:\WINNT\SYMBOLS

This will copy the Service Pack 3 .dbg files over the existing versions of these files. The XCOPY command shown will copy only those .dbg files that are already installed (/U switch), and only those with a more recent time-date stamp (/D switch).

For more information about debugging on Windows NT, see Chapter 39, "Windows NT Debugger," in the Microsoft Windows NT 4.0 Workstation Resource Kit.

3.4 Remote Access Service PPP CHAP MD5 Authenticator Support

Service Pack 3 provides limited PPP MD5-CHAP authenticator support to the Remote Access Server, which may be useful for small user-count environments using non-Microsoft PPP dial-in clients. The support is local to a given RAS server. The MD5 account information is stored in the RAS server registry and is not integrated or synchronized with the User Manager account database. Integrated support will appear in a later release, at which time this limited support may be removed.

The local MD5-CHAP authenticator is enabled by creating the MD5 key below and adding "account" subkeys of the form [ :] , with subvalue "Pw" containing the account password. The ":" notation is used instead of "\" due to the syntax rules of registry keys. The 'domain:' is optional and typically omitted. MD5-CHAP will not be negotiated (old behavior) when the MD5 key does not exist (default).

HKLM\SYSTEM\CurrentControlSet\Services\RasMan\PPP\CHAP\MD5 [ :] (REG_SZ)Pw

3.5 Microsoft DHCP Server -- This version of the Microsoft DHCP Server modifies the format of the DHCP database. You should back up the contents of your %windir%\system32\dhcp directory prior to upgrading.

The address conflict detection feature can limit the throughput of Microsoft DHCP Server. For improved performance, reduce the number of ping retries in the Server Properties dialog box. This feature is disabled by default.

Address conflicts are indicated by the replacement of the machine name with "BAD_ADDRESS." If a Unique Identifier is specified for the address in the Client Properties dialog box, then the address was declined by the client. If the Unique Identifier is not specified, then the address conflict was detected by the DHCP Server.

Microsoft DHCP Server can be configured to set a client's default gateway equal to its IP address. This causes the client to use the Access Resolution Protocol (ARP) for all IP addresses on the local subnet and is useful for routerless networks. To enable this feature for all clients in a scope, add the following value to the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer \Subnets\a.b.c.d\SwitchedNetworkFlag=1 (REG_DWORD)

This version of Microsoft DHCP Server supports BOOTP clients. BOOTP addresses currently must be reserved in advance by creating an IP address reservation. Future versions of Microsoft DHCP Server will be capable of leasing dynamic addresses to BOOTP clients.

BOOTP clients that do not specify the parameter request list option ( 55 ) can still retrieve the following options from this release of Microsoft DHCP Server:

1	Subnet Mask 3	Router 5	Name Server 12	Host Name 15	Domain Name 44	NetBIOS over TCP/IP Name Server 45	NetBIOS over TCP/IP Datagram Distribution Server 46	NetBIOS over TCP/IP Node Type 47	NetBIOS over TCP/IP Scope 48	X Window System Font Server 49	X Window System Display Manager 69	SMTP Server 70	POP3 Server 9	LPR Server 17	Root Path 42	NTP Servers 4	Time Server

In order to obtain other options, the client must specify option 55 in the BOOTP request. DHCP Server will return the options in the order listed above. DHCP Server will return as many options as will fit in response packet.

The activity log feature creates a text log file of all DHCP Server activity. The file is located at:

%windir%\system32\dhcp\dhcpsrv.log

When the activity log feature is enabled this file will be kept open by DHCP Server while the Server is running. To delete the activity log file you must first stop DHCP Server, using the command:

NET STOP DHCPSERVER

If available disk space becomes low, the activity log will pause until sufficient disk space becomes available.

You must also stop and restart the DHCP Service after enabling or disabling Logging, Superscope, or DHCP Decline support.

3.6 Unencrypted Passwords No Longer Sent By Default --- Connecting to SMB servers (such as Samba) with an unencrypted (plain text) password fails after upgrading to Windows NT 4.0 Service Pack 3. This is because the SMB redirector in Service Pack 3 handles unencrypted passwords differently than previous versions of Windows NT. Beginning with Service Pack 3, the SMB redirector will not send an unencrypted password unless you add a registry entry to enable unencrypted passwords.

To enable unencrypted (plain text) passwords, modify the registry in the following way:

WARNING: Using the registry editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT. Microsoft cannot guarantee that any problems resulting from the use of the registry editor can be solved. Use this tool at your own risk.

1. Run the registry editor (Regedt32.exe).

2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

\system\currentcontrolset\services\rdr\parameters

3. From the Edit menu, select Add Value.

4. Add the following:

Value Name: EnablePlainTextPassword

Data Type: REG_DWORD

Data: 1

5. Choose OK and quit the registry editor.

6. Shutdown and restart Windows NT.

4.0 List of Bugs Fixed in Windows NT 4.0 Service Pack 3

All bug fixes contained in Service Pack 3 are listed below. You can query the Microsoft Knowledge Base to find an article about a specific bug by using the Qxxxxxx number that is assigned to the bug. The Microsoft Knowledge Base can be found on the Microsoft Web site at http://www.microsoft.com/kb/

Service Pack 1 -- Q78303 Intermittent File Corruption Problem Q142653 STOP Message Occurs Calling GetThreadContext/SetThreadContext Q142654 Winsock Memory Access Violation in Ws2help.dll Or Msafd.dll Q142655 Stop Message Appears After Deleting ProductOption Registry Key Q142656 Internet Explorer 3.0 on RISC Computer Cannot Connect to Host Q142657 Data Corruption on Windows NT 4.0 Q142658 Internet Information Server Runs Out of Memory Q149903 File Manager Performs a Move Instead of a Copy Q156832 STOP Message when IBM Warp Client Connects to Windows NT 4.0

Service Pack 2 -- Q108261 Windows NT Hangs on Shutdown with Certain PCMCIA Devices Q140065 Multi-Processor Systems Randomly Restart or Stop Responding Q141375 Winstone 97 May Fail on Windows NT 4.0 Q141708 RAS Client IP Addresses Not Returned to Static Address godot Q142634 Multiple Processes Are Able to Open the Same Winsock Port Q142641 Internet Server Unavailable Because of Malicious SYN Attacks Q142648 STOP 0x00000024 in Ntfs.sys Q142656 Internet Explorer 3.0 on RISC Computer Cannot Connect to Host Q142671 Backup Fails on Certain Directories Due to Lack of Permissions Q142675 CSNW Sends Packets Greater Than Negotiated Maximum Packet Size Q142686 First Line of Print Job Lost When Printing Using Lpdsvc Q142687 Windows NT 4.0 Not Able to Read Some Compact Discs Q142847 Bugcheck 0x1e Caused by Isotp.sys Driver Q142872 Length of PDC Name May Affect Performance on a Domain Q142903 Windows NT Ndis.sys and Netflx3.sys Performance Improvement Q146336 Joystick in Windows NT 4.0 Does Not Work Properly Q147363 AlphaServer Hangs on Install of Windows NT Version 4.0 Q147497 Matrox Video Driver May Fail on Alpha-based Computers Q147552 Backup Always Reports Time as PM Q148378 Setup of RAS with Multiple Modems Gives Slow Performance Q148525 Removable Media Does Not Eject if Formatted in NTFS Q148602 Running SNA Server 2.11 on the Windows NT 4.0 Q150815 Windows NT May Fail to Boot on Toshiba Portable Computers Q153665 SPX Data Stream Type Header May Reset Unexpectedly Q154556 Delegation Requires a Stop and Restart of the DNS Server Service Q154784 Windows NT Operating System SNMP OID Incorrect Q155883 NT 4.0 Breaks SNA Server 2.x Server Communication Over IP Q156091 Access Violation with Long NDS Context in CSNW/GSNW Q156095 Replace Command with Space Character in the Path Does Not Work Q156276 Cmd.exe Does Not Support UNC Names as the Current Directory Q156324 Device Failure Message with Microchannel Network Adapter Q156520 Logon Validation Fails Using Domain Name Server (DNS) Q156578 Cannot Cancel Print Job on Windows NT 3.51 Shared Printer Q156735 WOW Applications Stack Fault When Launched by a Service Q156746 Print Jobs Are Deleted When Printer Is Resumed After Restart Q156750 AddGroupNameResponse Frame from WinNT May Cause WFWG to Hang Q156884 Problems Saving Event Viewer Log from Windows NT 4.0 to 3.51 Q156958 Serial Service Won't Stop with Serial Printer Installed Q157279 Nwrdr.sys Fails Reading File with Execute Only Attribute Q157289 Memory Leak Using RegConnectRegistry API Q157494 PPC 4.0 Cirrus Driver Fails to Redraw & Fill Objects Correctly Q157621 Personal Groups Not Visible If %Systemroot% Is Read-Only Q157673 Policy Not Updated on Workstation Q158142 WM_DDE_EXECUTE API Causes a Memory Leak in the WOW Subsystem Q158387 RAS Server Cannot Use DHCP to Assign Addresses w/ PPTP Filtering Q158587 16-Bit Named Pipe File Open Leads to WOW Access Violation Q158682 Shortcuts Created Under NT 4.0 Resolve to UNC Paths Q158707 DDE Destroy Window Code May Stop 0x0000001e in Windows NT 4.0 Q158796 Macintosh Clients Connected to WinNT Server Appear to Hang Q158981 IBM Thinkpads 760ED and 760ELD May Hang During Shutdown Q158994 Windows NT 4.0 Fails to Replicate to Backup Domain Controllers Q159053 NTFS Stream Limitation in Windows NT 4.0 Q159066 A Client Crash May Prevent an NTFS Volume Dismount Q159071 NTFS Does Not Prevent a File Deletion During Rename Q159072 An Account That Still Has System Access May Be Deleted Q159073 Screen Corruption on Dell Laptops Using Cirrus Video Q159075 Compression Is Not Supported on Quantum 4000DLT Q159076 Windows NT 4.0 May Hang or Crash in Win32k.sys During Setup. Q159085 Windows NT Kernel Crashes While Processing WM_NCCREATE Q159090 Delphi 2.00 and 2.01 Users Encounter Error 998 Q159091 German Time Zone Results in Incorrect Log Times Q159092 Mouse Buttons Not Swapped on German Windows NT 4.0 Q159093 Windows NT Muldiv Function Returns Incorrect Value Q159095 STOP 0x0000001E in Win32k.sys When Exiting Applications Q159098 WinNT 4.0 Resource Kit Utility "Remote Console" Client Fails Q159105 Cannot Open Truncated File Names from Compact Discs Q159107 Access Violaion in AddAtom Inside Kernel32.dll Q159108 SMP Full Duplex Adapter Configuration May Cause a Blue Screen Q159109 ExitWindowsEx Does Not Work With NEC Power Switch Service Q159110 CDFS Does Not Complete IRPs Correctly Q159111 Multiprocessor Computer Hangs Under Stress Using Halsp.dll Q159119 NTFS Generates Cross-Linked Files Q159127 Bugcheck in Windows NT While Running POSIX Applications Q159129 OpenGL Access Violation with Invalid OpenGL Context Q159137 Moving Files Can Corrupt NTFS Partition Q159141 CDFS Incorrectly Creates Short File Names for Some Files Q159144 Dongle May Not Function Under Windows NT 4.0 Q159203 Unattended Install Prompts for New IP if Zero Is in Address Q159204 IoCompletionPort Causes Blue Screen Error Q159205 SFM File Type and Creator Properties Invalid Q159206 Reactivation of Paused Print Queues Deletes Print Jobs Q159309 Windows NT 4.0 RAS Not Releasing Static IP Addresses Q159352 RPC over NetBIOS Programs Can't Call from Server to RAS Client Q159447 Applications Testing for Directory Existence Fail Q159449 DNS Server Glue Data Is Deleted Q159450 Second Recursive Query Sent from DNS Server Is Broken Q159594 Missing Eastern Europe FontSubstitutes in Registry Q159910 Memory Corruption on a Windows NT Alpha Platform Q159970 Slow List of Folders and Files with CSNW Q159971 SetTimer API Causes Memory Leak in the WOW Subsystem Q159972 WinNT 4.0 May Not Return Valid Response for SMB Search Command Q160015 2D Vector Performance on WinNT 4.0 Slower Than on 3.51 Q160055 Warning Event ID 4010 Generated on Windows NT LPD Server Q160189 CSNW Cannot See More Than 32 Volumes Per Server Q160190 RasSetEntryProperties Does Not Save a Full Path Script Name Q160354 Mouse and Keyboard Can Disappear when Replacing Drivers Q160370 Stop Screen 0x00000050 Caused by Fs_rec.sys Q160372 Intermittent File Corruption when Compiling on NTFS Partition Q160373 Adaptec Aic78xx Does Not Issue Multiple Tagged Commands Q160377 File Size Data Does Not Remain Consistent After Defrag on NTFS Q160392 Systems with 4 GB or More of RAM Cannot Boot Windows NT 4.0 Q160398 Cannot Read Files Greater than 4 GB Q160404 Madge EISA Stops Responding on Alpha in Windows NT 4.0 Q160405 Video Memory Not Correctly Detected on Dell Latitude Laptops Q160420 Changing Colors on Cirrus Logic Cards to 65k Can Cause Stop Q160459 DNS Delegations May Fail Q160470 Stop 0x0000000a IPX Sends Browser an Incomplete Datagram Q160493 NWLNKRIP Data Structures Corruption when Using a Demand Dial NIC Q160494 DNS Zone Transfer Fails After WINS Record Added Q160497 Cache File Entries Disappear Q160508 Unnecessary DNS Zone Transfers Q160518 Zone Files in Multiples of 4 KB May Cause Access Violation Q160583 Windows NT 4.0 with More Than 4 Processors May Stall & Reboot Q160601 Bad Parameters Sent to Win32k.sys May Cause Stop Message Q160603 No Output from DBMON Using OutputDebugString While Debugging Q160604 Access Violation in security!SspQueryContextAttributesW Q160606 Performance Enhancements for SQL Server Under Windows NT Q160610 READ_REGISTER_ULONG Doesn't Preserve ULONG Semantics on Alpha Q160649 STOP 0x0000000A in Ntoskrnl.exe at Logon to Windows NT 4.0 Q160650 Blue Screen When Closing Kernel Mode Handles from User Mode Q160651 OpenGL May Cause an Exception 0xc0000090 Q160653 NTFS Fails Assertion Under High Stress During Transfer Q160657 16-bit Version of Visual Basic 4 May Hang Windows NT 4.0 Q160658 Stop C0000021A Using MoveFileEx MOVEFILE_DELAY_UNTIL_REBOOT Q160670 FPSCR is Not Being Saved Across Thread Context Switches Q160671 Stop 0x0000007F May Occur on Compaq SystemPro Q160678 Possible Access Violation in Win32k.sys Under High Stress Q160702 Event 2006 Errors in Xcopy from WinNT 4.0 to OS/2 3.0 Client Q160732 FIX: SQL Server 6.5 Service Pack 2 Fixlist (Part 2 of 2) Q160791 Excel Charts Lose Color When Pasted into Word Q160840 Sharing Violation When Accessing User Profiles Q160894 Incoming Fax Jobs Do Not Appear in Print Queue Q160964 0x0000001e When Printing Certain Documents from Windows NT 4.0 Q161201 NTBackup.exe from WinNT 3.51 SP5 Causes Verify Errors Q161802 Stop 0x0000000A During Create File SMB Q161990 How to Enable Strong Password Functionality in Windows NT Q162157 Cyberbit Unicode Font Does Not Return Correct Charset Q163055 DHCP Client May fail with NT 4.0 SP2 Multinetted DHCP Server Q163736 Access Violation in DNS Manager when deleting cached domain Q163772 Nested "for" Loops Using the '~' Operators Does not Work Q163773 Brief 3.0 in NTVDM Consumes 100% Processor Q163837 SNMP query to Windows NT returns same value for NTS and NTW

Service Pack 3 --- Q135707	Programs Run at Priority Level 15 May Cause Computer to Hang Q141189	BUG: Wrong Error Code on NetBIOS Call When Using NWNBLNK Q142047	Bad Network Packet May Cause Access Violation (AV) on DNS Server Q147012	Activating /W Switch to Prevent Rebooting in WinNT Q149538	System Restarts Every 5 Hours if Workstation to Server Upgrade Q151926	Delayed WinLogon When Drive Mapped to Local Share Q153220	DHCP Manager Error "No More Data Is Available" Q154710	Cannot View Long File Names on Network in 16-Bit Programs Q154939	CreateQueueJobAndFile Fails w/ Queues Other Than Print Queue Q156410	STOP 0x1E or 0x50 Error on Multiprocessor DEC Alpha Computer Q157077	Netstat Slow to List Large Numbers of Connections Q158433	Re-creating Admin Shares Causes Exception Error Q158548	Sysdiff Changes Dates on Files It Applies to WinNT Q159060	Mouse Cursor Freezes with Microsoft IntelliMouse Q159176	XADM: Store Stops Responding with High CPU Usage Q159330	Map.exe Does Not Set Environment Variables Correctly Q159998	Error Message: Error Access Is Denied Q160386	Incorrect MediaType Parameter on IBM PCMCIA Token Ring Card Q160405	Video Memory Not Correctly Detected on Dell Latitude Laptops Q160990	DHCP Server Offers Duplicate IP Addresses for Windows NT Q161038	Winsock Apps Fail on First Attempt at NetBIOS Name Resolution Q161368	Service Pack 2 May Cause Loss of Connectivity in Remote Access Q161432	WINS Static Entries Overwritten by Duplicate Group Names Q161644	STOP 0x0000000A Sfmsrv.sys When Copying File to Mac Volume Q161714	IPX Doesn't Function Correctly over Token Ring Source Routing Q161830	Message from Unix Using Smbclient w/ Long Username Crashes Q161838	Programs That Lock 0 Bytes at Byte 0 Lock Entire File Q162077	Stop: 0x0000000A when Selecting NDS Map Objects Q162096	SET: Drivers Fail to Load When I/O Address Is Above 0xFFF Q162189	Macintosh Clients May Hang Temporarily with Multiple Mac Volumes Q162404	Service Pack 5 Breaks Microsoft Mail Shared Using FPNW Q162471	NT 4.0 May Not Recognize Scsi Devices That Use Non-zero LUN's Q162479	Poor Performance with Chips & Technologies Video Accelerator Q162563	WINS Restore Fails on Windows NT Server 4.0 Q162567	Telnet to Port 135 Causes 100 Percent CPU Usage Q162616	Extra Form Feed with Passthrough Functions to Text Only Driver Q162657	Choosing Default Domain Name for RAS Client Authentication Q162775	Access Violation in SPOOLSS when Printing to a Serial Printer Q162778	WINS May Report Database Corruption w/ More Than 100 Owners Q162881	RIP Table Sent While Shutting Down When Silent RIP Set Q162926	STOP: 0x0x0000000A After Call to GlobalAddAtom Q162927	Telnetting to Port 53 May Crash DNS Service Q163143	STOP: 0x0000001E with Status C000009A Q163202	Limit of the Number of Simultaneously Open Root Storage Files Q163203	Remote Access Autodial Manager may fail for second user logon Q163213	WebSTONE Benchmark of IIS May Show Poor Results for MP Systems Q163214	RAS Script with "set ipaddr" may fail with 3Com Defender Add-on Q163261	DEC ALPHA WinNT 4.0 Servers w/ SP2 Fail to Lease DHCP Addresses Q163267	Delay While Establishing SPX II Connection Q163318	Helpfile Word Lists May Be Rebuilt After Daylight Savings Change Q163333	Autosynch Compatible COM Applications May Fail w/ FIFO Enabled Q163383	Failure to Obtain IP Address Via DHCP on Token Ring w/ SP2 Q163431	16-Bit Application Stops Responding When Run on WinNT 4.0 Q163508	STOP 0xA in Ntfs.sys During Reboot Q163512	Error: The Mapi Spooler has Shut Down Unexpectedly Q163525	Delay When Saving Word 7.0 File to Windows NT 4.0 Server Q163538	NTBackup Does Not Properly Eject Tapes on DLT Tape Devices Q163614	HP LaserJet Series II Prints Extra Small Stripes or Points Q163620	Stop 0x50 in RDR.SYS If Pathname Too Long in SMB Q163672	Windows NT 4.0 Setup Fails on ThinkPad 535 Q163700	IIS Access Violation for Polygon with More Than 100 Vertices Q163714	SET: ATDISK Finds the Same Disk Twice on SunDisk PCMCIA ATA Ad Q163725	NDIS Driver Fails To Check Functional Address Q163790	RPC Service Stops Responding on UDP Port 135 Q163872	Sysdiff Cannot Delete Files Q163873	Czech Keyboard Layout Has Wrong Mapping Q163874	Hitting CTRL-ALT-DEL During Logon Can Cause Blue Screen Q163876	CSNW Clients Cannot Delete Print Jobs on Netware Print Queue Q163880	COPY Command Causes File Cache to Grow Q163881	Windows NT Does not Display Some Fonts Q163883	NetBT (tag=Nbt8) Corrupts Pool with WinNT 4.0 SP2 Installed Q163891	Excel97 Causes NT to Access Violate Q163892	A Service May Not Set Hooks on 32-bit GUI Applications Q163936	CLOCK Hangs and Consumes 90% CPU When Set to Digital Display Q163969	Event 552: DNS Was Unable to Serve a Client Request Q164014	Slow Exchange Client Logons Due to Deadlock in LSASS Q164121	App: Corel Fonts Unavailable Outside of English Locale Q164133	DOM: Logon Allowed When Access Denied to Mandatory User Profile Q164138	Files in MAC Volume Disappear from MAC clients Q164159	When restoring a tape backup, verify reports errors Q164161	NTBACKUP Fails to backup Exchange IS server data Q164201	Access Violation Installing IIS Q164211	FPNW Doesn't Convert the Long File Names Correctly Q164260	Compressing and Uncompressing Files Causes File Cache to Grow Q164309	Windows NT client: Primary/Secondary WINS Servers Switch Q164322	Memory leak in NetQueryDisplayInformation API Q164350	NEC IDE CD-ROM CDR-1400C Cannot Play Audio Compact Disks Q164352	Stop 0x00000050 in TCPIP.SYS Caused by Winsock Applications Q164391	NT V4.0 SP2 atapi claims an IRQ for an unused IDE channe Q164432	Accented Greek Characters Are Not Being Created Q164462	Conner 4mmDAT Tape Devices Fail After About 30 Seconds Q164491	Stop: 0x0000000A in RDR.SYS When Mailslot Message > 512 Bytes Q164507	Any User Can Logon to FTP Server with Disabled Anonymous Logon Q164542	MGET to an IBM Host FTP Server Returns Garbage Characters Q164546	SCSI Driver Description Truncated in Control Panel Q164595	Duplicate Route Not Removed After Second Redirection Q164600	4mmDATDriver Reports DEC TZ9L Supports Setmarks Q164606	Deferred Reconnections to Share Level Password Shares May Not Work Q164630	RPC over NetBEUI Fails from Windows NT 4.0 RAS to NT 4.0 RAS Q164631	Scavenging WINS Database Removes Static Entries Q164639	SNA Windows 95 Fails Logon if Password Change Required Q164806	CHKNTFS Does Not Exclude FAT Partitions from AUTOCHK on Boot Q164812	Computer Name Truncated When Name Resolution Attempted Q164821	DHCP Server Service May Hang Q164826	Direct Draw Programs May Hang NT 4.0 with S3 968 Video Chipset Q164928	Not All Objects Are Displayed When Browsing NDS Trees Q164938	Event Logging Frozen While Doing Heavy Logging; Services CPU Peg Q164982	Lack of Secondary Address May Cause DNS Service to Hang Q164987	Hard-coded Socket of 451 Causes LANtegrity Software to Fail Q165004	NTVDM Support for COMPAQ Financial Keyboard Scan Codes Q165245	APP: SP3: DDE server disconnect Q165314	Grace Logon Remaining Is Not Decremented When Logging to BDC Q165388	Invalid Directory Returned When Attempting to Access FPNW Q165427	CONVLOG.EXE May Cause Access Violation Q165443	NDS Login Script Fails When Checking "If Member Of" Q165456	STOP 0x0000000A in NTOSKRNL.EXE Q165483	RasEnumEntries API leaks memory

For the latest information on bug fixes see:

Q150734 List of Bugs Fixed in Windows NT Version 4.0

5.0 Additional Fixes and Work-Arounds

5.1 Tape Drive Not Recognized by Windows NT --- In some instances, after you apply the Service Pack, Windows NT will not be able to load the drivers for a tape drive, which may cause the tape drive to shut down or be inoperable. This is due to a conflict between the ATAPI driver that controls IDE devices and the tape drive controller. To fix the problem, you must set your tape drive controller to a different I/O address.

In most circumstances, your tape drive controller will be set to use I/O address 0x3F0-0x3F8. However, the ATAPI driver uses I/O address 0x3F6. If your tape drive controller has been assigned to 0x3F6, then you must assign the tape drive controller to an available address.

5.2 File Sharing Problems with Windows 95 - In some instances, you may experience "out of memory" problems when you save a file to a shared folder on a Windows 95 machine. You can obtain a fix for this problem at the following Microsoft Web site:

http://www.microsoft.com/visualc/download/mfc42cab.htm

6.0 Notes for Users of the 128-bit Version of Windows NT

All encryption-related components in this version of Service Pack 3 are limited to exportable 40-bit cryptography. During installation, you will be prompted when an existing component on your system containing 128-bit encryption is about to be replaced by an updated component with 40-bit encryption. If you require 128-bit support, you should click the "Skip" button on the dialog box when prompted during Service Pack setup. A version of this Service Pack with 128-bit encryption is available on request. See ordering information below.

Microsoft Internet Explorer supports both 40-bit and 128-bit encryption depending on the version (40-bit or 128-bit) of the file Schannel.dll. If you accidentally overwrite the 128-bit version of Schannel.dll with the 40-bit version included in this Service Pack, you can copy the original from your Windows NT Version 4.0 compact disc into the windir%\system32 directory to restore it.

7.0 How to Obtain the North American (128-bit) Version of this Service Pack --- The North American (128-bit) version of Service Pack 3 is intended for distribution only in the United States and Canada. Export of the North American version of this Service Pack from the United States is regulated by the International Traffic in Arms Regulations (ITAR, 22 CFR 120-130) of the U.S. State Department, Office of Defense Trade Controls. A State Department license is required to export the North American version of Service Pack 3 outside the United States or Canada.

Microsoft will distribute the North American (128-bit) version of Service Pack 3 to U.S. or Canadian companies or persons for end-use in the U.S. or Canada only.

Ordering Information and Availability:

Customers in the 50 United States and Canada can order the North American (128-bit) version of Service Pack 3 effective 4/30/97 for US $14.95 (CDN $20.95) plus customer service and handling charges of US $5 (CDN $7.50). Customers can order the product by phone or mail.

By Phone or Fax: Call (800) 370-8758 or Fax to (716) 873-0906 US, (905) 374-3855 Canada. The 800 number is for customers calling in the U.S. and Canada.

By mail in the 50 United States:

Microsoft Service Pack 3 PO Box 810 Buffalo, NY 14207-0810

By mail in Canada: Microsoft Service Pack 3 PO Box 643 Fort Erie, ON L2A 6M1 Canada

Be sure to request Part Number 236-00791. The product will be delivered within four weeks.