During RRAS setup at a branch, an incorrect modem driver was installed on a Windows 2000 Server. Removing the modem via Phone and Modem Options causes the system to hang each time. You must install the correct driver quickly. What should you do next?

Introduction / Context:
When a faulty or incompatible driver causes the system to hang during removal, the safest remediation is to take the hardware out of the equation so the operating system can boot cleanly and forget the device instance. Windows 2000 will then detect the modem as new hardware on the next insertion, allowing you to load the correct driver.

Given Data / Assumptions:

• Modem driver is incorrect and removal attempts freeze the server.
• The device is on an expansion card (not integrated).
• Rapid recovery is required.

Concept / Approach:

Physical removal prevents the bad driver from initializing at boot. After booting without the device, Windows will drop the active device instance. Re-inserting the card triggers Plug and Play detection; you can then supply the correct driver package. This avoids risky registry edits and repeated system hangs.

Step-by-Step Solution:

Verification / Alternative check:

Device Manager should now show the modem correctly installed without exclamation marks, and RRAS should be able to use it for dial-up.

Why Other Options Are Wrong:

Software removal tools are already shown to hang; repeating with a different wizard may still fail.

Manual registry deletion is dangerous and time-consuming.

The Modem Troubleshooter relies on the same subsystems that are failing.

None: There is a practical, low-risk physical removal path.

Common Pitfalls:

Forgetting to have the correct driver ready; not grounding yourself when handling hardware; reinserting in a different slot may change resource assignments—note the COM port/IRQ if relevant.

Final Answer:

Shut down, physically remove the modem card, restart, then shut down again and reinsert the card to install the correct driver