MoveFile API from Windows 95 with Invalid UNC Causes STOP 0xa
Article ID: 192453
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q192453
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, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is 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: kbbug KB192453