During a scheduled maintenance window you update the NIC driver on a Windows Server 2022 file server to resolve intermittent iSCSI disconnects. After the reboot the original disconnects remain and new driver-related warnings appear in the System event log. No other changes have been made yet. According to the CompTIA troubleshooting methodology, which action should you take next?
Roll back to the previous NIC driver, verify stability, and then test an alternative corrective action.
Leave the new driver installed and open an immediate support ticket with the hardware vendor.
Replace the physical NIC with a newer model while keeping the current driver version.
Apply all remaining Windows and firmware updates in case one resolves the issue.
Because the single change you implemented did not fix the problem and introduced new symptoms, the methodology dictates rolling the system back to its last known-good state before trying something else. Restoring the previous NIC driver removes the ineffective change, returns the server to a stable baseline, and lets you test a different fix one step at a time. Installing additional updates, replacing hardware, or escalating without first reversing the failed change would create multiple variables or leave an unverified configuration in place, making root-cause analysis harder and risking further outages.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.