Full Scan Getting Stuck or Working Very Slowly

Norton 360 for Windows
21

Hey @bjm -So we meet again. A few days ago I went to run my weekly full scan. It got stuck at around 90%. I tried quick scan. Same thing. Now a couple of days later, the full scan will complete after roughly 4x longer to run than normal. Since I have an ongoing investigation going (as you might remember) all the way back to October with V24, their tech just happened to call me. He said Norton knows about the scanning issues and is working on a fix. We’ll see!
Meanwhile my list of 7 things wrong starting with V24 is still an on going investigation. They will not admit it has anything to do with their software. Totally an uphill battle as you know my friend.
I’ll let you know if my scanning issue returns to Normal. I’m thinking it was caused by a bad live update.

1 Like
22

Thanks! for sharing.

Have you tried any Troubleshooting? Repair Norton?
fwiw ~ I’ve clean re-installed 25.5.x

23

@bjm- No sir. Ever since V24 came out, I’ve read every post on both threads. I’ve seen what lengths people have gone through to make this junk work right. Nobody fixed it by re-installing or running the ‘fix it’ tool. So I took a different approach and found myself finally getting all the way up to Level 3 Support. Now, what has that accomplished so far??? NOTHING. So I just assume that although things like cloud backups, or VPN’s don’t work for some, UDP (17) repeating in Security History, someone a lot smarter than I thought of turning off ‘NetBIOS’ solved that problem. I assume that the program as “A good protector” seems to function well though. So for a big discount I chose to remain, and Ride The Storm Out. (REO Speewagon). Cheers!

24

I hear ya’.
I’m agreeing with ya’.
fwiw ~ I’ve clean re-installed v24.x…too.
fwiw ~ Norton 360 v25.5.10141 (build 25.5.10141.934) feels okay…my side.

1 Like
25

@bjm – If I never looked within my security history, I would have no idea anything was wrong with V24 and up. I’m thinking that most people download this program, run it, and that’s that. They don’t even set preferences. It’s all automatic. I don’t like all automatic. I like to know when I get updates. But like you BJM and other folks, we dig too deep.

26

Windows update is the problem.

I had the same issue. This is what fixed it for me.

Open Terminal as administrator and type

dism /Online /Cleanup-Image /CheckHealth
if it says there is corruption found type

dism /Online /Cleanup-Image /RestoreHealth
(this may take some time)

Finally type
sfc /scannow

Restart your computer

Now your scans will go back to normal.

This issue was happening to me
after I did this my full scan went from 3 hours back to 5 minutes.

1 Like
27

Sorry for responding to myself but this is a windows issue not a norton issue.
Same thing was happening to hitmanpro and some other apps I have on my PC.

If you have no idea about DISM and SFC I can probably try and answer them.

1 Like
28

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Question regarding sfc and dism and System Performance | ElevenForum

What is the correct order of DISM and SFC commands to fix problems | TenForums

Note: recommended run sequence varies

==========================================================

How to Repair Corrupted Windows System Files with the SFC and DISM Commands | How-ToGeek

Using SFC and DISM to correct file corruption | Malwarebytes Forums

Note: recommended run sequence varies

=============================================================

AI Overview
SFC (System File Checker) and DISM (Deployment Image Servicing and Management) are Windows tools used to repair corrupted or missing system files. SFC is a command-line utility that scans and replaces damaged Windows files with cached versions, while DISM is a more comprehensive tool that can repair the Windows component store and the system image itself. If SFC finds errors and cannot repair them, DISM can be used to repair the underlying system image.

System File Checker (SFC):

  • Purpose:
    Scans and repairs corrupted or missing Windows system files.

  • How it works:
    SFC compares files on your system with the versions in the Windows component store and replaces any discrepancies.

  • When to use it:
    When you experience issues like crashes, errors, or malfunctioning Windows features.

  • How to run it:
    Open an elevated command prompt (search for “cmd”, right-click, and select “Run as administrator”), then type sfc /scannow and press Enter.

Deployment Image Servicing and Management (DISM):

  • Purpose:
    A more powerful tool that can repair the Windows component store and the system image, often used when SFC fails to fix issues.

  • How it works:
    DISM can scan and repair corruption in the Windows component store, and it can also use a healthy Windows image (from Windows Update, a running system, or installation media) to restore the system image.

  • When to use it:

When SFC fails to fix issues or when you suspect deeper system corruption.

  • How to run it:
    Open an elevated command prompt, and type DISM.exe /Online /Cleanup-image /Restorehealth and press Enter.

Relationship between SFC and DISM:

  • DISM provides the files that SFC uses to repair system files.
  • It’s recommended to run DISM before SFC, especially if you suspect deeper system corruption.
  • After running DISM, you can run SFC again to ensure all issues are resolved.

Norton and DISM/SFC:

  • Some users have reported issues with Norton antivirus interfering with DISM and SFC commands, specifically with the aswhook.dll file.
  • If you encounter errors with DISM or SFC while Norton is installed, you may need to temporarily uninstall Norton or perform a clean install after running the DISM/SFC commands.
  • Some Norton support threads suggest that the issue might be due to a compatibility problem between Norton and the DISM/SFC commands.

In summary, SFC and DISM are valuable tools for maintaining the health of your Windows system. If you encounter issues, running these commands can help repair corrupted or missing system files. If you have Norton installed, be aware that it might interfere with these commands in some cases.

AI responses may include mistakes.

ASWHOOK.DLL Errors on Windows 11 Using DISM Command | Norton Community

Note: recommended run sequence varies

==========================================================

AI Overview
When dealing with corrupted or missing system files in Windows, it’s generally recommended to run the DISM (Deployment Image Servicing and Management) tool before running the SFC (System File Checker) tool.

Here’s why:

  • DISM repairs the OS image:

DISM is a more powerful tool that can repair the underlying Windows image itself, including the component store where SFC gets its repair files.

  • SFC relies on DISM:
    SFC uses the component store repaired by DISM to restore corrupted system files.

  • Efficiency:
    Running DISM first ensures that SFC has a healthy source for repairs, potentially saving time and effort.

In short:

  1. Run DISM to repair the OS image.
  2. Then, run SFC to scan and repair system files.

Example Commands (run in an elevated Command Prompt):

  1. DISM: DISM.exe /Online /Cleanup-image /Restorehealth
  2. SFC: sfc /scannow

AI responses may include mistakes.

Note: recommended run sequence varies

========================================================

AI Overview
It is generally recommended to run the System File Checker (SFC) scan first. If SFC finds and fixes corrupted files, you’re done. If SFC encounters issues that it cannot resolve, then you should run the Deployment Image Servicing and Management (DISM) tool to repair the Windows image, followed by another SFC scan.

Here’s a more detailed explanation:

  1. SFC (System File Checker)
    SFC is a utility in Windows that scans for and restores corrupted or missing system files. It’s a good first step because it’s quick and can often fix minor issues.

  2. DISM (Deployment Image Servicing and Management)
    DISM is a more powerful tool that can repair the Windows image itself, including the component store. It’s useful when SFC can’t fix the problem because the underlying issue is with the image.

  3. Running them in sequence:

  • Run sfc /scannow.
  • If SFC reports errors it couldn’t fix, run DISM /Online /Cleanup-Image /RestoreHealth.
  • After DISM completes, run sfc /scannow again to ensure all issues are resolved.

This approach leverages the strengths of both tools and ensures a more thorough repair process.

AI responses may include mistakes.

Note: recommended run sequence varies

29

@bjm - I just wanted to let you know that as of yesterday, I’ve been able to run 4 Full and two quick scans normally.
@Mykola - AI did a good job explaining SFC, and the different levels of DISM. I’ve made it a point to always run SFC every month before I do my monthly backup, and of course DISM follows if needed (Rarely). Malwarebytes free oncall scanner is also in there. I’ve never had any issues with either of them as far as Norton getting in the way,

2 Likes
30

Hi,

Thank you for posting on the Norton Community and to the gurus for escalating it. We have released virus definitions for this issue. Could you please run LiveUpdate and check if the issue is resolved? Thank you.

1 Like
31

Hi @Gayathri_R. My PC is now able to run scans with no problems.
My wife’s meantime used to take 45 minutes to scan 1.8 million files. Now it takes 5 hours. Do you have any suggestions? Both PC’s run Windows 10.