[SOLVED] Windows 7 x64 machine doesn´t install monthly rollups anymore. KB4516065 KB4519976 failed

M

m.fessler

Contributor
Joined
Oct 12, 2019
Posts
5
Hello,

I have here a Win7 x64 machine which doesn´t install monthly rollups anymore.
The last successfully installed rollup was KB4512506 (2019-08).
KB4516065 (2019-09) and KB4519976 (2019-10) failed.

KB4490628 (SSU 2019-03), KB4516655 (SSU 2019-09) and KB4474419 (SHA-2 Update 2019-09) are installed.
I tried to uninstall (to reinstall it then) the KB4512506 (2019-08 Rollup), but it behaves exactly the same like when I want to install the newer rollups.
The installation works, but at the first reboot it says that an error has occurred and that the changes will be undone. It reboots then, everything works but the update is not installed.

sfc /scannow runs without errors
SURT does not work (... could not be installed due to an error: 2147944003 "Serious installation error.")
SFCFix Logfile attached.
CBS Folder: CBS.zip (31.67MB) - SendSpace.com

The CheckSUR.log shows for the most part problems with avast Antivirus.
These entries doesn't seem to be uncommon for avast, I noticed the same in the past on other machines which had no problems.
In the moment avast is not installed on this machine.

If it of importance: This is not the "real" machine because I have rarely physical access to it.
I cloned the machine to another device. But the Update Problem remained unchanged.
I created the image on 26.08., waited for the october rollup to see if that works, yesterday (12.10.) I restored the image to this "test device".
I have run windows Update - followed updates have been successfully installed:
A view Office Updates, KB4474419 (SHA-2 2019-09), KB915597 (Defender), KB890830 (MSRT), KB4524102 (.NET Rollup).

It would be nice if someone could help me.

Thank you,
greetings

Martin
 

Attachments

Add Missing Package
1. Click the Start button and type cmd.exe in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and hit enter.
pnputil -a C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24511_none_bbf6b5bd1f214d75\cpu.inf

Let me know if it says successfully installed. If it does, try installing the update again and attach setupapi.dev.log if it fails again.
 
You are a genius!

I got a driver unsigned warning (Windows cant verify the publisher of this driver software...) but I supposed it´s okay.
I clicked "Install this driver software anyway", restartet the machine, installed the KB4519976, two (or three) automatic reboots and the thing was successfully installed.

Thank you so much!
Could you please briefly explain what led to this error and how you figured it out?

Greetings,
Martin
 
Awesome!

Basically, there is something called the component store, which contains all the components that are vital for smooth OS operation, but when it comes to drivers, they have to be put in a special store, called the DriverStore in addition to being in the component store.

In your case, a driver was present in the component store, but not in the DriverStore, so I just ordered the system to put it in and activate it, so to speak. :-)

Code: 
!!!  sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24511_none_bbf6b5bd1f214d75\cpu.inf' in Driver Store. Error = 0x00000490
 
Ok, but why did windows removed the (cpu?) driver in the first place?
And why is the driver unsigned?

And why are they two different files for the cpu driver in the setupapi.dev.log?
Code: 
!!!  sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24475_none_bbb9d5771f4e5d50\cpu.inf' in Driver Store. Error = 0x00000490
!!!  sto: Failed to find driver update 'C:\Windows\WinSxS\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24511_none_bbf6b5bd1f214d75\cpu.inf' in Driver Store. Error = 0x00000490
Is this because I cloned it to another machine?

I hope there is no problem, that I now used the wrong one (...d75\cpu.inf instead of ...d50\cpu.inf) on the "real" machine.

There are apparently not identical, "...d75\cpu.inf" is at least the newer one (attached as zip files):
...d50\cpu.inf: DriverVer=06/21/2006,6.1.7601.24475
...d75\cpu.inf: DriverVer=06/21/2006,6.1.7601.24511

How do these cpu driver updates get on the devices? With the rollup?

Sorry, I really don't want to bother you any longer. :-)

I sent you a donation. Not overwhelmingly much, but it is to show my appreciation.
Thanks again!

Martin
 

Attachments

Thank you very much for the donation! We appreciate it.

It was not Windows. Something happened. I am really not sure what as I don't know what happened to the machine prior to the incident.

Those are two different versions. The rollups contain them (the newer the version, the later the release date of the rollup update).

As for the log, you should always check the latest errors. That's what I did, checked for the latest error and fixed it, the proof of that is the fact that the rollup installed successfully after the import.

I do not know what is the status of the real machine and whether it can or cannot install the rollups properly. If you are having issues with the real machine, let me know. :-)
 
It's almost like chatting here. ;-)

Ah ok, so the newer one (...d75\cpu.inf) probably came with the october rollup, and because I already tried to installed it on the "real machine" it was there.
Probably the error also occurred with this driver version (I didn´t check the logfile after the sysimage and the installation attempt) so it´s ok that I used that one to fix the problem.

I´ve already did it on the "real machine" yesterday.
Everything worked like on the cloned one. Perfekt!

Somewhat disappointing that none of the Microsoft Tools could fix it.

However, thanks a lot again and have a good one!
Martin
 
You must log in or register to reply here.

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

Back
Top