Cumulative Updates failing to install on Gigabyte Z390 Motherboard

spapakons · Nov 20, 2022

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

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.

Don't disable any Microsoft services to be in the safe side. Check the box in msconfig to hide Microsoft services. Then disable any updaters (Adobe updater, Google updater, Mozilla Maintenance etc). Don't touch any service you don't know what it is. Also look for suspicious services or unknown entries in Startup applications. This could indicate the presence of malware.

slcidea · Nov 20, 2022

spapakons said:
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.

Did all that and more multiple times to no avail.

slcidea · Nov 20, 2022

spapakons said:
Don't disable any Microsoft services to be in the safe side. Check the box in msconfig to hide Microsoft services. Then disable any updaters (Adobe updater, Google updater, Mozilla Maintenance etc). Don't touch any service you don't know what it is. Also look for suspicious services or unknown entries in Startup applications. This could indicate the presence of malware.

Only non-MS services were running (i.e. clean boot) and still it failed. This problem started when KB5016629 was introduced so I went back to the one before that KB5015882 and that went in fine. Which is why I suspect that MS added something in all subsequent updates that my setup for some odd reason is not working. There have been numerous reports of update failures for the last few months so this is apparently a known issue. Some configurations are working o.k. but others are having problem. The only workaround from what I can tell is a clean install.

slcidea · Nov 20, 2022

IanMosley said:
dism /Online /Cleanup-Image /RestoreHealth

Did all that.

retiredat44 · Nov 20, 2022

I have an Asus Z170 pro gaming with Win11 installed. Just an FYI, to let you know it should work with yours.

fireberd · Nov 21, 2022

IanMosley said:
dism /Online /Cleanup-Image /RestoreHealth

In my case, dism didn't help. I tried that plus others I found doing searches and none helped. Only the in place upgrade worked.

slcidea · Nov 21, 2022

fireberd said:
In my case, dism didn't help. I tried that plus others I found doing searches and none helped. Only the in place upgrade worked.

It's a bizarre problem with no consistent solution. Like I said before, the only workaround for me was to do a complete fresh clean install. The only clue that I have is the error code (0xC1900101 – 0x20017 or 0x30017, Installation failed in SAFE_OS phase with an error during BOOT operation) that's generated when you try to do the in-place upgrade. This is the only reason I suspect a driver related issue during "update only". If it's really a bad driver then my machine should be experiencing problem all the time and not only during cum updates. I found this link that may offer some clue 0xC1900101 – 0x20017, Installation failed in SAFE_OS phase with an error during BOOT operation I'll look at the setupact.log in the Panther directory to see if there are any clues as to which driver may not be migrating during update.

spapakons · Nov 21, 2022

Manually download and install latest drivers from manufacturer support site. Don't trust Windows Update. Then try upgrading again. I once had mixed version graphics drivers (not all components were updated to the latest version) and could not upgrade to the next Windows 10 build. Installing latest drivers did not fix the issue as it didn't replace all the files. The solution was to completely remove all drivers traces with DDU (Display Driver Uninstaller) and then install latest drivers again. See if you have a similar issue.

slcidea · Nov 21, 2022

spapakons said:
Manually download and install latest drivers from manufacturer support site. Don't trust Windows Update. Then try upgrading again. I once had mixed version graphics drivers (not all components were updated to the latest version) and could not upgrade to the next Windows 10 build. Installing latest drivers did not fix the issue as it didn't replace all the files. The solution was to completely remove all drivers traces with DDU (Display Driver Uninstaller) and then install latest drivers again. See if you have a similar issue.

Unfortunately, the drivers that are on Gigabyte's site for my MB are much older than what Windows recommends. Most vendors don't keep their drivers up to date especially when the board is a few years old.

spapakons · Nov 21, 2022

Download drivers for Windows 10 or 8 64-bit or 7 64-bit. They work in Windows 11 except for some Intel graphics drivers that are configured to install only on Windows 7.

Dru2 · Nov 21, 2022

slcidea said:
Unfortunately, the drivers that are on Gigabyte's site for my MB are much older than what Windows recommends. Most vendors don't keep their drivers up to date especially when the board is a few years old.

Can you show me where Windows "recommends" better drivers than those on Gigabyte's site???

BTW, those are the same drivers I'm using on my board and as said, no issues here. That if it was those "older" drivers", everyone with Z390 boards would be having the same issue. We know this isn't true.

Your board - Z390 UD (rev. 1.1) Support | Motherboard - GIGABYTE Global

My board - Z390 AORUS XTREME (rev. 1.0) Support | Motherboard - GIGABYTE Global

Honestly, at this point in time I think many are just grasping at straws in trying to solve your issue. There's zero reason to grab any other driver than what's on Gigabytes site for Windows 11, as shown in the links above. In short there "are" Windows 11 drivers there.

And no, I don't have an answer too, but given all the fixes you tried, it may be easier to simply do a clean install by using Media Creation Tool to download the latest install media.

Good luck.

slcidea · Nov 21, 2022

Dru2 said:
Can you show me where Windows "recommends" better drivers than those on Gigabyte's site???

BTW, those are the same drivers I'm using on my board and as said, no issues here. That if it was those "older" drivers", everyone with Z390 boards would be having the same issue. We know this isn't true.

Your board - Z390 UD (rev. 1.1) Support | Motherboard - GIGABYTE Global

My board - Z390 AORUS XTREME (rev. 1.0) Support | Motherboard - GIGABYTE Global

Honestly, at this point in time I think many are just grasping at straws in trying to solve your issue. There's zero reason to grab any other driver than what's on Gigabytes site for Windows 11, as shown in the links above. In short there "are" Windows 11 drivers there.

And no, I don't have an answer too, but given all the fixes you tried, it may be easier to simply do a clean install by using Media Creation Tool to download the latest install media.

Good luck.

Over time drivers are updated by Windows Update if and when they are available. The machine is about 2 years old and the original drivers that were installed during build may not be the same today. The error message when upgrade fails to complete is a generic error message that points to driver issue during migration. This happens when the system restarts part way through the upgrade process (i.e. after 30% complete). This is where the system gets hung up with the infinite spinning circle. This didn't happen until KB5016629 came out in early August. After trying so many things I resorted to a clean install of 22H2 and Windows installed all new drivers that come with the OS. It could either be a corruption in the registry or an actual driver that is not behaving properly when it comes to new updates that started in August. That's my best guess and conclusion. Like I said in my previous post, MS is apparently aware of numerous update issues and there's no single solution that works for everyone. In the end they too recommend a clean install because they have no clue what the cause could be.

Dru2 · Nov 21, 2022

slcidea said:
Over time drivers are updated by Windows Update if and when they are available.

Keenly aware that drivers get updated. I've been building and toying with PCs and Windows since 1998. My last build, in my system specs, was 2019. And I'm obsessive about driver, and BIOS updates.

That said, do you know the version of the chipset driver you're running?

slcidea said:
Like I said in my previous post, MS is apparently aware of numerous update issues and there's no single solution that works for everyone. In the end they too recommend a clean install because they have no clue what the cause could be.

If that were the case, we'd all have the issue. We all don't, so....

slcidea said:
In the end they too recommend a clean install because they have no clue what the cause could be.

Neither does anyone else. This is why it's important to provide information requested, no matter how "insignificant" it may seem.

As for Microsoft, given the myriad of PC configurations Windows is run on, yes, sometimes it is impossible to track down an issue, especially if they don't know what got the end user to the issue they have. Additionally, given all the stuff you did to try to "solve" the issue could even confuse more. At the end of the day a clean install may be to only option left to solve the issue.

slcidea · Nov 21, 2022

Dru2 said:
Keenly aware that drivers get updated. I've been building and toying with PCs and Windows since 1998. My last build, in my system specs, was 2019. And I'm obsessive about driver, and BIOS updates.

That said, do you know the version of the chipset driver you're running?

If that were the case, we'd all have the issue. We all don't, so....

Neither does anyone else. This is why it's important to provide information requested, no matter how "insignificant" it may seem.

As for Microsoft, given the myriad of PC configurations Windows is run on, yes, sometimes it is impossible to track down an issue, especially if they don't know what got the end user to the issue they have. Additionally, given all the stuff you did to try to "solve" the issue could even confuse more. At the end of the day a clean install may be to only option left to solve the issue.

The driver version for the Intel Z390 Chipset is 10.1.16.7. BTW, don't assume only device drivers as the cause of the issue. It could be a software driver related to a program that might be the culprit. Your system may have the same hardware and device driver but the software we install are entirely different and anyone of those programs could be the source of the problem.

Dru2 · Nov 21, 2022

slcidea said:
The driver version for the Intel Z390 Chipset is 10.1.16.7.

As I said, I've been doing this awhile, so yes, I know about software drivers as well. I also mentioned Windows is run on a "myriad of PC configurations" meaning not everyone has the same setup.

Anyway, where specifically did you find the version info for your chipset driver? Cause that's not what's listed on Gigabyte's stie.

slcidea · Nov 21, 2022

Dru2 said:
As I said, I've been doing this awhile, so yes, I know about software drivers as well. I also mention Windows is run on a "myriad of PC configurations" meaning not everyone has the same setup.

Anyway, where specifically did you find the version info for your chipset driver?

In Device Manager, under System Devices. I also ran a Utility that I found that spits out all the drivers on your machine including File Version, File Company....

Dru2 · Nov 21, 2022

slcidea said:
In Device Manager, under System Devices. I also ran a Utility that I found that spits out all the drivers on your machine including File Version, File Company....

Yeah, that's the wrong place as the driver version won't be listed there as explained by Intel

It's actually listed in the registry....

The same driver version listed on Gigabyte's site. And as you see it's not been "overwritten" by "Microsoft.

slcidea · Nov 21, 2022

Dru2 said:
Yeah, that's the wrong place as the driver version won't be listed there as explained by Intel

It's actually listed in the registry....

View attachment 45865

The same driver version listed on Gigabyte's site. And as you see it's not been "overwritten" by "Microsoft.

The driver for the chipset that I have on my machine were loaded by Windows and I don't have Registry Key that you have on your machine. I do remember trying the chipset driver from Gigabyte and it didn't make any difference. Which is why I strongly suspect a software driver and not a device driver which is what this is. Thanks for your suggestion. The fact that this problem emerged all of a sudden in August and no new software was installed is a mystery.

Dru2 · Nov 21, 2022

slcidea said:
The driver for the chipset that I have on my machine were loaded by Windows and I don't have Registry Key that you have on your machine. I do remember trying the chipset driver from Gigabyte and it didn't make any difference.

If you don't have that registry string, then you don't have the driver installed. Period.

BTW, how can you criticize a vendor for not providing updated drivers, when you don't even have the ones, they provide installed?

slcidea said:
The problem sometimes is that board vendors aren't current with their driver updates on their site.

Regardless, I'm not saying the driver is going to fix your issue, but if you don't install drivers, what else is happening? And especially since your error code is pointing to a driver issue. Was also why I asked to see your Device Manager, which you never provided.

With that I'll move along. Good luck.

slcidea · Nov 21, 2022

Dru2 said:
If you don't have that registry string, then you don't have the driver installed. Period.

BTW, how can you criticize a vendor for not providing updated drivers, when you don't even have the ones, they provide installed?

Regardless, I'm not saying the drivers are going to fix your issue, but you don't even install drivers, what else is happening? It was also why I asked to see your Device Manager, which you also never provided.

With that I'll move along. Good luck.

I did have the vendor drivers previously and it didn't make a difference so I uinstalled them thinking it would help to go with what Microsoft recommended. You have to try different things. The upgrade works if I only keep personal files which further confirms a software driver issue not a hardware device driver.