You are currently offline, waiting for your internet to reconnect

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

This article was previously published under Q192453
This article has been archived. It is offered "as is" and will no longer be updated.
When the MoveFile API is issued from a Windows 95 client with an improperUNC, Windows NT displays a blue screen STOP 0xa error.
When a Windows 95 client sends the MoveFile API call to an incorrect UNCpath, it will return a RENAME SMB with a zero length filename. When thecomputer running Windows NT encounters this RENAME SMB, it displays a bluescreen STOP 0xa error.

A Windows NT client does not exhibit the same behavior because it neversends the zero length filename with the RENAME SMB packet.
The code has been changed to check the length and therefore not crash whena 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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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.

Article ID: 192453 - Last Review: 11/02/2013 17:28:00 - Revision: 2.0

Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbbug KB192453