Jump to content

MedvedevUnited

KL Russia
  • Content count

    4,965
  • Joined

  • Last visited

About MedvedevUnited

  • Rank
    Consumer Expert Support Group Manager

Recent Profile Visitors

25,716 profile views
  1. Kaspersky VIP USER, а трассировки и GetSystemInfo собрали? Напишите в техподдержку (можно со ссылкой на эту тему), нужно смотреть.
  2. Здравствуйте, Попробуйте, пожалуйста, сделать следующее: 1. Обновите базы. 2. Включите запись трассировок. 3. Запустите быструю проверку и дождитесь её окончания. 4. Выключите запись трассировок. Воспроизведется ли детектирование MEM:Trojan-Spy.Win32.Agent.gen в этом случае? Если да, отправьте собранные трассировки и отчет GetSystemInfo в техподдержку через https://my.kaspersky.com/support.
  3. Здравствуйте, Попробуйте еще раз, пожалуйста - воспроизведется ли проблема?
  4. amir_s , good news that everything is OK now. If you need further assistance with databases update issue, please, contact our Technical Support via MyKaspersky account: https://my.kaspersky.com/support (you can find instructions here: https://help.kaspersky.com/KPC/1.0/en-US/101731.htm).
  5. https://forum.kaspersky.com/index.php?/profile/645341-ater-vox/ Thank you all for your feedback regarding the fix! I'm glad to hear that it helps the most of you. amir_s , Could you try update databases one more time and check its release date? If nothing changes, please, attach detailed databases update report here: - Open your anti-virus - Go to Database Update - Click hyperlink under 'Last update:' - In opened window select the latest update record and click 'Details' link on the right: - In opened window click 'Export...' button and save report: - Then you may attach saved report here Ater Vox , What do you mean by 'Same'? Do you have the same problem with databases update as amir_s ?
  6. Fix should be available from public updates servers. Please, run databases update, reboot and go to BIOS, enable Secure Boot again. After that check if the issue is reproduced.
  7. Hello Kiwie , Patches are a kind of update which is more complicated than regular databases updates. In patches we fix the most important current product's issues, improve its stability and performance. That's why we test all patches for a long time internally and externally here at forum (beta testers are able to switch to test updates servers and test patches prior we release it to public servers). Unfortunately, it also means that patch rollback procedure is slightly more complicated as well, and some time is required to stop patch distribution. It could be that fix is released sooner than patch would be recalled.
  8. Hello AHS0 , I don't know if your device has exactly the same BIOS as is shown by the provided link, but, please, check screenshot at Step 4 in that article - the first option there is 'Secure Boot state' which should be switched from 'enabled' to 'disabled'. It'd be a working solution until we apply the fix. After that you could enable Secure Boot again.
  9. Hello ObiTobi , Patch E had been published before we received first messages about the problem (otherwise we wouldn't publish it, of course). Our developers have found the root cause of the issue and we are going to release fix soon. We're very sorry for any inconveniences.
  10. Please, try to check if the steps bellow solve the problem: Click Windows Search ant type 'system information', then select System Information application from the results. In opened window select System Summary and check Secure Boot State feature. In case its value is 'Enabled' reboot PC and go to BIOS. Go to Advanced → Security → and set 'Secure boot' feature's value as 'Disabled' (Note, exact path may depend on specific device). Click 'Save and Exit' in BIOS and reboot PC.
×

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.