1. Record the machine before changing it
Capture model, CPU, RAM, GPU, storage, Windows edition/build and network hardware. That gives the sale description a factual baseline and prevents later confusion about what was actually tested.
2. Start read-only
Check Device Manager problem devices, Windows Update state, Defender state, installed applications, startup entries, scheduled tasks, relevant services, storage health and repeating Event Viewer errors before removing software or reinstalling drivers.
3. Repair the symptom, not the whole PC
If Windows reports that a control panel or driver component is missing, inspect the installed driver model and supporting components first. Broad reinstalls can hide the original cause and create new variables.
4. Debloat conservatively
Remove obvious trialware, obsolete launchers and unneeded OEM utilities only when their role is understood. Do not remove hardware drivers, Windows security components, Store infrastructure needed by driver packages or shared runtimes simply because they look unfamiliar.
5. Check the basics a buyer will notice
- GPU and display output
- audio
- LAN or Wi-Fi as fitted
- USB ports
- storage free space and basic health
- Windows activation
- reboot behaviour
- idle CPU/load after cleanup
6. Reboot and read back
Rebooting is part of the test. Recheck problem devices, startup processes, security status and the specific issue you repaired. A clean session is stronger evidence than a desktop that only looked healthy before restart.
7. Remove the support path before handover
Temporary services, rescue media, test folders, exclusions and remote-access authority must be removed. Verify the endpoint is offline from the support system rather than assuming cleanup succeeded.
Reusable resale playbook
- Inventory hardware and Windows.
- Run a read-only health audit.
- Resolve actual driver/software faults.
- Debloat conservatively.
- Check activation, security and updates.
- Run a practical hardware/stability test.
- Reboot and independently read back the state.
- Remove temporary support artefacts and remote authority.
- Produce a concise factual handover report.
What recent physical work taught us
Across several physical sale-prep sessions, the visible complaint was rarely the whole job. One machine surfaced an NVIDIA control-panel problem; another had a background process driving CPU load close to 100% until an unnecessary runtime path was stopped. The useful procedure is therefore broader than fixing the first notification.
The final deliverable should be a verified machine state plus a playbook that makes the next resale audit more systematic.