MoveFileEx API Does Not Work After Applying SP4

 Last reviewed: March 24, 1997
Article ID: Q149857
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

When you apply Service Pack 4 for Windows NT 3.51 Server or Workstation, the MoveFileEx API stops responding. Files that are marked for deletion or rename upon next restart are not deleted or renamed when you restart the system.

CAUSE

When you use the MoveFileEx API with the MOVEFILE_DELAY_UNTIL_REBOOT parameter, a setup program can mark a file for deletion, or rename, upon the next system restart. This is needed when a specific file is currently in use by the system and cannot be deleted.

The API appears to work, returns the correct error code, and the registry keys are created. However, on restart the files still exist and the registry keys are not deleted.

STATUS

Microsoft has confirmed this to be a problem in Windows NT 3.5 and 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: prodnt movefileex
movefile_delay_until_reboot
Keywords : kbbug3.50 kbbug3.51 kbsetup ntfilesys NTSrvWkst
Version : 3.5 3.51
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.