Archive Bit Is Not Reset When a File Is Renamed

• Microsoft Windows NT Workstation version 4.0
• Microsoft Windows NT Server version 4.0

SYMPTOMS

When you rename a file on an NTFS or FAT partition, the archive bit is not set to indicate the file has changed. As a result, utilities that rely on the archive bit, such as backup utilities, do not correctly handle a renamed file.

CAUSE

This problem occurs because the file system drivers do not set the archive bit when a file is renamed.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following time stamp:

   Intel:
      01/28/98  11:56a               135,536 Fastfat.sys
      10/20/97  10:05p                51,872 Hal.dll
      10/20/97  10:05p                48,288 Hal486c.dll
      01/05/98  02:08p                66,336 Halapic.dll
      10/20/97  10:05p                46,048 Halast.dll
      10/20/97  10:05p                82,144 Halcbus.dll
      10/20/97  10:05p                80,256 Halcbusm.dll
      10/20/97  10:05p                46,336 Halmca.dll
      01/05/98  02:08p                68,448 Halmps.dll
      01/05/98  02:08p                67,488 Halmpsm.dll
      10/20/97  10:06p                78,944 Halncr.dll
      10/20/97  10:05p                40,128 Haloli.dll
      10/20/97  10:05p                56,512 Halsp.dll
      10/20/97  10:05p                40,672 Halwyse7.dll
      01/28/98  12:00p               360,560 Ntfs.sys
      01/26/98  01:42p               938,880 Ntkrnlmp.exe
      01/26/98  01:41p               918,976 Ntoskrnl.exe

   Alpha:
      01/28/98  11:52a               238,928 Fastfat.sys
      01/28/98  12:02p                60,224 Hal.dll
      01/27/98  01:58p                60,224 Hal0jens.dll
      01/27/98  01:58p                81,088 Halalcor.dll
      01/27/98  02:00p                82,528 Halalp.dll
      01/27/98  01:58p                75,968 Halavant.dll
      01/27/98  01:59p                92,576 Haleb164.dll
      01/27/98  01:59p                82,400 Haleb64p.dll
      01/27/98  02:00p                89,824 Halflex.dll
      01/27/98  02:00p                89,568 Halgammp.dll
      01/27/98  01:59p                97,824 Hallego.dll
      01/27/98  01:59p                85,024 Hallx3.dll
      01/27/98  01:59p                79,808 Halmikas.dll
      01/27/98  01:59p                72,256 Halnonme.dll
      01/27/98  01:59p                95,776 Halpinna.dll
      01/27/98  01:59p                71,904 Halqs.dll
      01/27/98  01:59p                99,680 Halrawmp.dll
      01/27/98  01:59p                85,248 Halsabmp.dll
      01/27/98  02:00p                92,320 Haltimbr.dll
      01/27/98  02:00p                89,568 Halxl.dll
      01/28/98  11:57a               555,728 Ntfs.sys
      01/26/98  01:40p             1,399,872 Ntkrnlmp.exe
      01/26/98  01:39p             1,372,416 Ntoskrnl.exe

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.