Kaspersky's full-screen confirmation window does not pop up properly (it starts with a flashback and cannot be displayed afterwards)
-
<p><strong>Reproduction steps:</strong></p>
<p>Found a problem after the updateKaspersky is normal at the first boot every day.But after restarting the system, Kaspersky's confirmation window will not pop up.For this I recorded a video, check the address: <a href="https://drive.google.com/file/d/1-h78hgs9_6MXw6-IIqH_8TD3BmY4mPhE/view?usp=drivesdk" target="_blank" rel="noopener">https://drive.google.com/file/d/1-h78hgs9_6MXw6-IIqH_8TD3BmY4mPhE/view?usp=drivesdk</a></p>
<p></p>
<p></p>
<p>I collected a trace file of the complete flashback processDownload address: https://cloud.qainfo.ru/s/6Zr73SctFlFJvb7</p> -
<p>My GSI report download address: https://cloud.qainfo.ru/s/fmnkyI4hEiQGuTD</p>
-
-
<p>@jarvis said in <a href="/post/5900" target="_blank" rel="noopener">Kaspersky's full-screen confirmation window does not pop up properly (it starts with a flashback and cannot be displayed afterwards)</a>:</p>
<blockquote>hello! Can you reproduce it on patch B and on 2021 new build ?</blockquote>
<p>I have been a Windows 7 system before, this time I changed to the Windows 10 system, there was no problem in the previous environment, it was the push time of the b patch.Due to this problem, I have become very difficult to uninstall. I can't determine if the b patch has this problem.And my virtual machine is Windows7 system, everything is fine, but currently my virtual machine has not been replaced to Windows10 1903</p> -
<p>@jarvis said in <a href="/post/5900" target="_blank" rel="noopener">Kaspersky's full-screen confirmation window does not pop up properly (it starts with a flashback and cannot be displayed afterwards)</a>:</p>
<blockquote>hello! Can you reproduce it on patch B and on 2021 new build ?</blockquote>
<p>Hello, there is a dump report that failed to start, I hope to be useful to you.https://cloud.qainfo.ru/s/1BkU9wZcgzUs3vN</p> -
<p>@huang1111 Hi! Developers says old Windows and .Net versions can cause this problem. Can you update Windows and ,Net and try to reproduce it? </p>
<p></p>
