Hi Amira Hamid,
Persistent high CPU utilization between 90 and 100% during idle states indicates an operational loop within the Windows subsystem, frequently tied to background service corruption or driver misbehavior. Isolating this requires bypassing the generalized Processes tab in Task Manager and moving to the Details tab to sort by the CPU column. This exposes raw executable behavior, allowing you to identify if a specific system binary like SearchIndexer.exe, which governs the Windows Search service, or TiWorker.exe, the Windows Modules Installer Worker, is failing to release processor threads. If the resource drain is instead dominated by System Interrupts, the processor is stuck handling continuous hardware requests, a behavior heavily documented in Microsoft diagnostics as a symptom of a malfunctioning device driver.
When a native service like Windows Update or indexing is the culprit, the root cause is often corruption within the local Windows component store. To resolve this, administrative privileges are required to run deployment verification tools directly through the command line interface. Executing the command DISM.exe /Online /Cleanup-image /Restorehealth targets the image management deployment engine, comparing local system binaries against an official cloud-based manifest and repairing hidden corruption. Following this with the system file checker command, sfc /scannow, forces Windows to scan and replace altered or damaged protected system files, effectively breaking the processing loops causing the resource bottleneck.
Domic V.