KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 Win Update

Page 64 of 65 FirstFirst ... 145462636465 LastLast

  1. Posts : 120
    Window 10 Pro 22H2
       #630

    Thx Bree
      My Computer


  2. Posts : 4
    Windows
       #631

    I'm fairly nervous to run the partion script, I believe these are good instructions to do so?
    https://answers.microsoft.com/en-us/...a-726ebac6bbf6
    But I'm worried if it fails what mess might I end up in.


    Thus I think maybe the wushowhide route is more appealing.

    Are there any concerns to not do that?

    In some ways I'd be happier to follow Bree's older steps KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 with minitools... But still a bit apprehensive!
      My Computer


  3. Posts : 120
    Window 10 Pro 22H2
       #632

    You likely don't need KB5034441 unless you use BitLocker Drive Encryption. Check whether you're using it in CONTROL PANEL. You can just disable it.

    Then use SHOW/HIDE from Microsoft to hide KB5034441. It works well and will eliminate your fears and concerns.
    Last edited by Toronto Cat; 07 Mar 2024 at 20:32. Reason: Correction
      My Computer


  4. Posts : 1,939
    Windows 7 Home Premium x64
       #633

    ConfusedTiger said:
    I'm fairly nervous to run the partion script, I believe these are good instructions to do so?
    https://answers.microsoft.com/en-us/...a-726ebac6bbf6
    But I'm worried if it fails what mess might I end up in.


    Thus I think maybe the wushowhide route is more appealing.

    Are there any concerns to not do that?

    In some ways I'd be happier to follow Bree's older steps KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 with minitools... But still a bit apprehensive!
    don't run the MS script - it's NOT worth it if you don't know what you're doing

    hide or block the KB5034441 update with wushowhide.diagcab indefinitely until MS decides one day to no longer offer it
      My Computers


  5. Posts : 667
    WIN 10 19045.4291
       #634

    erpster4 said:
    hide or block the KB5034441 update with wushowhide.diagcab indefinitely until MS decides one day to no longer offer it
    You don't have to hide or block something. Just close your eyes und you will be astonished. You will not see it, because it's not there.
    If you have some basic knowledge about partitions and the sfc-scan is not the only command you are able to execute, you can solve it in less than 5 minutes. And that is a fact.
      My Computer


  6. Posts : 16
    Windows 10
       #635

    I messed around unsuccessfully with command prompt and minitool wizard, apparently I failed to follow the clear step by step directions to the letter. Then I hid the update. Then I changed it to unhide or show it. The failed update continued appearing for a couple days and then disappeared.

    My desktop PC is almost six years old and it's still running 10. I hope to buy a new desktop and then make the move to 11 at some point this year. Apart from the occasional Windows update hiccups, it's still running fine. Last week it went to a black screen for a long time after a Windows update and I had to force restart a bunch of times. I don't want to wait until it goes to black permanently to finally buy a new PC.
      My Computer


  7. Posts : 667
    WIN 10 19045.4291
       #636

    I know that the internet is full of wrong instructions. To solve the problem a screenshot of "Diskmanagement" is needed.
      My Computer


  8. Posts : 30,192
    Windows 11 Pro x64 Version 23H2
       #637

    and the tutorial to do that.


    How to Post a Screenshot of Disk Management
      My Computer


  9. Posts : 4,594
    several
       #638

    Bree said:
    I've got quite well practised at sorting this one out. My process:

    • turn off recovery with reagentc /disable
    • Use Disk Management to shrink C: enough to allow the recovery partition to be enlarged to at least 800MB.
    • Use Minitools Partition Wizard to enlarge the recovery partition.
    • restart the PC. This is essential so that the OS knows the new start point of the recovery partition.
    • turn on recovery with reagentc /enable
    • In Windows Update retry installing KB5034441
    Has anybody tried

    reagentc /disable
    then mount winre.wim
    use dism to install the cab
    https://www.catalog.update.microsoft...px?q=Safe%20OS
    unmount commit
    reagentc /enable

    could optimize/export the wim to make it a bit smaller if desired

    the updated winre.wim might not be much bigger than the original. If it is too big, then use a 3rd party tool to expand the recov partition before reagentc /enable.

    It seems quite sensible to have a big recov partition anyway, about 1gb perhaps to avoid faffling in future.
    Last edited by SIW2; 21 Mar 2024 at 16:26.
      My Computer


  10. Posts : 4,594
    several
       #639

    @ferrarabrainpan

    ferrarabrainpan said:
    I messed around unsuccessfully with command prompt and minitool wizard, apparently I failed to follow the clear step by step directions to the letter. Then I hid the update. Then I changed it to unhide or show it. The failed update continued appearing for a couple days and then disappeared.

    My desktop PC is almost six years old and it's still running 10. I hope to buy a new desktop and then make the move to 11 at some point this year. Apart from the occasional Windows update hiccups, it's still running fine. Last week it went to a black screen for a long time after a Windows update and I had to force restart a bunch of times. I don't want to wait until it goes to black permanently to finally buy a new PC.
    That sounds like a windows issue, not an issue with the machine.

    If your dell xps is 8th gen or newer, it is a decent machine and it should run win11 fine

    those dell things sometimes come with only one stick of ram and often a basic disk. So they can be improved for little cost.

    If it is an old 4th gen or similar, then it might be time to think about getting something more recent.
      My Computer


 

  Related Discussions
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 12:04.
Find Us




Windows 10 Forums