Windows.old preserves files from a previous Windows installation after an upgrade. Remove it through Windows cleanup controls only after you are sure you will not roll back.
Quick answer
Start by identifying which layer is failing
What to do first
The folder is protected because it can support recovery to the previous installation for a limited time. Ownership changes and manual deletion can break cleanup or recovery. Start with the least disruptive test that can separate a local problem from a wider Windows, network, printer, storage, or hardware issue.
Likely causes
What commonly produces this symptom
Common possibilities include rollback window still active; files in use; permissions; pending update; cleanup not run as administrator. The symptom alone does not prove which one is responsible, so use the decision path before changing several things at once.
Diagnostic path
Use evidence before the bigger fixes
Open Settings > System > Storage > Temporary files, select Previous Windows installation(s) only when offered, and read the rollback warning. Alternatively run Disk Cleanup as administrator and choose the clearly labeled previous installation category. Back up important files first.
Record the exact message, when it began, and any update, driver, peripheral, or network change that preceded it.
Test the smallest comparison that applies: another device, account, cable, port, display, printer queue, or power source.
Make one reversible change, restart or retest, and note whether the symptom changes.
Fixes
Work from safest to most invasive
Confirm the current installation is stable; copy personal files you need; run the built-in cleanup; restart and recheck storage; do not take ownership or delete Windows.old from Command Prompt as a first fix.
Use commands only when they match the evidence. An elevated Terminal may run sfc /scannow to check protected Windows files, followed by DISM /Online /Cleanup-Image /RestoreHealth when component repair is justified. Restart and test after the repair.
When to stop
Know when the next step is support
Keep it if you may need rollback or if the current installation is unstable. If cleanup fails with permissions or disk errors, seek support rather than forcing removal. Avoid random registry edits, unknown driver tools, manual deletion of system folders, or a Windows reset simply because the first check did not work.