F-Secure Total: Full manual scan freezes at 11% and not progressing

Vido
Vido Posts: 6 Explorer
edited January 10 in Device Protection

F-Secure Total Version 19.8, Windows 11 Pro 24H2, Fujitsu Lifebook E449, RAM 16,0 GB
Full manual scan gets

Untitled.jpg

stuck at 11% 304,524 files of ca. 400,000. SSD drive C:\ 80 GB free
Last scanned folder c:\ProgramData\Package Cache{10725A82-69E2-521A-2E4F-94312A28AA90}v10.1.25398.1\installers. No process is locking the folder.
Before the scan: deleted F-Secure Total and released the license.
Then reinstalled the package and started scan. Any ideas, anyone?

Tagged:
Like Awesome

Accepted Answer

  • Ukko
    Ukko Posts: 3,798 Superuser
    Answer ✓

    Hello,

    It may be useful to know things like:

    - is it really stuck? or is scanning still 'processing', scanning and further things (but not as fast and not as 'visually' understandable)? for example, by looking at information in Task Manager (CPU/RAM/Disk usage or whatever else places) or "UI" of Scan Wizard.

    - can you try manually scanning the mentioned 'last scanned folder' and see see if it completes?

    - if manual scanning (context scan) is possible for mentioned folder; can you try to exclude this folder in Settings (Manage scanning exclusions) and then running Full Scan and check if there will be another 'stuck'?

    Sorry for my English.

    Thanks!

    1Like Awesome

Answers

  • Vido
    Vido Posts: 6 Explorer

    Yes, it was really stuck. I let it run for 12 hours and no progress after 11% although the scanned file count was clearly more than 11%. Task manager also showed minimal CPU and memory consumption. I manually scanned the folder (File Explorer context scan) without problems. No viruses. I was at my wits end.

    Then, I actually don't know why I did it but I took ownership of C:\ProgramData\Package Cache folder (using takeown and icacls) because that's the folder where the manual full scan got stuck.

    And what do you know! Presto, the scan went without a hitch. It started at 23:39:03 o'clock and ended at 00:03:47. Pretty fast I would say. Scanned 443036 items, no harmful items found. Problem solved, case closed

    2Like Awesome
  • jnnh73
    jnnh73 Posts: 12 Enthusiast
    edited February 16

    I also noticed a similar problem.

    I had Windows 11 23H2. F-Secure Total was working just fine, and when I ran full scans, it never got stuck.

    Since I installed 24H2, three things started to happen:

    • F-Secure gets stuck on full scan. Every time. Sometimes it scans 17.000 files, sometimes 120.000 and so on, from the system drive. But every time it gets stuck. I've tried to just leave it on for hours, but it has not made any progress during that time.
    • After that update, my computer takes minutes to shut down. It has something to do with F-Secure + 24H2 because I tried uninstalling it and it no longer was slow shutting down.
    • Also under 24H2 F-Secure doesn't uninstall nicely. The installer gets stuck every time, and after reboot I have to try again more than once.

    So, I restored a Macrium Reflect system image and went back to 23H2, and… everything works just fine again. Scan doesn't get stuck and my computer shuts down as fast as it always did before 24H2.

    I regret that I didn't take any logs etc. while I was running 24H2, they could have been useful, but it is too late now.

    While running 24H2, reinstalling F-Secure didn't help. I even tried to clean all the relevant folders by hand after uninstall, and also tested the removal tool.

    I was wondering, is this some known 24H2 + F-Secure issue that will get fixed eventually, or was it just my computer.

    Like I said, I can' t send any logs etc. because I didn't save them. I will reinstall 24H2 during the next few weeks/months and see what happens then. Until that I'll enjoy the smooth ride with F-Secure + 23H2.

    2Like Awesome
  • jnnh73
    jnnh73 Posts: 12 Enthusiast

    SO, my earlier post is no longer relevant.

    F-Secure is now working just fine, MS Windows was the culprit.

    I was going to run 23H2 for now, but Windows forced the 24H2 update.

    This time after the update everything works fine, F-Secure finishes scans normally and no longer hangs on shut down.

    I suspect my earlier 24H2 installation was botched/incomplete. First time it left 15 gb on that "windows.old" folder and took 2 hours. Now it took longer and left 47 gb stuff behind. So I suppose now it did something it was supposed to do the first time but didn't.

    Case closed, all is well :)

    1Like Awesome

Categories