MoveFile API from Windows 95 with Invalid UNC Causes STOP 0xa

SYMPTOMS

When the MoveFile API is issued from a Windows 95 client with an improper UNC, Windows NT displays a blue screen STOP 0xa error.

CAUSE

When a Windows 95 client sends the MoveFile API call to an incorrect UNC path, it will return a RENAME SMB with a zero length filename. When the computer running Windows NT encounters this RENAME SMB, it displays a blue screen STOP 0xa error.

A Windows NT client does not exhibit the same behavior because it never sends the zero length filename with the RENAME SMB packet.

RESOLUTION

The code has been changed to check the length and therefore not crash when a zero length filename is encountered.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Microsoft has confirmed this to be a problem in Windows NT version 3.51.

Keywords : NT4SP4Fix ntstop kbbug4.00 kbfix4.00.sp4
Version : WinNT:3.51,4.0,5.0
Platform : winnt
Issue type : kbbug