Jump to content
  • Announcements

    • Rodion Nagornov

      Долгое сохранение сообщений || Delays while posting (click here to read the full text RU/EN)   09/20/2017

      Due to some technical reasons visual delays are possible while message sending. Actually your message is published immediately - just interface works long. In such case, please, do not re-send your message immediately! Press F5 to reload the page and check if your message/topic is published. || По техническим причинам возможно визуально долгое отправление сообщений на форуме. Фактически ваше сообщение публикуется мгновенно - долго отрабатывает графика. В случае подобной ситуации, пожалуйста, сначала обновите страницу (F5) и проверьте, появилось ли ваше сообщение. Не пытайтесь сразу отправить его заново.
Sign in to follow this  
Schulte

[Erledigt] Patch "G" für KAV/KIS/KTS/KFA 2018 / KSeC 2.0 / KSC 1.0

Recommended Posts

Patch "G" für KAV/KIS/KTS/KFA 2018 / KSeC 2.0 / KSC 1.0 steht zum Testen bereit.

Updatequelle:

http://dnl-test.kaspersky-labs.com/test/ap

Scope features:
•    Requirement 2483890:[BRQ][HTTPS] Show system dialog window with certificates for establishing encrypted connection (2018)
•    Requirement 2509164:[BRQ][Support] Solve encrypted connection excessive checks and notifications problem (2018)
•    Requirement 2483925:[BRQ][SUPPORT][2] Notify user about MITM problems (2018)
•    Requirement 2507165:[BRQ][Win10][RS4]support RS4 - app compat

Fixed problems:
•    Bug 2562187:SUPPORT: DUMP: KasperskyLab.Platform.NativeInterop.TaskManagerExtension!AskAction[[System.__Canon,mscorli_E55
•    Bug 2601020:[2018 Patch G][Web-AV] Certificate rights are reset in FF browser with enabled master password
•    Bug 2590637:[2018G] KL icon looks ugly in MS Edge safe-banking mode

Testhinweise:

1. Installiere das Produkt
2. Führe ein Update von den offiziellen Updateservern durch und starte das Betriebssystem neu.
3. Aktiviere die Fehlerprotokollierung (Traces).
4. Führe ein Update von http://dnl-test.kaspersky-labs.com/test/ap/ durch.
5. Starte das System neu.
6. Deaktiviere die Fehlerprotokollierung.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×