Error Accessing Boot Sector File \\BOOTSS

Last reviewed: March 20, 1997
Article ID: Q154733
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

If your computer is configured to dual boot into Windows NT version 4.0 and another operating system (such as MS-DOS or Windows 95), you may receive the following error message when you attempt to boot into the non-Windows NT operating system:

   I/O error accessing boot sector file
   Multi(0)disk(0)rdisk(0)partition(1)\\BOOTSS

CAUSE

When your computer is configured to dual boot into Windows NT version 4.0 and another operating system, it uses a hidden file called Bootsect.dos to boot into the non-Windows NT operating system. If the Bootsect.dos file becomes corrupted, or is missing from the root of drive C, you will receive this error.

Note that the Ntldr file displays the erroneous file name Bootss instead of the correct file name of Bootsect.dos.

RESOLUTION

Search for the hidden Bootsect.dos file in the root of drive C. If it is missing, it can be re-created or restored from a recent backup. If it exists, it is probably corrupted. You should delete the file and then re- create it. To do this, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q101789
   TITLE     : Reconstructing Bootsect.dos

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodnt
Keywords : kbbug4.00 kbenv ntboot ntconfig NTSrvWkst
Version : 4.0
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 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.