Article ID: 234339 - View products that this article applies to.
This article was previously published under Q234339
When you run a program that improperly uses an NTFS volume lock function call on a computer running Windows NT 4.0, the volume lock may not be removed after the program has finished running.
The DeviceIoControl() function can be used to lock the volume by specifying FSCTL_LOCK_VOLUME as I/O control code. This function may not work properly if it is called after you perform the following file operations:
Disk Administrator may also be affected as well.
The type of the file is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?
The closed file object is not dereferenced if the closed file was specified as the new file for the MoveFileEx() function before the file cache write process completes. Other file operations other than locking a volume work fine. This is an NTFS-specific problem. FAT volumes are not affected by this problem.
Windows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for 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:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
You can run Clearmem.exe to recover from this problem. The Clearmem utility flushes the section used as file cache, thus the file object in question is dereferenced by running Clearmem. This tool is included in the Microsoft Windows NT 4.0 resource kit.
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 Server version 4.0, Terminal Server Edition Service Pack 6.
Article ID: 234339 - Last Review: June 11, 2012 - Revision: 3.0