Using FDISK /MBR for Troubleshooting Windows NT Boot Problems (166454)
The information in this article applies to:
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
This article was previously published under Q166454 SUMMARY
In Microsoft Windows NT, using the MS-DOS FDISK /MBR command is not
always appropriate when you cannot boot a computer. The problem is that
the command rewrites the master boot record (MBR) only, and not the
entire boot record. The FDISK /MBR command rewrites only the first 446
bytes of the master boot record, not the partition table. Windows NT
disk signatures used for fault tolerance are also overwritten, and if
the drive contained an FT member, it may not be recognized by Windows NT
as an FT member afterward.
If a drive is infected with a Stealth virus, the partition table and
pointers have been offset. The offset pointer is contained in the MBR.
Using the FDISK /MBR command on the computer refreshes the MBR--the
pointer to the partition table is lost, as is the ability to boot. The
only possible solution is to reinfect the drive and then try to remove
the virus again using Fdisk or anti-virus software.
The only time that the FDISK /MBR command is effective against a virus
is if it is a boot-sector-only virus (such as the Stoned virus).
If the sector is infected, recovery cannot be guaranteed. If the FDISK
/MBR command is used and a Stealth virus is present, the computer can
most likely not be recovered because the offsets are not constant.
Examples of Stealth viruses include:
- NY Bomber or NYB
- Stealth.B
- Hare
- Monkey.B
Modification Type: | Major | Last Reviewed: | 5/14/2003 |
---|
Keywords: | kb3rdparty kbother KB166454 |
---|
|