Bug reports connected to the following components of Home and Small Office products are received in this topic:
— Standard Windows installer tasks (install/delete, Force Update);
— Migration: KFA <-> KAV <-> KIS <-> KTS;
— Bases update.
Please write in this topic only about the problems that suits the list of components!
General requirements for bug-reports are written in Section 2 of testing guide.
All inappropriate messages will be deleted!
-
Reproduction steps:
Update database
Actual result:
Error, but update successfully.
Expected Result:
No error
-
#2981 Update Error
Rejected
Reproduction steps: Trying update databases manually.
Actual result: Update files are corrupted.
-
#3068 The previous interface will not change immediately after the update source is adjusted.
Accepted
Reproduction steps:
I put the reproduced video and trace in the network disk.
Actual result:
Does not change immediately.
Expected Result:
Change immediately.
-
I have heard that some users will have application errors during cross-version and cross-MR updates. I think this is a very rare event, but it seems that this is not the case. In our investigation, we found that most applications Users with abnormalities often have problems after upgrading from the old MR to the new MR through automatic update. Reinstallation seems to be able to solve the problem, but in their "Programs and Features" list, the original MR version cannot be uninstalled normally. It can only be displayed there all the time.
I installed Kaspersky’s MR1 version on another computer. It was updated to the MR2 version through automatic updates, but a fatal error occurred. The application cannot be updated normally and cannot be used normally. The right-click menu has about Kaspersky All parts of SKY are invalid, and it seems to have reached a very serious level. I checked the application list and saw that there are two Kaspersky application versions (one is the original MR1, and the other is the MR2 installed by automatic upgrade) , I reinstalled the MR2 version, these fatal errors no longer occur, but in the application list, the original MR1 version cannot be deleted normally, and the message cannot be deleted. It needs to be restarted and tried, but this prompt still appears after the restart.
Due to the latest update method, the large version is advanced much faster than before. The original application may be updated once a year, but now it will be performed once in a few months. If this update method has a very high probability of error, then I hope the test team can conduct a test investigation, because if a fatal error occurs, the user may not find it in time. At this time, the program does not have any prompts, but it is already in a state of almost unable to work normally.
-
Reproduction steps:
View the database update report.
Open support and check the database release date.
Actual result:
The dates are not consistent.
Expected Result:
The dates are the same.