If there are no actual Windows symptoms beyond some slowdown, those “corrupted ZIP archive” results from Norton 360 are not enough by themselves to conclude that Windows is damaged.
Two relevant points from the available guidance:
- Third-party antivirus scans can report archive-related issues or performance problems during scanning, especially with CAB/ZIP-style archives. Microsoft documents that scanning archive files such as
.ZIPor.CABcan degrade scan performance. - Microsoft guidance for Windows file corruption is to verify system files with System File Checker, not to manually delete Windows files based only on an antivirus archive warning.
Recommended path:
- Open Command Prompt as administrator.
- Run:
sfc /scannow - Wait until verification reaches 100%.
- Check the result:
- “Windows Resource Protection did not find any integrity violations.” → no missing or corrupted protected system files were found.
- “Windows Resource Protection found corrupt files and successfully repaired them.” → Windows repaired them.
- “Windows Resource Protection could not perform the requested operation.” → run the scan in safe mode and make sure %WinDir%\WinSxS\Temp contains PendingDeletes and PendingRenames.
- “Windows Resource Protection found corrupt files but was unable to fix some of them.” → review the SFC details and replace the affected file manually with a known good copy.
Important:
- Do not delete Windows archive or system files just because Norton flagged them during that scan.
- If the issue is only scan-time slowdown, archive scanning itself can contribute to that.
- If Norton was run from a command-line style scan at
C:rather than its normal UI, that does not by itself mean Microsoft needs to update or remove files.
Based on the available information, Windows should handle repair of protected system files through SFC. Norton is responsible only for its scan results and behavior; it should not be used as the basis for manually removing Windows files.