[SOLVED] Windows 7 Pro 64 (AMD) does NOT receive last updates KB4088881, KB4100480

I

iudith

Member
Joined
Apr 2, 2018
Posts
21
Hello All,


On March 14, 2018 when I installed 6 new updates of the "Patch tuesday" on my Windows 7 Pro 64 (amd) machine,
it got stuck forever during the required restart, showing "Windows configuring updates 100% complete".


I had to hard power the machine and go through several CHKDSK cycles until I was able to boot and all the updates are shown as "Installed Successfully".
The following updates were Installed:



  • KB4088875 (the 2018-03 Monthly Quality Rollup)
  • KB890830 ( the Malicious Software Removal tool - March 2018 )
  • KB2952664 ( update for Win7 64 bit )
  • KB4011675 ( security update for MS Excel 2010 )
  • KB4011674 ( security update for MS Word 2010 )
  • KB3114416 ( security update for MS Access 2010 )


It looks like the culprit here was KB4088875.




Starting from that date, no subsequent security updates appear on my Windows Update list of available updates.


Specifically, the new updates KB4088881 (optional - from March 23 ) and KB4100480 ( security update from March 30 )
DO NOT appear, neither on automatic search for update not on manual search.


All the WindowsDefender updates do arrive and are installed automatically without any errors.



WindowsUpdate.log does not show any errors related to the issue, and after enabling verbose logging it shows the following:


- for the update ID related to KB4088881:


Agent update {969E37F4-7022-4146-8BFB-0DBC76D75BC4}.201 is NOT a generic match


- for the update ID related to KB4100480:


Agent Final detection state for update 26415621 (updateId = {B7533D34-0678-403F-BFDF-576C780A935D}.204) is "NotApplicable"
......
Agent update {B7533D34-0678-403F-BFDF-576C780A935D}.204 is NOT a generic match








There are no errors shown in the Event Viewer, neither in the System log nor in the WindowsUpdate Client log.


I have tried to use all of the following:


1. The Windows 7 Update troubleshooting tool, which reported all of the problems solved.

2. The Microsoft Windows update troubleshooter (file WindowsUpdate.diagcab downloaded from MS web site) which did not report any issues.

3. Installed manually successfully and run KB947821 (System Update Readiness Tool) which found no errors.

4. Run SFC/scannow, which found no errors.





I would like to underline that two other machines having the same Win 7 Pro version, but which are INTEL machines (not AMD)
and have MS Office 2007 (not 2010) did NOT encounter any of the above problems.


These machines did NOT get stuck on reboot after installing the Updates of March 14 (the same set of 3 Windows Updates + 3 corresponding Office 2007 updates),
and they also DID receive both the new updates KB4088881 (optional) and KB4100480 (important) and also installed successfully the second one.




I have read on the web that many people encountered a similar reboot problem when applying KB4056894 (the 2018-January monthly quality pack)
which on my machine caused no problems.






I would like to understand what is the reason that my AMD machine DOES NOT receive the new Windows 7 update,
aka, why were they found to be "not applicable" by the Windows Update service (as the above messages show).


Can it be that these two specific updates (KB4088881 and KB4100480) are presented only to INTEL machines and NOT to AMD machines,
even though their Microsoft Catalog update page specifically mentions "Architecture: AMD64" ?




Usually ALL my 3 machines used to receive always the SAME set of Windows updates (with version differences only for MS Office).




The following registry setting that is documented as a prerequisite for these updates is in place as required (installed by my AntiVirus):


Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
Data="0x00000000”



I know that several websites recommend resetting the Automatic Update components, but I am a little reluctant to take such drastic steps
if they are not strictly necessary.





Thanks a lot in advance & Best Regards,
Iudith Mentzel
 
Hello All,

I would like to add to this thread the fact that on Apr 05 there was another update KB4099950 released by MS, which my AMD machine also DID NOT receive.

The verbose WindowsUpdate.log shows the following messages:

2018-04-06 17:38:49:388 536 21f8 Agent Final detection state for update 26450334 (updateId = {CDCFE708-AFC3-46E7-80F5-B47F439D6D1E}.204) is "NotApplicable"
2018-04-06 17:38:49:466 536 21f8 Agent update {CDCFE708-AFC3-46E7-80F5-B47F439D6D1E}.204 is NOT a generic match
2018-04-06 17:38:54:286 536 21f8 Agent update {CDCFE708-AFC3-46E7-80F5-B47F439D6D1E}.204 is NOT a generic match


I would be very grateful if I could get any help for my initial thread, with this info added.

As I specified in my initial thread, I have already performed some of the general steps indicated for troubleshooting Windows Update problems,
without any problems found, namely:

Step #2 - Run SFC Scan
Step #3 - SURT/DISM Scan

I would like to receive your advice before taking any additional steps.

Please advise if it is safe for me to run the SFCFix step.

Also, please advise whether I should upload the entire C:\Windows\Log\CBS folder (or just the file CBS.log from that folder ).


Thanks a lot again in advance,
Iudith Mentzel
 
Hello Brian,

Thank you so much for not having abandoned me :):)

Yes, definitely, I need your help to guide me further !

I will highly appreciate it !

Reading through several threads, I am really enchanted of the level of assistance supplied on this site :)

Hopefully, it will help me also.

Please just tell me whether I should start and perform (or repeat) ALL the steps in the general guide.

Thanks a lot again :)
Iudith Mentzel
 
No problem. Since it's the second Tuesday of the Month, Microsoft will be releasing the April 2018 cumulative update today. Let's take this a step at a time. When you check for Windows Updates let me know if the April cumulative update shows up. It may not show up until tomorrow though.
 
Hello Brian,

Maybe you will wonder that I am all the time at my computer, with a strong hope to get this issue fixed.

Since the March 2018 updates (including the KB4088875 that caused all the problems),
Windows Update DID NOT detect any more updates for my Windows system, although there were the following 3 released since then:

- KB4088881
- KB4100480
- KB4099950

I only did receive the WindowsDefender and MS Office 2010 updates.

I wonder whether AU could show the new April 2018 updates, if it did not show the previous ones.

The fact that the previous ones were not shown made me suspect that the whole AU mechanism remained stuck somewhere,
following the last reboot problem.


I tried to read a lot "around the problem", to compare behavior + registry settings with my Intel machines that do not have this problem,
but I could not become any wiser ... everything is very cryptic and there is a lot of contradictory information on the web.

I also became a little pessimistic about letting any Windows Updates to just go and install ... as they might every time cause a new problem of this kind ...


All my hope is in your help :)


I can only wish to have a bit of Windows Mastery that your team does :)


In the meantime, I thought about starting to do (or repeat) the preparatory steps for your further help.

But, if you think it's better to wait one more day, I will try to be patient :)


Thanks a lot in advance for any help :)

Best Regards,
Iudith Mentzel
 
Yes I would like to wait until tomorrow and have you check for Windows Updates to see if the new one shows up. Can you also do the following for me?

Retrieve Components/Software Hives
Note: The Software have has confidential and sensitive information in it so please send me a PM with a link to that particular hive so it's not in the public form.
  • Please download the Freeware RegBak from here: Acelogix Software - Download products
     You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, two of which are named COMPONENTS and SOFTWARE.
  • Copy these two files to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right click on these files on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file(s) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBack program now.
 
Hello Brian,


I waited for the Tuesday to pass, and, as I suspected, only the following 4 important updates are shown up on my AMD machine:



  • Security Update for Microsoft Excel 2010 (KB4018362) 64-bit Edition
  • Security Update for Microsoft Office 2010 (KB4018311) 64-bit Edition
  • Security Update for Microsoft Word 2010 (KB4018359) 64-bit Edition
  • Windows Malicious Software Removal tool - x64 - April 2018 (KB890830)




On my Intel machines, however, the following 2 are also shown up:



  • 2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)
  • Update for Windows 7 for x64-based Systems (KB2952664)




So, all the non-OS updates are shown, but the OS-related ones ARE NOT.




Thanks a lot once again and waiting for your help.


Best Regards,
Iudith Mentzel
 
OK, please do the following.

1. Download this file and save to your desktop.
2. Right-click on the file and choose Run as Administrator and click Yes to the UAC prompt if it appears.
3. Type Y into the Window to continue.
4. Type 2 and hit enter to select option#2.
5. When it completes, press any key to go back to the main menu.
6. Type 13 and hit enter to check for Windows Updates.
7. At some point your Windows Update screen will come up and then you can click the Check for updates button.
Let me know if anything shows up.

We are basically running the script as documented at the following link. I put separate instructions to make it a little easier to follow.
Q and A - Script Reset Windows Update Agent
 
Hello Brian,

Since this step is a more drastic one, before I am going to do this, I would just like to better understand what is it going to do exactly.

As far as I can understand, this is going to wipe out the Update History of the machine.

Does this mean that on the next Check for Update, Windows will go and check ALL the (thousands) of updates available on the MS site
and check each one of them against what is effectively installed on my machine ?
If yes, then this is supposed to be a huge task !


Or, instead, will Windows somehow rebuild the Update History from the installed updates,
for using it further during the following Check for Update cycles ?



To ask it in another way:
How exactly does Windows decide whether an update is needed or not for my machine ?
What is it comparing to what ?



And another interesting detail:

As I wrote in my last post, one of my Intel machines (Laptop) did receive both the last Tuesday updates that the AMD machine did not receive:

2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)
Update for Windows 7 for x64-based Systems (KB2952664)



I was sure that my second Intel machine (PC) did receive the same, as it has always happened up to now.

Today, however, I found that it only did receive KB2952664, but NOT the 2018-04 Security Monthly Quality Rollup !

And, in the WindowsUpdate.log, I found the following entry, referencing exactly the UpdateID of the missing KB4093118:

"Update {B8C802BF-1C1D-4835-8083-E09937CA00DB}.201 is pruned out due to potential supersedence"



Such an entry DOES NOT appear for the AMD machine ( for any of the several last missing updates ),
so this one definitely has a different problem.


None of the two Intel machines did encounter any boot problems while applying the March updates ( as the AMD machine did ),
so now I really don't understand why this last 2018-04 monthly update was only received by one of those two machines, and not by the other one.



Sorry to trouble you with so many questions ... but I just want to make sure that I am on the safe side ... and also acquire a little more knowledge on the way.


If anything happens to go wrong, is this procedure reversible ?


Thanks a lot once again for your patience
and Best Regards,
Iudith Mentzel
 
No problem with the questions. This is actually a fairly common process. It's like clearing your Internet Cache of your browser and then let it rebuild. It removes any corruption that may be contained within.

It's actually a procedure that Microsoft publicly documents as a potential solution to Windows Update issues. If you go through the following troubleshooting steps, Microsoft will have you do this manually.
https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

Instead of having you do it manually I'm having you run a script to make the process easier and less error-prone.

Or, instead, will Windows somehow rebuild the Update History from the installed updates,
for using it further during the following Check for Update cycles ?
Click to expand...
Correct, Windows update will traverse the following key in your registry to see which updates appear to have been installed and then do further checking in the Software and Components hive to make sure everything is there.
Code: 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache

It's extremely safe to do. And if for some reason you wanted to revert back, the script creates a backup (C:\Windows\SoftwareDistribution.bak) so yes we could do it but this should not be necessary.
 
Hello Brian,


I am still sitting and studying registry settings, just to understand how exactly the windows update process works.


I just want to exploit your being a great specialist, to help me learn something, after I have tried to find information on the web for so many weeks by now ...



So, if you don't mind, I have a few more questions:


1. Trying to understand where in the registry is Windows storing the list of installed updates,
I discovered the following registry key:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages


which indeed contains a long list of package names.


What is the difference between this key and the one you indicated:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache




I, of course, did not compare their content one-by-one, but I just looked after the KB4088875 (the update that caused the boot failure)
and it does appear in several entries under the first key above, but NOT under the second one.




2. Another question:


What is the significance of the following registry key:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending




It exists on all my machines, with some 10 to 20 subkeys under it, so I don't think that it is directly related to the boot problem,
even if the word "pending" might suggest something in this direction.






3. And a 3rd question:


If I understand correctly, the hive files that we see in folder C:\Windows\System32\config are the storage files for the Registry information.


In other words, ALL the information regarding the Installed Updates is in fact stored in the registry,
so, while checking for available updates, Windows probably uses this registry information.


If so, then what is the role of the files in C:\Windows\SoftwareDistribution and especially in the \DataStore subfolder in the Check Update process itself ?

I guess that the \Downloads folder is probably just a temporary storage for the new update files.



Or, otherwise put, how can the deletion of these files help in fixing an update problem, without making also some change in the Registry content itself ?





And now, to the culmination of this full 24-hours day that I spent at my computer !!!


At this very moment, while I am writing this post, the Check Update window popped up and it shows 1 important update of the last two missing ones,
namely the


2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)






And this happens without having changed anything yet on my machine !!!




And it appears as being published yesterday ( Apr 12 ), though on the other machines it already appeared 2 days ago !


It also appears as Last Updated on Apr 12 on the Microsoft Update Catalog page,
and now with a new UpdateID:


"3ca74ab7-d2bf-47aa-905f-108760444ef5" instead of the previous "b8c802bf-1c1d-4835-8083-e09937ca00db"




So, I can only guess that MS did change something in this update in the last two days,
and "opened it up" for becoming applicable on my AMD machine ... I simply don't have any other logical explanation.


This can also be a warning that the "first edition" of the update might have contained some bug,
that could have easily damaged any of the machines if applied immediately, just the same as it happened the last month !




The second update of this week though, KB2952664, still did not arrive on this machine (but did arrive on the 2 Intel machines).


And the same for the other 3 missing updates, that still did not arrive on this machine during this month.
( KB4088881, KB4100480, KB4099950 ).






This is simply unbelievable !




I should apologize for asking so many questions, and I would be really grateful if you could guide me a little bit
in also understanding somewhat deeper what happens.


As an experienced software developer myself, though not a Windows specialist, and already retired from active work,
I have the feeling that Microsoft keeps all these Windows internals information a little "covered in darkness",
so that only "Windows magicians" could help in solving these strange issues not just for the huge number of non-computer-professional users,
but even for software people specialized in other fields.






Now the question is whether it is safe to let this 2018-04 Monthly update to install itself.


Afterwards I think that I will wait a little bit more to see what happens further, before taking any other action.






Thank you so much for your patience, I do appreciate very much all your help and any valuable information :)




Best Regards,
Iudith Mentzel
 
Hello Brian,

I would just like to update you with another strange issue that happens now:

The new update
"2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)"

appears as having been installed successfully in the "Update History" list, now already 5 times,
however, the machine DID NOT ask for a restart, as usual, but instead the same update keeps appearing again and again when performing Check for Updates.

So, it looks like the previous month's update (KB4088875), that caused the reboot problems,
left the update mechanism itself stuck somewhere, and the new update is unable to complete its installation.


I would be very grateful if you could guide me how to proceed from this point further.

Do you still advise to perform the Update Components reset (as in the previous post) or is there some other action that should be taken ?


Thanks a lot once again & Best Regards,
Iudith Mentzel
 
Hello Brian,


I would like to add more info for you.


While waiting for the next step, I just discovered that starting from today morning, I suddenly have many warnings and errors in the Event viewer.


For not mixing things up, I opened a separate thread for these:


Event ID 136-137 started to appear in EventLog




But, since these errors started only today, which is exactly after the new update KB4093118 made its first attempt to install,
it looks to me that the things are related ...


As I described in the above new thread, I found several web sites indicating some steps to correct this problem,
but they did not help for me, namely:


1. running


fsutil resource setautoreset true c:\


2. running the following:


cd /d c:\windows\system32\config\TxR
attrib -r -s -h *
del *


cd c:\windows\system32\SMI\Store\Machine
attrib -r -s -h *
del *.tm*
del *.blf
del *.regtrans-ms




After performing these steps in safe mode + restart, I remarked the following:


- In folder c:\windows\system32\config\TxR
all the files are from today Apr 14, except for one that is from Apr 12, which is BEFORE the last update did arrive,
and this one probably could not be deleted.


- In folder c:\windows\system32\SMI\Store\Machine
all the files that were deleted above are now from today Apr 14, but the hive file SCHEMA.DAT was last modified on Mar 14 20:48,
which is exactly the precise day and time when the previous update KB4088875 caused the crash and the reboot problem.




Also, once I found the fsutil command, I also tried the following (as Administrator):


fsutil resource info c:\


and it gave me the following:


Error: Transaction support within the specified resource manager is not started or was shut down due to an error.


and trying to start it:


fsutil resource start c:\


says:


Error: Access is denied.






I have a faint supposition that Windows is not able to install the new update KB4093118 because this hive file SCHEMA.DAT
has some problem remained after the previous stuck update.


The many EventID=136 and EventID=137 errors in the EventViewer are probably results of attempting repeatedly
to install this new update without success.






So, here I am stuck again, and I am waiting for your update.




Please forgive me if all what I say is wrong ... I am just struggling to find my way out from this "bush" ...






Thanks a lot so much again if you continue to help me with this issue.


Best Regards,
Iudith Mentzel
 
Hello Brian,


In addition to all the above, today morning, after the new update failed to install,
I also repeated the following 2 checks:


1. SFC /SCANNOW - which again ended without finding any integrity violations:


2. Run the SURT tool - which again did not find anything



However, I do see some error messages in CBS.log.

Attached is a ZIP file containing CBS.log and CheckSUR.log.



Maybe it could help you further.


Thanks again & Best Regards,
Iudith Mentzel
 

Attachments

I am still sitting and studying registry settings, just to understand how exactly the windows update process works.
Click to expand...
No one but Microsoft and more specifically the WU team knows exactly how this works.

1. Trying to understand where in the registry is Windows storing the list of installed updates,
I discovered the following registry key:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages


which indeed contains a long list of package names.


What is the difference between this key and the one you indicated:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache
Click to expand...

ApplicabilityEvaluationCache = shows if an update is installed or not. CurrentState of 70 (hex) means installed.
Packages = Contains all the package names of the updates.

2. Another question:


What is the significance of the following registry key:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending




It exists on all my machines, with some 10 to 20 subkeys under it, so I don't think that it is directly related to the boot problem,
even if the word "pending" might suggest something in this direction.
Click to expand...

Windows uses this key to track the progress of a Session when windows updates are being installed. Any time Windows installs updates, a session is created and all the work is done within that session. When the work is complete the session still stays in this key for historical purposes so you can ignore.

3. And a 3rd question:


If I understand correctly, the hive files that we see in folder C:\Windows\System32\config are the storage files for the Registry information.


In other words, ALL the information regarding the Installed Updates is in fact stored in the registry,
so, while checking for available updates, Windows probably uses this registry information.


If so, then what is the role of the files in C:\Windows\SoftwareDistribution and especially in the \DataStore subfolder in the Check Update process itself ?

I guess that the \Downloads folder is probably just a temporary storage for the new update files.



Or, otherwise put, how can the deletion of these files help in fixing an update problem, without making also some change in the Registry content itself ?
Click to expand...

Information for updates is installed in the registry AND on the file system.

It's possible for the DataStore file to get corrupted and it's also possible for a download within SoftwareDistribution to get corrupted. So cleaning these out simply ensures that this is not part of your issue.

And now, to the culmination of this full 24-hours day that I spent at my computer !!!


At this very moment, while I am writing this post, the Check Update window popped up and it shows 1 important update of the last two missing ones,
namely the


2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)






And this happens without having changed anything yet on my machine !!!




And it appears as being published yesterday ( Apr 12 ), though on the other machines it already appeared 2 days ago !


It also appears as Last Updated on Apr 12 on the Microsoft Update Catalog page,
and now with a new UpdateID:


"3ca74ab7-d2bf-47aa-905f-108760444ef5" instead of the previous "b8c802bf-1c1d-4835-8083-e09937ca00db"




So, I can only guess that MS did change something in this update in the last two days,
and "opened it up" for becoming applicable on my AMD machine ... I simply don't have any other logical explanation.


This can also be a warning that the "first edition" of the update might have contained some bug,
that could have easily damaged any of the machines if applied immediately, just the same as it happened the last month !




The second update of this week though, KB2952664, still did not arrive on this machine (but did arrive on the 2 Intel machines).


And the same for the other 3 missing updates, that still did not arrive on this machine during this month.
( KB4088881, KB4100480, KB4099950 ).






This is simply unbelievable !
Click to expand...

There are many Microsoft Update servers so it's very possible for one machine to get an update and the other machine not to get it for a day or so after. Just depends on which server your machine was pointing to at the time and if that server had the update. At this point, yes I would say it is safe to install the April update but that decision is yours.
 
Hello Brian,

I would just like to update you with another strange issue that happens now:

The new update
"2018-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4093118)"

appears as having been installed successfully in the "Update History" list, now already 5 times,
however, the machine DID NOT ask for a restart, as usual, but instead the same update keeps appearing again and again when performing Check for Updates.

So, it looks like the previous month's update (KB4088875), that caused the reboot problems,
left the update mechanism itself stuck somewhere, and the new update is unable to complete its installation.


I would be very grateful if you could guide me how to proceed from this point further.

Do you still advise to perform the Update Components reset (as in the previous post) or is there some other action that should be taken ?


Thanks a lot once again & Best Regards,
Iudith Mentzel
Click to expand...

To avoid confusion, let's please work on only the machine that you started this thread for. If you have a different machine with a different issue, let's start a new thread for that one.
 
If you are indeed using an illegal version (not properly licensed) of Microsoft Windows of Microsoft Office I will be unable to help you further.
 
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