Reproduction steps:

The video and trace are placed in the network disk.

Actual result:

Selectable status.

Expected Result:

It should be in a non-selectable state because no operation can be performed on the process.

Windows 10 Pro Build 19041 EN All update KTS 21.1.15.482 EN

Reproduction steps:

1. Launched update.
2. After update complete update Click More Tools->Manage application->Software Update.

Actual result:

After update component Software Update not available and ask again update bases.

Expected Result: 

After update component Software Update available from using.

Reproduction steps:

As shown in the figure: https://box.kaspersky.com/smart-link/767a4091-b28e-432f-94fe-aa676b523042/

Actual result:

"接受/发送“

Expected Result:

”入站/出站“

Reproduction steps:

The video and trace are placed in the network disk.

Actual result:

Status display error.

Expected Result:

The status is displayed correctly.

Reproduction steps:

The video and trace are in the network disk.

Actual result:

You can restore the network connection without the second confirmation.

Expected Result:

A second confirmation is required.

Reproduction steps:

The video and trace are in the attachment.

Actual result:

No second confirmation is required.

Expected Result:

A second confirmation is required.

Reproduction steps:

The specific video and trace are in the attachment.

Actual result:

The progress bar is not completed and the result appears.

Expected Result:

The progress bar is completed and the result appears.

Reproduction steps:

The specific video and trace, I put in the attachment.

Actual result:

No second confirmation window pops up.

Expected Result:

The second confirmation window pops up.

Reproduction steps:

The specific reproduction process and video are in the network disk, file name: 0523

Actual result:

Multiple prompt windows appear.

Expected Result:

Only one prompt window appears.

Reproduction steps:

The video and trace have been uploaded to the network disk, and the compressed file named 01.

Actual result:

Clicking the button is invalid.

Expected Result:

Clicking the button is valid.

Reproduction steps:

Settings-Protection-Application Manager-PC Cleaner-Select Object Category

The specific reproduction process and trace, I put it in the network disk, download address: https://c-t.work/s/84917175b7744d

Actual result:

Regardless of whether changes are made, the current window is not automatically closed after clicking Save

Expected Result:

Regardless of whether changes are made, the current window should be closed automatically after clicking Save

For some reason, KTS creates different application groups for the apps with identical vendor/digital signature data, e.g. for Microsoft Edge KTS created MICROSOFT group, while for Microsoft Edge Update — MICROSOFT CORPORATION, please find attached screenshots.

I thought that perhaps, both application just have different digital signature credentials, but not, according to Application control data, they are identical. Such behaviour leads to a mess in Manage application view.

Reproduction steps:

1. Install KTS
2. Install Edge
3. Run Edge

Actual result:

For Microsoft Edge KTS created MICROSOFT group, while for Microsoft Edge Update — MICROSOFT CORPORATION

Expected Result:

All Edge components should be assigned to the same application group.

This issue is an old-one issue and can be reproduced in 2020 as well (INC000011515424).

Reproduction steps:

For some reason the Application Control assigns some of apps with a valid digital signature to a generic groups, e.g. Skype, which is signed by Microsoft Signature ist assigned to "Control created programs → Skype" instead of Microsoft Corporation, and Google Chrome is assigned to "Additionally controlled" instead of Google LLC. Please, find attached screenshots.

Actual result:

Expected Result:

There will be one single Microsoft Corporation group, which will contain all MSFT software.

This issue is quite old and known already for at least 7-10 years at least.Hope, that in KAV/KIS/KTS 2021 this issue will be finally fixed.

The same is relevant for 2020 as well, for that version there is a ticket in Support: INC000011515418