The correct answer is C. Switch the NIC settings from manual to automatic, which allows the computer to obtain an IP address dynamically from the DHCP server. When a static IP address is no longer required, reverting the network configuration to DHCP ensures the system integrates properly with the current network design.
According to the Quentin Docter - CompTIA A+ Complete Study Guide, DHCP simplifies network management by automatically assigning IP addresses, subnet masks, gateways, and DNS settings. Leaving a static IP in place can cause address conflicts or connectivity issues, especially when the device is repurposed.
The Travis Everett & Andrew Hutz - All-in-One Exam Guide explains that DHCP reservations are used when a device must always receive the same IP address, which is unnecessary in this scenario. Creating exclusions or manually changing the static IP does not meet the requirement to remove static addressing altogether.
The Mike Meyers / Mark Soper Lab Manual reinforces that switching the NIC to automatic configuration is the correct way to return a system to standard network operation and avoid manual IP management.
Because the static IP is no longer needed, enabling DHCP by setting the NIC to automatic configuration is the correct solution, making C the correct answer.

Virtualizationallows the legacy OS to be run in a virtual machine (VM) on top of the newer OS. This method provides backward compatibility without requiring outdated operating systems on physical hardware.
FromQuentin Docter - CompTIA A+ Complete Study Guide:
"Using virtualization is a preferred method when legacy applications are needed after migrating to newer operating systems. It allows legacy environments to exist securely within a modern OS framework."

When DHCP isn't enabled, static IPs must be assigned manually, so the engineering team provides the IP details.
FromTravis Everett - All-in-One Exam Guide:
"If DHCP is unavailable, technicians need the static IP configuration to connect devices to the network." .

When a system begins randomly crashing after a hardware change (installing a GPU) and the correct vendor driver update does not resolve it, the best next troubleshooting step is to collect evidence about what is failing.
Windows records crash details, driver faults, and unexpected shutdowns in Event Viewer (System/Application logs) and related reliability tools. Quentin Docter specifically states that Event Viewer should be the first place you look when the solution is not evident because applications and the OS often create log entries that help verify operation and diagnose problems. These logs can reveal whether the crash is tied to a display driver fault, power/kernel events, or another subsystem. Docter also notes you can often find more information about application crashes by reviewing the Application log, and for instability/shutdown patterns you "start combing through the logs" in Event Viewer to determine whether the system lost power or crashed.
Mike Meyers adds that Event Viewer is the tool used to read and understand Windows logs (Application
/System/Setup/Security) for diagnosing what's happening on a system.
References: Quentin Docter - CompTIA A+ Complete Study Guide (Event Viewer as first stop; crash
/shutdown investigation via logs); Travis Everett & Andrew Hutz - CompTIA A+ All-in-One Exam Guide (Event Viewer logs and event levels for troubleshooting); Mark Soper - Mike Meyers' A+ Lab Manual (Event Viewer and the "big four" Windows logs).

A repeated failure to open Task Manager -a core Windows troubleshooting utility-strongly suggests the system is compromised and critical tools are being interfered with. In malware-response methodology, Quentin Docter emphasizes that the first step is to "identify and verify the malware symptoms" before proceeding to containment and remediation. If Task Manager cannot be launched at all, that behavior itself is a highly suspicious symptom consistent with malicious activity attempting to prevent the administrator from viewing or stopping processes.
Docter also explains that when systems are compromised by a virus or other malware, the threat agent may embed persistent access methods, and in some cases the only way to be sure it's fully removed is to reinstall the OS-highlighting how deeply malware can integrate and disrupt normal tools.
The other options do not plausibly block Task Manager: a developer application may increase CPU/RAM usage but typically won't prevent Task Manager from opening; Windows Update set to manual affects patching behavior; and moving the pagefile can affect performance but not usually stop Task Manager from launching.