Golomar

Hello Flood: Coincidentally, as soon as I read your earlier post, I manually updated my database and application file and when I checked the application version, it changed and included the “a” appendage to the version number: I did a restart of my computer as you suggested and it seems to work OK. I live in Canada but the patch must have become active sometime very recently because I updated my application version to 21.3. within the last day or two and there was no “a” until today. So, thank you once again and tomorrow I will use your link to the Windows 7 application version update. I will ask the person I am helping tomorrow to do a full uninstall and clean install from the global website just to make sure we are both on the same page when he finishes updating his data and application version. He does not want to update his OS to Windows 10 so whatever we do must work with Windows 7. Once again, thank you for your assistance and suggestions.

Hello Flood: Thank you for this information about Windows 7 still being supported for the upgrade of KIS to application version 21.3.10.391 because I will need this information tomorrow when I walk a fellow KIS user with a Windows 7 machine through an application version upgrade to 21.3.. And thank you for the information re Patch(a) and for providing the appropriate links. I will install the Patch “a” right now to bring my machine up to date.

Hello Psiu47: Your problem seems to have been caused by the upgrade to application version 21.3.10.391 (no “a” appended on my version for Windows 10 Home Edition 64-bit OS). From some of the reading I have done, KIS no longer supports Windows 7 OS so I am wondering if the ‘forced’ upgrade to application version 21.3.10.391(a) is indeed the source of your problem while it was the solution to my problem? Since you have a valid activation code, do you think it would be possible for you to completely uninstall KIS from your computer and then download a fresh copy with the latest application version starting with 21.3.XX.XXX? I don’t know which region you are writing from so perhaps the “a” at the end is meant for your region and not Canada where I am. Good luck.

Hello Berny: Your suggestion to upgrade my application version to 21.3 was successful in allowing the Background Scan to automatically start and complete a scan: Thank you once again for all your assistance.

Hello Berny: I didn’t know KIS version 21.3 was available until you brought it to my attention today. I have downloaded and installed this version on my Windows 10 Home Edition desktop computer and I am just running a Full Scan right now; thank you very much for the information about the upgraded application version for my region [Global]. I will still need to see if the Background Scan kicks in automatically and goes to completion with this new version installed but thank you for all your assistance so far.

Hello: Following Berny’s advice above [enable both iChecker and iSwift] I still have the same problem of the Background Scan utility not running to completion. The latest scan came back with only 30% of the Background Scan being completed: Latest Background scan shows only 30% of scan was automatically completed and no further scans were done in the last 2 days. I remember in an earlier version of KIS that a Background scan could be run manually. I can run Quick, Full, and Vulnerability scans manually so why not return to letting users run a Background scan manually just like in the past? My computer does not noticeably slow down when any of these scans are being run and I like to run them manually or at least have the option of running the Background scan manually. Anyone else having incomplete Background scans on their Windows 10 Home Edition machine?

Hello Berny: I read the link information you sent and changed my Quick Scan advanced settings to enable both iChecker and iSwift (only iChecker was active by default). I will try this suggestion and see if that helps my Background Scan activate itself automatically and goes to completion. Merci beaucoup. Golomar

Hello: I have been having a recent problem with my Windows 10-based Kaspersky Internet Security where the Background Scan will ‘hang up’ at 1% of the scan and then quit: This is a relatively recent problem because I remember the background scan running smoothly and to completion not too long ago. I religiously update my Windows 10 operating system and run frequent manual updates to my KIS database including both Quick Scans and Full Scans with no problem. Anyone having a similar problem? I would also like to know if I can manually run a Background Scan as used to be possible in previous versions of KIS. Thank you.