KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867 Win Update

Page 29 of 33 FirstFirst ... 192728293031 ... LastLast

  1. kado897
    Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       New #280

    Jaguwaar20 said:
    The Windows system was corrupted and has now been fixed !
    I want to thank everyone for their guidance and suggestions and for being patient with me while I had used so much digital ink to get this issue resolved.

    A shout out to all - a big thanks !


    Attachment 323501

    Attachment 323502
      My Computer
    Quote Quote

  3. Caledon Ken
    Posts : 30,613
    Windows 11 Pro x64 Version 23H2
       New #281

    Excellent.


    The repair install definitely has its use.


    Stay safe
      My Computer
    Quote Quote

  4. Jaguwaar20
    Posts : 145
    Windows 10 Home
       New #282

    ... One more thing


    Before performing the repair install, I booted into the system's UEFI menu using the manufacturer's method and disabled Secure boot in the UEFI boot mode. Before getting too far in the weeds on all the different menus in UEFI boot mode (UEFI and Legacy, UEFI and BIOS, UEFI native, UEFI + CSM, and Legacy), the obstacle is whether I have full control to re-enable secure boot again after the repair install of Windows.

    To my dismay, Secure boot might no longer be an option that can be re-enabled if it was not enabled before the OS repair install.

    After the repair install, an attempt to re-enable Secure boot produced a message which read that Legacy boot was enabled. Except on the same 'boot' menu settings where Secure boot is found, the Legacy boot setting is showing 'Disabled' and it always has been.

    Any chance or possibility of re-enabling Secure boot now?

    msinfo32 shows that Secure boot state is OFF
    pics of the AMI with Aptio setup settings menu are available
      My Computer
    Quote Quote

  5. CountMike
    Posts : 19,526
    W11+W11 Developer Insider + Linux
       New #283

    Jaguwaar20 said:
    Before performing the repair install, I booted into the system's UEFI menu using the manufacturer's method and disabled Secure boot in the UEFI boot mode. Before getting too far in the weeds on all the different menus in UEFI boot mode (UEFI and Legacy, UEFI and BIOS, UEFI native, UEFI + CSM, and Legacy), the obstacle is whether I have full control to re-enable secure boot again after the repair install of Windows.

    To my dismay, Secure boot might no longer be an option that can be re-enabled if it was not enabled before the OS repair install.

    After the repair install, an attempt to re-enable Secure boot produced a message which read that Legacy boot was enabled. Except on the same 'boot' menu settings where Secure boot is found, the Legacy boot setting is showing 'Disabled' and it always has been.

    Any chance or possibility of re-enabling Secure boot now?

    msinfo32 shows that Secure boot state is OFF
    pics of the AMI with Aptio setup settings menu are available
    Secure BOOT is in BIOS/UEFI, windows will not change anything in BIOS.
      My Computers
    Quote Quote

  7. Cliff S
    Posts : 27,283
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       New #284

    Thank Technical Boy(the tech god on American Gods)


    for @Brink, and his posting the .msu links, I was getting the error too from Windows Update.
      My Computers
    Quote Quote

  8. Caledon Ken
    Posts : 30,613
    Windows 11 Pro x64 Version 23H2
       New #285

    That is strange. You should be able to re-enable Secure Boot.

    Do you see anything about reloading default keys.
      My Computer
    Quote Quote

  9. pietcorus2
    Posts : 1,962
    Windows 10 Pro x64
       New #286

    " I was getting the error too from Windows Update ".........yes, only downloading/install fixed my Canon-printer !
      My Computer
    Quote Quote

  10. Jaguwaar20
    Posts : 145
    Windows 10 Home
       New #287

    CountMike said:
    Secure BOOT is in BIOS/UEFI, windows will not change anything in BIOS.
    Let me see if this clarifies what I tried to explain. I tried to change the Secure Boot setting back to the original state of 'Enabled' in BIOS/UEFI. I receive a message though that says Legacy boot is 'Enabled'. Except that right underneath the Secure Boot setting that I selected as 'Enabled' in order to change back to Secure boot (on that same menu tab), Legacy Boot shows that it is 'Disabled'.
      My Computer
    Quote Quote

  11. IronZorg89
    Posts : 2,557
    Windows 10 pro x64-bit
       New #288

    Jaguwaar20 said:
    Let me see if this clarifies what I tried to explain. I tried to change the Secure Boot setting back to the original state of 'Enabled' in BIOS/UEFI. I receive a message though that says Legacy boot is 'Enabled'. Except that right underneath the Secure Boot setting that I selected as 'Enabled' in order to change back to Secure boot (on that same menu tab), Legacy Boot shows that it is 'Disabled'.
    I don't know if I understand you correctly, but if one is on "Enabled", the other ought to be on "Disabled". As a matter of fact, "legacy boot" should be put on "Disabled" before putting "Secure boot" on "Enabled".
      My Computers
    Quote Quote

  13. Caledon Ken
    Posts : 30,613
    Windows 11 Pro x64 Version 23H2
       New #289

    Do you have phone.

    Snap a pic of that screen and post please.


    Apart from changing the secure boot option have you ever changed any other setting other than date time ?
      My Computer
    Quote Quote

 

  Related Discussions
UPDATE 3/9: KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867 The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2). Source:...
If you already updated to 661 or 662, then you will not need to manually download and install 631 since 661 and 662 is a higher build. No need to do anything. Source: https://support.microsoft.com/en-us/help/4594440 See also:...
UPDATE 1/12: KB4598242 CU Windows 10 v2004 build 19041.746 and v20H2 19042.746 The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2). Source:...
UPDATE 12/8: KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Source: https://support.microsoft.com/en-us/help/4586853 See also:...
UPDATE 11/19: KB4594440 CU Windows 10 v2004 build 19041.631 and v20H2 19042.631 UPDATE 11/12: Fixes the in-place upgrade (repair install) issue. KB4586853 CU Windows 10 v2004 build 19041.661 and v20H2 19042.661
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 20:44.
Find Us




Windows 10 Forums