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

Article translations Article translations
Article ID: 192453 - View products that this article applies to.
This article was previously published under Q192453
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

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.

Properties

Article ID: 192453 - Last Review: November 2, 2013 - Revision: 2.0
Applies to
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug KB192453

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com