Kaspersky Standard 21.17 [ Bug report page ];

[Psiu47]

'Report' page column is not saving or updating anymore which includes detailed information regarding viruses scan like 'full/quick/path file or external devices'. Not sure yet about background/rootkit scan since last time it happened was at 3 a.m. And going to wait untill it start 24 hours after.

 

This similar bug happen to occur last month around May 12th and took more than 9 days to Kaspersky acknowledge that existing issue. And I was still studying that proccess and symptoms and wait so others could report this as well. Although back then that bug was only affecting 'background/rootkit scan'.

 

But this happening out of the blue again but instead got to affect all type of scans on report page is one thing to get me annoyed. So I'm making this report as fast as I can so it get fixed as soon as possible.

Last known scan was save and it happen to be 18 hours ago and the update pulled a search for at 1:39 a.m. of 06/10. Then at the same day on 7:00 p.m. this bug started. Any action I'd initiate like viruses scans were not properly being saved at report page.

 

[Psiu47]

Ok...seems like is only affecting 'quick/full scans'. Ran another 'selective scan' or path file and it did save on report page.

 

Edited June 11 by Psiu47

[Flood and Flood's wife]

1 hour ago, Psiu47 said:

1. 'Report' page column is not saving or updating anymore which includes detailed information regarding viruses scan like 'full/quick/path file or external devices'.

Not sure yet about background/rootkit scan since last time it happened was at 3 a.m. And going to wait until it start 24 hours after.

2. This similar bug happen to occur last month around May 12th and took more than 9 days to Kaspersky acknowledge that existing issue.

And I was still studying that process and symptoms and wait so others could report this as well. Although back then that bug was only affecting 'background/rootkit scan'.

But this happening out of the blue again but instead got to affect all type of scans on report page is one thing to get me annoyed. So I'm making this report as fast as I can so it get fixed as soon as possible.

Last known scan was save and it happen to be 18 hours ago and the update pulled a search for at 1:39 a.m. of 06/10. Then at the same day on 7:00 p.m. this bug started. Any action I'd initiate like viruses scans were not properly being saved at report page.

 

Hello @Psiu47, 

Welcome back!

1. Do you have an example of how the Report is when the problem does not exist? 
2. When this *similar* issue happened - that (you) observed around 12th May 2024, was a topic raised by (you), we cannot find any? OR perhaps (you) escalated it to Kaspersky? 
3. *IF* the report was logging *path* for Quick, Full, Background etc - potentially there could be thousands of paths in the report... 

• Our Background & Quick scan from the 11th of June 2024 or the 15th of May 2024: 

 

May 2024, Selective scan, shows path, see image

Thank you🙏
Flood🐳+🐋

Edited June 11 by Flood and Flood's wife
added Quick scan & Selective & 2.

[Psiu47]

There were no discussion I've posted last month. What happened actually for 9 days aprox. at May 12th  'rootkit/background scans' were not saving in the full report page like other scans. So with my old habit everytime these scans were about to happen I've kept tracked the time would start accordingly to my clock and when they would stop by checking how many minutes the last background/rootkit finished. And made a log everyday on notepad. That is how I've managed to keep tracking these scans since there bugging for no reason.

And I've thought Kaspersky might be aware, collecting information gathered from their client base to figure out what issue is and get resolved as soon as possible. So I would not bother with another topic about an issue as this since unknown bugs are always related to updates and changes and since KS is set to update daily by automatic. Is an unknown ground which updated blew this off.

Yesterday, I've noticed a similar symptom happening when I'd execute a 'quick scan' and when went to check 'full report page', there were no log about that 'quick scan' and the last detail was from another scan. 

So I have booted the computer and then I've started running path selected, or 'selective scans', 'quick scan' once more and somehow managed to save these reports at 'full report page'.

At late last night after several searches and automatic database updates. What I have noticed is at 10:02 p.m. all scans/verifications I have started were being stored at 'full report page'.

I may have antecipated with no further study and conclusion which gets a wrong image about my presence. So anyhow, it seems like is back to normal by sort of and if the next it happens another bug. I'll wait a day or two before spreading anything at the forum.

 

My apologies for unwary discussion I should have gathered more information before posting this.

 

 

Edited June 11 by Psiu47

[Psiu47]

Apologize once again but this report should not be clarified as closed since this abnormal symptom with report window not registering rootkit or quick/complete scans still happening even with Kaspersky Standard 21.18.5.438(a). I can't record properly this bug because there are moments the scan will be registered and displayed and sometimes not. Ever since Kaspersky Standard 21.17.7.539 which I have firstly see happening on May untill September with actual version KS 21.18.5.438(a) this unknown behavior have been going and the company should be aware of it.

Whenever I execute these scans if I don't keep report window opened, there is a chance the task is not being saved and registered with full detail on report window so with my last studies about this bug. Having opened and minimzed report window whenever scans are about to finish. The task will display as they are ongoing but at the end when is over. The scan is saved, being registered and display but if I close report window or click to update there is a %60 of chance that task will not be registered or displayed on report window.

I'm annoyed to know that I have been facing this bug for a while and I would like revive the situation regarding this unknown bug which started at May 9th accordingly to my first post.

Edited September 29 by Psiu47