Windows 11, version 24H2 won't install

Anonymous
2024-11-14T16:51:47+00:00

Hello

I never had any problems with my PC .

Windows 11, version 24H2 update is ready to install, I approve the restart, it starts working, stops at 68% for 5 minutes, then restarts and turns off PC. When I booth back, it simply wants to download it and install it again.

Troubleshooter shows Error but offers no solution.

I have downloaded the ISO and followed all instructions, but 26% in, the installer just stops all goes back to windows and says Windows 11 instalation failed.

Any ideas?

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

412 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-19T00:21:32+00:00

    Well said. Microsoft has screwed up badly with this update. So now we have two updates that won't work on many machines - Win 10 to 11 and 11 to 11. So, does this mean I have to buy another machine?? I think not.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-10T16:02:04+00:00

    Hello

    I never had any problems with my PC .

    Windows 11, version 24H2 update is ready to install, I approve the restart, it starts working, stops at 68% for 5 minutes, then restarts and turns off PC. When I booth back, it simply wants to download it and install it again.

    Troubleshooter shows Error but offers no solution.

    I have downloaded the ISO and followed all instructions, but 26% in, the installer just stops all goes back to windows and says Windows 11 instalation failed.

    Any ideas?

    Hey, hope you solved your issue by now

    I had windows update not downloading issue since 22h2, and I used iso file to update my windows

    But finally I found the solution!

    If you have 8GB or less ram:

    First delete windows update cache

    Then do a clean boot and update your windows.

    This solution worked for me; I think this error is due to windows update NOT being optimised and therefore it uses a lot of resources especially ram.

    By performing a clean boot your system should allocate available resources to windows update.

    Hope it helps

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-01-10T03:35:51+00:00

    OEMs and Microsoft has to work in tandem to fix this issue. Whitelist the Windows update processes in their real-time scans will ease the situation. I just got my MSI Vector 16 and post powering on I started with upgrade. I was stuck at 25% then I removed all update cache from C:\Windows\SoftwareDistribution\Download and disabled all AV features. It worked like a charm.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-01-08T21:54:16+00:00

    To all it concerns (that's meanwhile quite a lot):

    Again, Microsoft urges me to do the accursed 24H2 Windows 11 update, which definitely can't succeed, as Microsoft and a huge amount of users know by now. That is, lest one does some time-consuming digital acrobatics, which I am not prepared to submit to and that don't even guarantee a positive outcome most of the time. So, I have decided to stop all updating until Microsoft has sorted out this mess.

    Bye,

    HKB

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-01-06T20:00:29+00:00

    I, for one, did run the hvciscan_amd64 tool. Apparently, it found no incompatible drivers To wit:
    C:\Temp> .\hvciscan_amd64

    VbsGetIssues: 0x00020040

    UEFI WX Memory Attributes Table required

    8GB RAM required

    VbsIsRecommended: 0

    HVCI incompatible driver scan start...

    HVCI: Driver scanning complete

    HVCI incompatible driver scan passed!

    And still, the dreadful update won't install. This little game has now lasted far too long. Let Microsoft sort that boo-boo out until one can install the thing without all those convolutions it has put its users through.

    The whole caboodle is a digital scandal. Meanwhile, let whoever is in charge include me out. I'm giving up.

    I studied Microsoft's guide: "Get help with Windows upgrade and installation errors" - it was horrible reading for a normal user.

    It contains more than 30 possible error codes and suggested remedies if the update fails - several of which have been featured here as well.

    And they also say that "common errors can be fixed with a few steps (??) that you can do on your own"

    It came to my mind that "does Microsoft now live in the same world as millions of users?"

    Does Microsoft really think that someone could follow these massive and time-consuming instructions - after all, it's often a user, not an IT engineer?

    Is 24H2 already too big and ambitious update for Microsoft --> it doesn't seem to be now under "anyone's control" anymore?

    Is Microsoft trying to pass on fixing their own errors to users by releasing such a massive number of possible error codes --> this causes a large number of users to be in such a "distress" due to lack of knowledge?

    https://support.microsoft.com/en-us/windows/get-help-with-windows-upgrade-and-installation-errors-ea144c24-513d-a60e-40df-31ff78b3158a#WindowsVersion=Windows_11&articleFooterSupportBridge=contactUsBridge

    Certainly seem to be duff drivers that don't pass the first boot at 30%. Found one of those. I suspect the bulk updating of drivers in 23h2 prior to the update is where people go wrong. You are told you need to update drivers that are old but they can fail in the upgrade which stops at 30%. There are sticklers that won't unload low level programs.

    The most frustrating thing about sorting out the update was reading the same old fixes that didn't fix it. They might have fixed getting to 23h2 but don't fix to getting to 24h2. Hvciscan was the one that fixed mine after nine weeks of trying. The memory integrity at the end of all this was the one. The error code was too general,

    Personally I can't see Microsoft sorting it out since they have changed the installation rules unless they go back and weaken what they are trying to do in making the installation more tight... tight it is. Thus the clock is running till when support ends.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments