Error27300 when install klhk driver. Error code: -2147024319
-
<p>there was also an installation issue with error code 27300 and a secure boot in UEFI is also enabled on the PC</p>
<p>https://cloud.qainfo.ru/s/G6wUY6CB3rgc35o</p> -
<p>I can still reproduce this problem with secure boot enabled. Same error code.</p>
<p>Can you give more Detailed explanation about the issue?</p>
<p>As far as I can tell, it is a big problem and stable reporduce using any of my devices.</p>
<p></p>
<p><a href="https://cloud.qainfo.ru/s/epRQ1vBET3MOlmh" target="_blank" rel="noopener">https://cloud.qainfo.ru/s/epRQ1vBET3MOlmh</a></p>
<p>logs from new installer.</p> -
<p>Hello</p>
<p>Same problem reproduced with latest build: <span>20.0.10.954 RC</span></p> -
<p>@xzz123 can you add new installer traces, please? I'll reopen bug</p>
<p></p>
<p></p> -
<p>@xzz123 can you add new installer traces, please? I'll reopen bug</p>
<p></p>
<p></p><p>@dmitriy-pisarets</p>
<p>I just disabled secure boot and the installation was successfull.-----Just in oder to check another bug,</p>
<p>I will reproduce this one next day, it is very late in my here.</p> -
<p>@xzz123 can you add new installer traces, please? I'll reopen bug</p>
<p></p>
<p></p><p>@dmitriy-pisarets</p>
<p>here are new installation logs and GSI6 reprot with windows event logs included.</p>
<p><a href="https://cloud.qainfo.ru/s/0OiHM394YDD1iFm" target="_blank" rel="noopener">https://cloud.qainfo.ru/s/0OiHM394YDD1iFm</a></p>
<p></p>
<p>Device: Thinkpad X240s with latest BIOS & secure boot enabled & CSM disabled</p>
<p>OS: windows10 2016LTSB 14393.2670 x64</p>
<p>OS language: Simplified Chinese</p>
<p></p>
<p>The problem has long history, and it is highly likely to be reproduced on some of those old devices. </p>
<p>with old 4th generation CPU, legacy default boot option. After you turn to secure boot and uefi, product install will fail.</p> -
<p>I am going to get a new laptop, will not hold those old devices for long.</p>
<p>Please, investigate the problem, before I can still offer you logs and data.</p> -
<p>@dmitriy-pisarets</p>
<p>here are new installation logs and GSI6 reprot with windows event logs included.</p>
<p><a href="https://cloud.qainfo.ru/s/0OiHM394YDD1iFm" target="_blank" rel="noopener">https://cloud.qainfo.ru/s/0OiHM394YDD1iFm</a></p>
<p></p>
<p>Device: Thinkpad X240s with latest BIOS & secure boot enabled & CSM disabled</p>
<p>OS: windows10 2016LTSB 14393.2670 x64</p>
<p>OS language: Simplified Chinese</p>
<p></p>
<p>The problem has long history, and it is highly likely to be reproduced on some of those old devices. </p>
<p>with old 4th generation CPU, legacy default boot option. After you turn to secure boot and uefi, product install will fail.</p><p>@xzz123 thank you.</p>
<p></p> -
<p>I am going to get a new laptop, will not hold those old devices for long.</p>
<p>Please, investigate the problem, before I can still offer you logs and data.</p><p>@xzz123, i got answer from developers: our drivers are not signed now. When 2020 will be released, secure boot will not crash our installer. You can try install 19 version and install it with secure boot. It'll work. </p>
<p></p>
<p></p> -
<p>@xzz123, i got answer from developers: our drivers are not signed now. When 2020 will be released, secure boot will not crash our installer. You can try install 19 version and install it with secure boot. It'll work. </p>
<p></p>
<p></p><p>@dmitriy-pisarets</p>
<p>So that is the reason.....wow, it worrys me for nearly half a year</p>
<p>the good news is that we finally get a happy ending. Better than never getting an answer.</p>
<p>You may close the case.<img src="/plugins/nodebb-plugin-composer-kl/vendor/tinymce/plugins/emoticons/img/smiley-smile.gif" alt="smile" /></p> -
<p>@dmitriy-pisarets</p>
<p>So that is the reason.....wow, it worrys me for nearly half a year</p>
<p>the good news is that we finally get a happy ending. Better than never getting an answer.</p>
<p>You may close the case.<img src="/plugins/nodebb-plugin-composer-kl/vendor/tinymce/plugins/emoticons/img/smiley-smile.gif" alt="smile" /></p><p>@xzz123 bad, that we didn't provide you info much more earlier. </p>
