Author Topic: Can't install certain Windows 7 Updates  (Read 825 times)

0 Members and 1 Guest are viewing this topic.

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Can't install certain Windows 7 Updates
« on: November 04, 2017, 10:51:22 AM »
Hi,

     I have been having 3 long-standing problems since 2016.  I have run Windows Repair Free but it didn't fix my issues.  I also tried SURT(System Update Readiness Tool) from Microsoft.  It fixed nothing.  I'm running Win 7 x64 SP1 Ultimate.

     Basically, I can't install the KB3126587 Windows Update since its launch in 2016.  It fails to install with the error 80070490 - Element not found.

     I also have another strange problem.  The Windows Update would ask me to install the very first version of IE 11(released in 2013), while I already have the latest version of IE 11.  Accepting this update will prompt installation successful.  After reboot and check for updates, Windows Update will ask me to install the same old IE 11 version again...  Every time after I close IE 11, the iexplorer.exe *32 and iexplorer.exe processes will still be running, and I have to manually end the processes.

     Also, I don't see the important Servicing stack update KB3177467 installed on my PC.  And Windows Update does not ask me to install it.

     Looks like my Windows 7 component store is corrupted.  I don't know if the Windows Repair Pro version can fix it?
« Last Edit: November 04, 2017, 10:59:07 AM by kk159 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #1 on: November 04, 2017, 03:05:29 PM »
The free version of WR does the same standard repairs as the Pro version, but the Pro version can be useful if Step 2 - the Pre-Scan finds problems with the Package files.

Have you run the Pre-Scan ?

Have you also ran an antimalware scan ?

Have you also ran a sfc /scannow to see if it repairs or reports any corruption ?

To run a sfc /scannow, go Start - type cmd then right click on cmd and select Run as administrator - accept the UAC and type sfc /scannow and press enter.

It can take about 20mins to run.

If it reports that it cannot repair some files then download/run SFCFix.exe which can sometimes repair files that a sfc /scannow cannot but it will produce its own log which you can copy & paste into the reply box.

http://www.majorgeeks.com/files/details/sfcfix.html

See if you can manually install KB3177467 from the MS Update Catalog and then try the install for KB3126587.

https://www.catalog.update.microsoft.com/Search.aspx?q=kb3177467

You need the first one for a 64bit system.

If KB3177467 installs okay but you still have problems with KB3126587 then run SURT again.

You can view its log in C:\Windows\Logs\CBS then double click on the Checksur one.

I'm not sure if the update problem is related to your IE problem, but you could try unchecking the box for IE in Programs and Features/Turn Windows features on or off but it's best to have another browser installed first as you will lose all access to the Internet.

I have Firefox installed as my spare browser.

After the reboot, go back into features and re-check the box for IE and see if you get the same prompts.

This is as near as you can get to reinstalling IE.

Do you have an install disk for your Win 7 Ultimate with a valid retail key ?

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #2 on: November 04, 2017, 05:58:23 PM »
Hi man, thanks a lot for looking into my case!

If windows repair pro can in principle fix my problem, I would definitely buy it.  Even the free version saved me 3 times in the past, so I didn't have to reinstall the OS.

I tried everything you suggested, things didn't look so promising, as I might have some serious issues with the win 7 component store.

Here is what I did:

1. I manually installed KB3177467 a few days ago, thinking it would solve my problems.  It installed successfully.

2. Today I tried to install KB3126587, failed with the error 80070490 again.

3. I ran SURT, it completed the process after an hour, and generated 4 files, attached in my reply: CheckSUR.log, CheckSUR.persist.log, DeepClean.log, FilterList.log
I was able to get about 400M more disk space after running SURT, I guess the size of the winsxs folder is reduced after running SURT

4. I tried to install KB3126587, failed with the error 80070490 again.

5. I ran sfc /scannow(not in safe mode), found integrity violations, and SFC says it repaired issues.  Note that I had run sfc /scannow multiple times in safe mode in the past, and none of those times reported any integrity violations.
I used the command findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" to get only the SFC-related entries in my CBS.log and attached it here.

6. I ran SFCFix.exe.  It says SURT total detected corruption count: 1535, and fixed nothing  :rolleyes:, the log is also attached.



About the Windows version I'm using - I bought a legit copy of Windows 7 pro years ago off Microsoft, and for some reason I upgraded to Ultimate within the OS.  And I had to use a certain program to activate/crack it.  I don't have problems installing other updates, no black screens.  Just having problems with the KB3126587 and the never-ending update of the oldest IE 11 version.
« Last Edit: November 04, 2017, 07:25:21 PM by kk159 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #3 on: November 05, 2017, 01:51:06 AM »
I was asking about the install disk because I was considering a repair install may be the way to go on this.

Can you download the free version of Speccy to see if the product key is the same as the one you got for Win 7 Pro ?

https://www.piriform.com/speccy

Click on Operating System in the right pane and that will give you your 25 alphanumeric product key.

To do a repair install, your install disk would need to include SP1 which depending upon when you bought it can determine if it did or not, but you would need the correct key to retain Ultimate.

It may be worth contacting MS to confirm if that product key is for Ultimate, explaining how you upgraded from Pro to Ultimate and what you are wanting to do.

There are two sources that I know of where you can download a Win 7 x64 Ultimate ISO but the first would need to accept your product key to release the download and is from -

https://www.microsoft.com/en-gb/software-download/windows7

The second is from - http://windowsiso.net/

Hover over Win 7 ISO and the sub menus to select the one for Ultimate.

I believe these will include SP1.

When you have saved the download, in both cases you will need a program to create the install media.

You can use Windows own USB/DVD Burner tool - http://wudt.codeplex.com/ or you can use ImgBurn - http://www.majorgeeks.com/files/details/imgburn.html

With the latter you can only create a disk.

A repair install doesn't affect your personal stuff or installed programs but you will need to reinstall all Windows Updates again which may resolve the missing .mum files.

To perform a repair install - go Start - Computer - insert the install media and double click on the drive.

If using a DVD, this will start the process but if using an USB, that will open to the files where you would double click on setup Application.

However, before you go that route, can you run the Step 2 Pre-Scan to see what it reports for the Package .cat and .mum files.

Can you also check Event Viewer by going Start - type eventvwr and press enter.

When Event Viewer opens, ensure Event Viewer (Local) is highlighted in the left pane - if it isn't then just click on it.

When it has read the data, click on Error then on Show All Instances of This Event in the lower right pane.

A while ago I ran the pre-scan on my Win 7 laptop and it produced 2005 Package file problems as I've documented in this thread -

http://www.tweaking.com/forums/index.php/topic,4412.0.html

My Event Viewer at the time had a number of ESENT errors listed but also one for CAPI2 Event ID 257.

From a Google on that I ran a cmd prompt as an admin and entered these cmds which resolved those, but they don't always work which was found for others.

net stop cryptsvc

ren C:\Windows\System32\catroot2 catroot2.old

net start cryptsvc

shutdown /r /t 00

A Pre-Scan for me after the reboot came up clean.

One of the repair program's Pro repairs is designed to resolve those missing/corrupt Package files.

If you do decide to upgrade to the Pro version, remember that now it is a one licence/one machine product key, but see how you get on with those cmds.

You can easily reverse them by changing the cmd to catroot2.old catroot2



Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #4 on: November 05, 2017, 08:26:09 AM »
Thanks.  atm I consider a repair install as a last resort, as I don't want to reinstall all drivers.  The key for the Ultimate is different from Pro, unfortunately.  I have both the Pro and Ultimate install disks.

I looked at my catroot2 folder, and it's only 32.3 MB = 21 files + 3 folders with random names.  Am I missing a lot of stuff here?

Attached below is the pre-scan result.  Different from your case, I also see missing .cat files other than .mun files.  Windows repair version is 4.0.8

I checked the event viewer, no errors like you mentioned are found after the pre-scan.










~~~~~~~

┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (11/5/2017 11:09:18 AM)

│ These Files Are Missing: (Total: 932)
C:\Windows\servicing\Packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_102_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_102_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_102_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_102_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_103_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_103_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_103_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_103_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_104_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_104_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_104_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_104_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_104_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_105_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_105_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_105_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_105_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_105_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_105_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_105_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_106_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_106_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_106_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_106_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_106_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_106_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_106_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_106_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_107_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_107_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_107_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_107_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_107_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_107_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_107_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_107_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_108_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_108_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_108_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_108_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_108_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_108_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_108_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_109_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_109_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_109_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_109_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_109_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_109_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_109_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_109_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_109_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_110_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_110_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_110_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_110_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_110_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_110_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_110_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_111_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_111_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_111_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_111_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_111_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_112_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_112_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_112_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_112_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_112_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_112_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_112_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_112_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_113_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_113_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_113_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_113_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_113_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_113_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_113_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_113_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_113_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_113_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_113_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_113_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_113_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_113_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_114_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_114_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_114_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_114_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_114_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_114_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_114_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_114_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_114_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_114_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_114_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_114_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_114_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_114_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_115_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_115_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_115_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_115_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_115_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_115_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_115_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_115_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_116_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_116_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_116_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_116_for_KB3057154~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_117_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_117_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_117_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_117_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_117_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_118_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_118_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_118_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_118_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_119_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_119_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_119_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_119_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_120_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_120_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_120_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_120_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_121_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_121_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_121_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_121_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_121_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_121_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_121_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_121_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_122_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_122_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_123_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_123_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_123_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_123_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_124_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_124_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_124_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_124_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_125_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_125_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_125_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_125_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_126_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_126_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_126_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_126_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_127_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_127_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_127_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_127_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_127_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_127_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_127_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_127_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_146_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_146_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_147_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_147_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_148_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_148_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_149_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_149_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_150_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_150_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_151_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_152_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_153_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_153_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_154_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_154_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_155_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_155_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_156_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_156_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_157_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_157_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_158_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_158_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_159_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_159_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_160_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_160_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_161_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_161_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_162_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_162_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_163_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_163_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_164_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_164_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_165_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_165_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_166_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_166_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_167_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_167_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_168_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_168_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_169_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_169_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_170_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_170_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_171_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_171_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2909210~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2909210~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2925418~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2925418~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2936068~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2936068~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.3.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.3.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.2.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.2.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.4.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.4.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.5.3.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.5.3.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.8.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.8.mum
C:\Windows\servicing\Packages\Package_1_for_KB2964358~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2964358~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2978092~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2978092~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3000869~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3000869~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.cat
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.29.mum
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.2.13.cat
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.2.13.mum
C:\Windows\servicing\Packages\Package_1_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_1_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_1_for_KB3048070~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB3048070~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3069114~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB3069114~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB3070738~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3070738~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3087918~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3087918~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_217_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_217_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_21_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_21_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_237_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_237_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_253_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_253_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_254_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_254_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_29_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_29_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_29_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_29_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2925418~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2925418~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2936068~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2936068~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2978092~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2978092~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3000061~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3000061~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_2_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_2_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_2_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3034344~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3034344~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3039066~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3039066~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3046482~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3046482~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3048761~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3048761~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3063858~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3063858~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3065979~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3065979~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3069114~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3069114~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3070102~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3070102~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3070738~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3070738~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3076895~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3076895~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3079757~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3079757~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_30_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_30_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_30_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_30_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_31_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_31_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_31_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_31_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_32_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_32_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_33_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_33_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_37_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_37_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_38_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_38_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_38_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_38_for_KB3045999~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_38_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_38_for_KB3083992~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_38_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_38_for_KB3088195~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_38_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_38_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_39_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_39_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_39_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_39_for_KB3013410~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_39_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_39_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.2.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.2.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.4.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.5.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.5.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.8.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.8.mum
C:\Windows\servicing\Packages\Package_3_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2979570~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3000061~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3000061~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3034344~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB3034344~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3048761~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3048761~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3063858~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3063858~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3065979~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3065979~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3070102~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3070102~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_40_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_40_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_41_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_41_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_41_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_41_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_42_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_42_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_45_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_45_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_48_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_48_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_49_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_49_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_49_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_49_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_49_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_49_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2522422~31bf3856ad364e35
« Last Edit: November 05, 2017, 08:59:18 AM by kk159 »

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #5 on: November 05, 2017, 02:15:05 PM »
This is strange.

I just bought the Pro version.

In safe mode it took around 40min to repair the registry correspondence of the missing package files.  I reboot then did a pre-scan, it still reports 932 missing package files?

KB3126587 still fails with 80070490
« Last Edit: November 05, 2017, 02:17:28 PM by kk159 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #6 on: November 05, 2017, 03:00:48 PM »
You can back up your drivers folders from C:\Windows\System32 onto something like a Flash drive and drop them back in if required after the repair install has completed.

Can you run the Package file repairs again and then do another pre-scan.

I think Shane found that when the pre-scan found a large number of files being snagged, if using Intel graphics was to update those drivers - again, this didn't work for everyone.

You could also run SURT again - the only two fixes MS has for that error code is a sfc /scannow or SURT.

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #7 on: November 05, 2017, 05:17:24 PM »
\/\/\/ DO NOT FOLLOW WHAT I SAID IN THIS REPLY, AS IT COMPLETELY DESTROYED MY REGISTRY AND CAN'T BOOT WITHOUT RESTORING THE REGISTRY \/\/\/

Thanks.

I ran the missing servicing package clean up tool again.

If I tick all entries at once, it would spend a long time going through every package - about 40 min for all 932 entries.  At the end, it promts to delete or keep a certain registry entry(I always choose "yes"), and the fix only applies up to the problematic windows update corresponding to that registry entry, which I find a huge waste of time.
It doesn't fix all entries in one go.  After scanning through all ticked entries, whenever the program needs my permission to delete something, it will stop at that windows update.
The least amount of problematic entries for a given package is 2, 1 for the .cat and 1 for the .mum.  Usually the program doesn't ask me for permission if a package only has 2 problematic entries.  But if a package has more problematic entries(more than 60 for package #2 in my case, meaning that package affects more than 30x different problematic windows updates), it usually requires my permission to fix it.

Instead of ticking everything, I manually tick all entries for a given package.  The whole package would get fixed if the cmd window auto closes at the end.  Otherwise, it would require my permission to delete some registry entries.  In this case, I repeat this process until that entire package gets cleaned up.  No restart is needed, and it works.

I'm able to get down to 600+ entries now and keep going.  Will report when I finish.

I don't know what will happen if I simply delete the registry key whenever it asks me.  One could make the program automate this process to save a lot of time.  Just need to do a registry backup before cleaning up everything.
« Last Edit: November 06, 2017, 08:50:15 PM by kk159 »

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #8 on: November 05, 2017, 07:45:21 PM »
Ok, almost dead...

I got stuck on the last 78 entries and it wouldn't fix anything.

Reboot = BSOD

Safe mode, last known good config, either BSOD or black screen after Windows logo...

No system restore image or restore point, cuz I disabled those.  sfc can't be launched

Startup repair doesn't work, says autofailover with 0xf4 error message...

So I used a usb win 7 SP1 x64 Ultimate iso image, in cmd I copied back my registry from RegBack: software, system and sam

Now I'm able to boot into OS without problems...
« Last Edit: November 05, 2017, 07:47:23 PM by kk159 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #9 on: November 06, 2017, 12:46:08 AM »
Perhaps it's time to go for a repair install then.

I think you should turn System protection back on as you never know when you might need it - such as in this instance.

Does your computer use Intel graphics and have you checked for driver updates if so ?

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #10 on: November 06, 2017, 08:34:33 PM »
After successfully running the missing servicing package cleanup tool yesterday by choosing "No" every time, the number of missing packages reported by Windows Repair went to 0.
The IE 11 problem was fixed, but I still couldn't install KB3126587.
However, the # of corruption detected by SURT went from 1500+ to 34000+.  I think this is a dangerous feature to use...

So I did a repair install today, fixed everything.  Reinstalled a few corrupted programs(cfosspeed, vmware, VS 2015) after the repair install, and I installed every windows update with some effort(had problems installing .net framework updates cuz somehow I already installed a newer version).  Now SURT shows 0 errors.

Except one problem.  The Oct 2017 update will cause SFC to report a usb driver issue, again:
https://www.sevenforums.com/performance-maintenance/410998-sfc-detects-corrupted-files-again-after-kb4041686.html
« Last Edit: November 06, 2017, 08:55:42 PM by kk159 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #11 on: November 07, 2017, 12:23:30 AM »
I have a laptop with Win 7 x64 Home Premium and it is up to date with all WUs and I don't get that error.

However, yesterday I ran an offboot sfc /scannow from the Recovery Environment Command Prompt and it reported it had repaired some files but as it didn't produce a CBS log as it said it did, I was unable to find what it had repaired.

I would just uninstall that update and change your update setting to Check for but let me choose and then when it is presented again, you can right click on it and select Hide.

I'm going to pass on what you found when running the Package file repair but not choosing any and finding they weren't snagged anymore.

That may need looking into, but glad you're back up and running and I wouldn't condemn SURT as it can be a useful tool.

Offline kk159

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 14
  • Karma: 1
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #12 on: November 15, 2017, 09:57:20 AM »
I uninstalled the buggy KB4041686, and it took 2 reboots  :thinking:

SFC /scannow reports no errors now.  The usb drivers seem working properly, finally.

Previously with KB4041686 installed, SURT can take up to 20min to finish.  Now SURT takes less than 2 min to finish installing.

References:
https://www.askwoody.com/2017/big-problems-with-win7-preview-of-monthly-rollup-kb4041686/
https://www.computerworld.com/article/3236385/microsoft-windows/temporarily-turn-off-windows-automatic-update.html

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6598
  • Location: UK
  • Karma: 100
    • View Profile
Re: Can't install certain Windows 7 Updates
« Reply #13 on: November 15, 2017, 02:33:31 PM »
I haven't had any problems with Win 7 updates, although prior to this month's, following a chkdsk /f I ran an offboot sfc /scannow and it reported it had fixed some files but because I'd done those outside of Windows by booting up with an install disk, I was unable to view the CBS log it said it had produced.

This month's updates have also gone in fine.

Anyway, glad to see that you are sorted.