Solved W11 24H2 concerns.

I have two PCs. I have just upgraded both to 24H2. My Gigabyte B460M just updated the Cumulative .NET Framework with KB5044033 and the Win 11 update with KB504285. Both worked as expected.

But, my main PC Asus Z490Z used KB5044030 and KB5044284. The upgrades both failed when at 40% and reverted back. What do I do now? Is it just a case for MS to replace these two upgrades? Any idea why the two different programs for two different motherboards?

It would help if you could tell us what error you got on the system that failed. You may find it at settings>windows update>update history.

Here's the 2 you applied to the gigabyte machine. The first was for 23h2. It looks like the second has been pulled from the microsoft download database.

October 8, 2024-KB5044033 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 and Windows 11, version 23H2​

KB 504285 id not in the windows update catalog. It has been pulled for some reason.

Here's the 2 the Asus machine tried to apply. They are for 24h2.

October 8, 2024-KB5044030 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2​

2024-10 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5044284)

Are you absolutely sure both machine upgraded to 23h2? You can check by opening a command prompt as administrator and type winver

Fyi, I am on 24h2. The updates that applied to my machine today are KB5044030 and KB5044284

System is definitely 24H2. I see both have downloaded again and are ready to install. I will try again.

But also check the version in the gigabyte machine to make sure it's also 24h2. Something is not kosher here.

My mistake, sorry! The Gigabyte is 23h2, my wires are crossed at present.

I restarted the 24H2 and it did the same "Something went wrong - not to worry" etc. So, I am now going to roll back to 23H2 and wait until MS push the upgrade to me. Watch the roll back go wrong. I do thank you for your input, it is always appreciated.

Right I'm back on 23H2 and 6 days behind on updates. Thanks Glasskuter.

Bryan said:

Right I'm back on 23H2 and 6 days behind on updates. Thanks Glasskuter.

Click to expand...

This is how I did it... my system doesn't seem to like Feature Updates, either.
It could be because I don't wait long enough for them to "roll-out" to me?

I am confused so let me make sure I have this straight. Your Asus machine is running and completely updated on 24h2. Correct?
Your Gigabyte failed to update to 24h2 and rolled back to 23h2 correctly. Correct?

If the 24h2 iso failed to upgrade the gigabyte machine, it's a fair bet to say it will probably fail when it finally gets to you through windows update.
You need to try to find what prevented this upgrade attempt and fix whatever caused it if you can before it comes down the windows update route.

You can look at the upgrade log files to get an idea of what's causing that failure . You have to look at Whichever log applies to the step of the upgrade that failed for you.
Example: Mine failed and initiated roll back on its own during the creating windows.old process which is one of the last thing the upgrade does,so I found my error log in C:\$Windows.~BT\Sources\Rollback\setupact.err

There's a ton of info in the log but I've noticed what causes the failure is repeated in several steps of the log. At the very least you should see an error number that may point us to the problem.If you find the logfile and can't determine the failure, upload it to the cloud. Provide us a share link to the file and we can take alook at it for you.

The following log files are created when an upgrade fails during installation before the computer restarts for the second time

• C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\Windows\setupapi.log
• [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log
• C:\Windows\inf\setupapi.app.log
• C:\Windows\inf\setupapi.dev.log
• C:\Windows\panther\PreGatherPnPList.log
• C:\Windows\panther\PostApplyPnPList.log
• C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and then you restore the desktop:

• C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log
• C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and the installation rollback is initiated:

• C:\$Windows.~BT\Sources\Rollback\setupact.log
• C:\$Windows.~BT\Sources\Rollback\setupact.err

For what it's worth, here is MS article on how to determine the failure using the logs. I had to stumble my way through it since it's all in MS speak. Maybe it will help you. Log files and resolving upgrade errors

If you're a gamer, you might want to take a look at these articles. Ms is putting a hold on some machines which run certain Easy Anti Cheats
as there are problems. (In all honesty I have no idea what an anti cheat is. I've never gamed in my life but if you're a gamer, you'll know if you are afected by these issues.)

My apologies for leading you up the garden path. I should have done my homework and gotten my thoughts in order.

The Gigabyte I did say had been upgraded to 24H2, that was wrong, it remained at 23H2. All is well with that PC.

My problem was with the ASUS Z490. I had used the Media Assistant to upgrade the ASUS 23H2 to 24H2 by overwriting the earlier 23H2. When I came to apply the MS updates, that's when it all turned to custard. The Cumulative updates given were KB5044284 for the System and KB5044030 for the .NET Framework. Both downloaded but when they got to 40% in the Install phase the install failed and a message " Something went wrong - not to worry we will reverse the problem". this was done and 24H2 was all happy again except that the two updates re appeared and began downloading again in a loop. I must have had this at least three times.

Consequently, I rolled back to 23H2 where I will remain until MS say I can upgrade. Thanks for your interest and I am sorry for causing confusion.

Probably the updates are incompatible with the version you have or newer updates made them obsolete and obviously cannot install. Open This PC, click on your Windows disk and from Tools select Cleanup. Click the button to also clean system files. Wait a lttle so the new Cleanup window appears. Make sure you check to delete Windows Update cache (or whatever is called). After doing that restart your computer, open Windows Update and search for updates again. You should see different more appropriate updates to install.