Cannot Rename System File in Windows Explorer
Microsoft Knowledge Base Article When you try to rename a system file (such as Kernel32.dll - in Windows Explorer by using the Rename command, you receive the following error message: Cannot rename Kernel32.dll: The specified file is being used by Windows However, you can rename the system file at the command prompt or shell by typing the following line:command ren kernel32.dll kernel32.old 

Drive Mapping May Time Out on a Windows 2000-Based Computer 
Microsoft Knowledge Base Article: 297684 - When you perform drive mapping from a Windows 2000-based client computer to either a Microsoft Windows NT or Windows 2000 network share, the drive mapping may be disconnected after 15 minutes of inactivity and Windows Explorer may display a  red "X" on the icon of the mapped drive. However, if you attempt to access or browse the mapped drive, it reconnects quickly. 

Explorer.exe Still Shows Files on a Mounted Volume After Being Deleted 
Microsoft Knowledge Base Article: 272061 - If you are a member of the Administrators group, you can use Disk Management or the Mountvol.exe command, to connect, or mount a local drive on any empty folder on a local NTFS volume. 

File Security (Inherited) Permissions May Be Removed When You Remotely Edit the Permissions 
Microsoft Knowledge Base Article: 304140 - When a drive is mapped to a share point of a server and you edit the remote NTFS file system permissions, any existing inherited permissions are removed and only explicit permissions remain. 

File That Is Larger Than Four Gigabytes Appears to Be Zero Bytes in Windows Explorer Microsoft Knowledge Base Article: 318484 - When you use Windows Explorer to view the size of a file that is larger than 4 gigabytes (GB), the file size may appear to be zero. 

File Version Information May Be Incorrect in Windows 2000 Multilanguage Version
Microsoft Knowledge Base Article: 263212 - After you apply a hotfix or service pack to Windows 2000 Multilanguage version, the file version that is displayed in Windows Explorer (when you right-click a file in Windows Explorer and then click Properties) may be incorrect. 

Invalid File Handle Error Messages When You Use Remote Files and a Sharing Violation Occurs 
Microsoft Knowledge Base Article: 284247 - When multiple users try to access the same file and file open attributes are not set to allow sharing, the file may be closed out from under a thread that successfully opened the file. When this occurs, the thread tries to access the file with a file handle of 0xFFFF. There error returned to the program is error 6, which maps to ERROR_INVALID_HANDLE 

Slow Network Performance Occurs If You Copy Files to a Windows 2000 Domain Controller
Microsoft Knowledge Base Article: 321098 - If you copy files from a Windows 2000-based or a Microsoft Windows XP-based client computer to a network share on a Windows 2000-based domain controller, network performance is slower than if you copy the same files to a Windows 2000-based member server. You may notice this problem if you copy many small files; however, you may not notice this problem if you copy a few large files. This problem only occurs if you either use Microsoft Windows Explorer to copy the files or if a Windows Explorer window is open and connected to the target server. However, if you use Xcopy.exe to copy the files and all of the Windows Explorer windows are closed, you do not experience this problem. 

Slow Network Performance Occurs When You Select a File on a Share That Uses NTFS 
Microsoft Knowledge Base Article: 265396 - When you select a file on a network share that uses an NTFS file system partition, extra Server Message Block (SMB) packets are sent on the wire. This behavior causes overall slow network performance. The same issue occurs if you browse the network, and you position the mouse cursor over one of the files; however, this issue does not occur if you use a Microsoft Windows NT 4.0-based client computer

Slow File Write from Windows 2000 to Windows NT 4.0 Server
Microsoft Knowledge Base Article: 279282 - The file-copy write process from a Windows 2000 Professional-based computer to a Windows NT 4.0 Server-based computer may take up to four times longer than reading the same files from Windows NT Server. 

The DIR Command Displays Wrong Information for the Date and Time of a File 
Microsoft Knowledge Base Article: 314048 - File times on Windows 2000 are stored as a FILETIME value. This is a 64-bit value that represents the number of 100-nanosecond intervals since January 1, 1601 (UTC). Windows 2000 also supports time-zone adjustments. Time-zone adjustments are accomplished by adding a time-zone offset to the UTC time to compute local time. Time-zone offsets range from -12 hours (International Date Line West) to +13 hours (Nuku'alofa).

The "My Documents" Folder Is Not Refreshed Correctly When It Is Redirected to a NetWare Server 
Microsoft Knowledge Base Article: 285897 -  If you have redirected the My Documents folder to a NetWare server and you delete files from the folder, the files do not disappear from the folder until you refresh the view manually.

The Windows Explorer Progress Bar May Be Misleading When You Move or Copy Large Files 
Microsoft Knowledge Base Article: 326429 - If you move or copy a large file (five gigabytes [GB] or larger) by using Windows Explorer, the progress bar may give a misleading status. The progress bar moves right until it reaches the end and then jumps back to the beginning many times. Also, the time remaining is random (from a few minutes to millions of minutes). However, the file is moved or copied successfully if you do not cancel the operation. 

You Cannot Set the User Home Folder Path When You Receive an Error Message After You Create the Folder 
Microsoft Knowledge Base Article: 285547 - When you assign a home folder to a user, the new information is not set to the user account and you may receive the following error message: The home folder could not be created because: Access is denied The information after the colon (:) in the error message may vary, depending on the cause of the problem

You May Not Be Able to Copy Large Files on Computers That Are Running Windows NT 4.0 or Windows 2000
Microsoft Knowledge Base Article: 259837 - When you try to copy a large file, you may not be able to and you may not receive an error message.