Cumulative updates do not install other updates do

Ha100

Member
Joined
Sep 28, 2024
Posts
5
Cumulative updates fail with error 0x8007054F. Other updates do install. Windows update says database corruption.
My server 2016 is a vps on an Red Hat virtualizer. Virto.
I have done all the scans and tried many things, it still does not work.
 

Attachments

Code:
2024-09-27 23:09:54, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]
2024-09-27 23:09:54, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]
2024-09-27 23:09:54, Info                  CBS    Perf: Doqe: Install ended.
2024-09-27 23:09:54, Info                  CBS    Failed installing driver updates [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]
2024-09-27 23:09:54, Error                 CBS    Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]

Could you please provide your setupapi.dev.log file, which can be found here: %systemroot%\inf\setupapi.dev.log. Please also provide your DRIVERS hive using the following:

Upload Drivers Hive

  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current DRIVERS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the DRIVERS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as Dropbox or OneDrive or SendSpace and include the link with your reply.
 
Code:
     sto: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\uaspstor.inf_amd64_8a155e74da9fa75b\uaspstor.inf} 16:57:06.710
     sto:      Driver Package = uaspstor.inf_amd64_8a155e74da9fa75b
     idb:      {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\uaspstor.inf_amd64_8a155e74da9fa75b\uaspstor.inf} 16:57:06.710
     idb:           Changing active driver package from 'uaspstor.inf_amd64_2c6ca114353abf59' to 'uaspstor.inf_amd64_8a155e74da9fa75b'.
     cpy:           Unpublished 'uaspstor.inf'.
     idb:           Deindexed 1 driver file for 'uaspstor.inf_amd64_2c6ca114353abf59'.
!!!  idb:           Failed to query driver INF matches for '{4d36e97b-e325-11ce-bfc1-08002be10318}'. Error = 0x0000054F
!!!  idb:           Failed to update driver package device IDs for 'uaspstor.inf_amd64_2c6ca114353abf59'. Error = 0x0000054F
!!!  idb:           Failed to publish 'C:\Windows\System32\DriverStore\FileRepository\uaspstor.inf_amd64_8a155e74da9fa75b\uaspstor.inf'. Error = 0x0000054F
     idb:      {Publish Driver Package: exit(0x0000054f)} 16:57:06.710
!!!  sto:      Failed to publish driver package. Error = 0x0000054F
     sto: {Publish Driver Package: exit(0x0000054f)} 16:57:06.710
!!!  sto: Failed to publish all driver updates. Error = 0x0000054F

Thanks, could you please open command prompt and then enter the following command:

Code:
pnputil /enum-devices /class {4d36e97b-e325-11ce-bfc1-08002be10318} >> %userprofile%\desktop\devices.txt

Please attach the file devices.txt which would have been saved to your desktop in your next post.
 
Thanks but just realised that the command I suggested is only applicable on Windows 11 machines. Could you please run the following FRST script? It doesn't actually fix anything despite the name but will run a series of registry queries and then save the output of each to a file named fixlog.txt.

FRST Fix
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Thanks, I can't seem anything immediately obvious at the moment, could you please try and perform the same update again but while a Process Monitor trace is running?

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file. Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

The LogFile.PML can reach up to a couple of GB so please make sure you've placed it in a .zip folder.
 
The update fails after a reboot so I cannot do this. I think it has to do with the Virtio scsi driver viostor.sys. When I try to update this driver it fails with 'Element not found' or 'Internal Error'.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top