Cumulative Updates failing to install on Gigabyte Z390 Motherboard

slcidea · Nov 20, 2022

spapakons said:
I miss the good old days you could repair Registry by loading an older instance. It was done in Windows 98 by running the scanreg command with the appropriate parameters. From Windows Me and later you can use System Restore to go back to an earlier restore point, provided you have enabled System Restore (it is disabled by default in Windows 10 and 11) and there is a suitable point to return to. Once you fix it with an in-place upgrade or with a clean installation, make sure you enable System Restore and you create a restore point. If anything goes wrong again just return back to this point. Your data are not affected.

I periodically make complete backups with Macrium after major updates and also have restore points to revert back to.

IanMosley · Nov 20, 2022

spapakons said:
Once you fix it with an in-place upgrade or with a clean installation, make sure you enable System Restore and you create a restore point. If anything goes wrong again just return back to this point. Your data are not affected.

By MS's own admission,'system restore' is not reliable; you should investigate a bespoke OEM backup & restore software. Most contributors to this Forum run Macrium Reflect or other backup software.

The free version of MR - here - should be OK for your needs,.

SIW2 · Nov 20, 2022

I had problems with the updates as well. The big one call kb501 something appeared to go in, but on restart just stuck on a blank screen.

After uninstalling the update using the function on the boot media, restarted into win11 alright.

Then after more updates, at least it it booted into win11. But there was another problem - file explorer jamming up.

Bit bored with it doing that. I might just reinstall and start again.

spapakons · Nov 20, 2022

I am aware of Macrium Reflect and other cloning tools, but creating a Restore point takes 1-2 minutes while cloning the whole 480GB SSD would take over 30 minutes. If I have to go back at a specific restore point it might take 10-20 minutes while cloning back the whole disk would take more than 30 minutes. I reserve clones when there is a total disaster I cannot fix by simply getting back to a restore point. Also it is well known that you might not succeed to go back to the latest restore point or going back to that might not fix your issue. In that case try again going back to an earlier restore point and this usually works.

SIW2 · Nov 20, 2022

I might try reinstalling with the boot media I just made. I included the windows setup files, though I dont normally install that way, I will give it whirl when I have the time.

2261v7.iso

For people who like using windows setup, it searches all partitions for the appropriate sources folder on the root. So you can plonk the sources folder on the root of any partition and run setup from booted media and it should find it. Setup has behaved like that since win7.

Dru2 · Nov 20, 2022

IanMosley said:
By MS's own admission,'system restore' is not reliable;

That would be false as Microsoft never said, "System Restore" is not reliable. What they said was "Backup and Restore" was being depreciated and no longer being updated. Different program and has nothing to do with "System Restore"

Deprecated features in Windows client - Windows Deployment - System Restore is NOT listed there.

Dru2 · Nov 20, 2022

slcidea said:
I did all that and also uninstalled it but same infinite spinning circle after 30% restart. Something and likely a driver issue is preventing the update to complete is my guess.

I'd asked you earlier what board you had? Also stated I had a Z390 board. Did you miss the post or what?

SIW2 · Nov 20, 2022

Seems the OP wants to keep it secret.

Dru2 · Nov 20, 2022

SIW2 said:
Seems the OP wants to keep it secret.

Yeah, it seems to be the ole "help me" but I'm not providing any info on the hardware post. Check the system specs. We don't even know which version of Windows being run.... another question I asked.

spapakons · Nov 20, 2022

The brand makes little difference. As soon as the Firmware (BIOS) and the chipset drivers are properly updated there should not be any issue.

Dru2 · Nov 20, 2022

spapakons said:
The brand makes little difference. As soon as the Firmware (BIOS) and the chipset drivers are properly updated there should not be any issue.

It actually DOES help to know system specs, and you know this. It also helps to know the board model to check if the drivers and BIOS are up to date or correct. You know this as well.

As I'm fond of saying.... help me help you.

slcidea · Nov 20, 2022

Dru2 said:
I'd asked you earlier what board you had? Also stated I had a Z390 board. Did you miss the post or what?

Sorry, my board is Gigabyte Z390 UD Rev: 1.1 and I am running the latest F10 Bios.

spapakons · Nov 20, 2022

Which brand? Asus, Gigabyte, Asrock, MSI?

slcidea · Nov 20, 2022

spapakons said:
Which brand? Asus, Gigabyte, Asrock, MSI?

Gigabyte Z390 UD Rev 1.1

Dru2 · Nov 20, 2022

slcidea said:
Sorry, my board is Gigabyte Z390 UD Rev: 1.1 and I am running the latest F10 Bios.

Your post title - "Cumulative Updates failing to install on Gigabyte Z390 Motherboard" at first reads as though "Gigabyte Z390 boards" had an issue, but reading through all your posts, your issue is anything after KB5015882 has fails to install, and not really an issue with the board itself?

slcidea · Nov 20, 2022

Dru2 said:
Your post title - "Cumulative Updates failing to install on Gigabyte Z390 Motherboard" at first reads as though "Gigabyte Z390 boards" had an issue, but reading through all your posts, your issue is anything after KB5015882 has fails to install, and not really an issue with the board itself?

My post was to see if anyone else was having similar issue with Gigabyte Z390 relative to cum updates after KB5015882. My hardware is fine, and I was able to do a clean install without any issues. My problem is that these cum updates go to 30% and when the computer restarts to finish the rest of the update it just stays with the spinning circle forever. I've let it run overnight thinking it's taking extra time but no luck. Something in the boot process during an update is not working and the most logical cause is driver hangup. When the update fails the error code that's associated with why the update didn't work is 0xc1900101 which is related to driver. What I need to know is which driver in particular is the culprit. I've even disabled all non-Microsoft Services and used clean boot but no luck. If it's something related to the registry then it's almost impossible to figure out the cause.

spapakons · Nov 20, 2022

I don't think the motherboard has anything to do with it. Run sfc /scannow in the Terminal or Powershell as Administrator to fix any faulty system files. Then restart. If this doesn't fix the issue you must also use the dism command. Sorry I don't remember the syntax.

SIW2 · Nov 20, 2022

I had similar problems. Just did a clean install and the subsequent updates appear to have been ok .

Gave me a chance to try out my new boot media

I got rid of the existing namespace folders

that looks better:

and we're off:

Dru2 · Nov 20, 2022

slcidea said:
My post was to see if anyone else was having similar issue with Gigabyte Z390 relative to cum updates after KB5015882.

I don't. And I have a Z390 board. See my system specs.

slcidea said:
What I need to know is which driver in particular is the culprit. I've even disabled all non-Microsoft Services and used clean boot but no luck. If it's something related to the registry then it's almost impossible to figure out the cause.

Yeah, that error code is not going to point to a specific driver as it is generic in nature only indicating there is some type of driver issue.

One of the things you could (should) do is investigate your Device Manager to see if there are any Red X or yellow exclamation points or question marks. With that can you post an image of your Devie Manager?

BTW, I don't think it's a good idea to disable services when you're already having issues, unless you know for certain the service, you're disabling is actually the cause of your issue.

IanMosley · Nov 20, 2022

spapakons said:
If this doesn't fix the issue you must also use the dism command. Sorry I don't remember the syntax.

dism /Online /Cleanup-Image /RestoreHealth

Cumulative Updates failing to install on Gigabyte Z390 Motherboard

Active member

My Computer

Windows Insider

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

Attachments

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Windows Insider

My Computer

Similar threads