0x80070005 is the access-denied error: a file, folder, or registry key the update needs is locked down tighter than the update process can open. It appears at the install stage, after the download completes, and it also shows up when installing apps and drivers for the same underlying reason.
DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Restart afterwards; a repaired store often lets the same update sail through on the next attempt.net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old, then restart the four services with net start. This rebuilds the download cache and the update database from scratch.If the code also appears when installing ordinary apps, the permission damage is wider than Windows Update: run the DISM/SFC step, check the drive for errors with chkdsk /f, and as the last resort do an in-place repair install from Microsoft’s installation media (choose “Keep personal files and apps”), which resets default permissions across the system folders.
Does 0x80070005 mean I have a virus? No. It means access was denied. Malware can change permissions and cause it, and so can over-zealous security or hardening tools, but the code itself is a permissions report, not an infection report. A full scan is a reasonable completeness check, not the main road.
Why does it happen to only one update? Each update touches a different set of files and keys. One locked-down folder or key is enough to fail the update that needs it while others, which never go near it, install normally.