Cannot Configure Disabled Devices in Device Manager

Last reviewed: January 26, 1996
Article ID: Q132906
The information in this article applies to:
  • Microsoft Windows 95

SYMPTOMS

When you are using a Plug and Play BIOS, you may not be able to configure in Device Manager a device that has been disabled in the BIOS, even though the BIOS supports configuring devices for the next time the computer starts.

When you click the device in Device Manager and then click Properties, you see the following message in the Status box:

   The device has been disabled in the hardware. In order to use this
   device, you must re-enable the hardware. See your hardware
   documentation for details. (Code 29.)

CAUSE

Device Manager does not allow resources to be allocated to devices that are disabled in the BIOS, even if the BIOS supports configuring devices for the next time the computer starts.

RESOLUTION

Enable the device in the BIOS before you try to configure it in Device Manager. For information about enabling devices in the BIOS, please contact your computer vendor or manufacturer.

STATUS

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


KBCategory: kbhw kbenv
KBSubcategory: wpp95 win95 winpnp
Additional reference words: 95 pnp nextboot


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: January 26, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.