Messages

1

Tweaking.com Support & Help / Re: win 7 major screw up after running windows repair v4.9.0 pro

« on: June 23, 2020, 11:59:05 am »

Another profile?  User profile?

I don't know which repair option caused this icon bug / green bar of death.  Maybe the ones in file associations?
Should be reproduceable on a lot of machines.

2

Tweaking.com Support & Help / win 7 major screw up after running windows repair v4.9.0 pro

« on: June 22, 2020, 05:33:47 pm »

I have recently been having AMD driver issues so I decided to do a clean install of the driver, then run all repairs using windows repair v4.9.0 pro in safe mode.
Did all pre-repair steps except I forgot to back up the registry.
My system is win 7 x64 SP1 ultimate.

After the repair, my OS's folder icon associations are completely messed up.  They are normal in safe mode, but in regular mode, the following issues suddenly appear:
When I open 'My Computer', none of the drives shows up.
When I launch control panel, there is 0 icon in it until I wait a minute or 2.
When I open any folder, all icons(.png, .mp4, .doc, .txt etc.) are blank.  After a few refresh, the green bar in the address bar shows up and it always takes longer than 3 minutes for the icons to display.  That folder only has 10 files.  I got very fast CPU and SSD.
The above issue repeats the next time I open the same folder.

I tried to reset the icon cache and restore win 7 default folder templates, none of them helped.

Searched on sevenforums and didn't find a solution.

Then I realize I have a windows generated registry back up in c:\windows\system32\config\RegBack
The back up was created just before I used windows repair pro's repair all function.
I manually restored the 5 registry files using cmd before getting into the OS, and the icon / explorer problems are solved.

I'm 100% sure your software was the reason for this mess up, spent the whole afternoon trying to fix it.

3

Tweaking.com Support & Help / Re: Kaspersky Says bat file is Trojan?

« on: November 27, 2017, 07:32:59 pm »

I remember my Kaspersky reported a similar file when booting to safe mode

You can submit the file as a false positive here:
https://virusdesk.kaspersky.com/

4

Tweaking.com Support & Help / Re: trying to run AIO on a known corrupt HDD

« on: November 24, 2017, 04:05:06 pm »

I would back up the data before running chkdsk

/r checks for bad sectors and it's a lot of read actions, much slower than /f.  If the hdd is about to fail, a chkdsk /r may fail the hdd

Check your hdd SMART data and see if there is anything funny

When running chkdsk on an external device, use diskpart to obtain the correct drive letter

If your hdd is Seagate, I would suggest using SeaTools

5

General Computer Support / Re: Can't install certain Windows 7 Updates

« on: November 15, 2017, 09:57:20 am »

I uninstalled the buggy KB4041686, and it took 2 reboots 

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

6

Tweaking.com Support & Help / Re: Windows Defender blocked 4.09 as threat

« on: November 06, 2017, 08:35:49 pm »

Kaspersky reported Windows Repair generated a temp file right after I chose "Reboot to Safe Mode"

7

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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

8

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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...

9

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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.

10

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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

11

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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

12

General Computer Support / Re: Can't install certain Windows 7 Updates

« 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  , 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.

13

Tweaking.com Support & Help / Re: Registry compressor crashes upon compression

« on: November 04, 2017, 05:44:55 pm »

I have never tried renaming the ntuser.dat, will Windows allow me to do that?
Sometimes inside C:\Windows\System32\config, one or two registry hives will not get replaced either, leaving .new files.
I think when it did replace the old one, it will leave .old files.

I strongly suspect that it's the DEP preventing the program from making changes to the system.  Today I was trying to run a 1997 game, upon clicking on it, the game program instantly stopped working.  So I added that program to the DEP's exclusion list, and I was able to run the game.  I tried adding registry compressors's executable to DEP's exclusion list, but I still get the program has stopped working message after I hit compress.  And I end up getting ntuser.dat.new again.

14

General Computer Support / 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?

15

Tweaking.com Support & Help / Registry compressor crashes upon compression

« on: November 04, 2017, 10:43:05 am »

Hi,

     I selected the Best compression setting and "Restart the system after finished" option.  After analyzing the registry and clicking the Compress button, Windows prompts that the registry compressor has stopped working.  The system automatically reboots within the next minute.  Is this kind of behavior normal?  I have closed every other program before running the registry compressor.

     After the reboot, it created a smaller ntuser.dat.new file, but the old one didn't seem to get replaced, since the old one has a larger size.

     I'm using Win 7 SP1 x64 Ultimate, and the latest registry compressor v1.1.0

     The crash problem can be reproduced every time, and it happens to both my host pc, and a virtual machine with a clean install of Win 7 running on the host pc.

16

Tweaking.com Support & Help / Re: windows update repair works only partially

« on: April 20, 2016, 05:49:00 pm »

Aha,

I have been having very similar issues on April 19, 2016, my OS is win7 x64 sp1

First I found my win update took forever to find any updates(it failed), after I cleaned some win update backups files, I got into an infinite configure windows 35% loop at login.  Couldn't get into my system.
All system restore failed.  Had to use DoS to recover.
Then I used Tweaking.com's repair to fix win update, afterwards it could find updates.

However, after successfully installing 30+ updates, I'm stucked with 4 failed updates:
1. An IE 11 update, but I have already got latest version, that's why it failed to update with error 9C48.  From the log, I see "A newer version of Internet Explorer is already installed on the system".  SURT and Windows Repair could not fix this problem.  I guess the only solution is to reinstall IE 11.
2. KB2574819 successfully installed, but it reverts back after each restart...  I ran SURT, after 3 hours, this problem was fixed.
3. The Feb 2016 security updates KB3126593 and KB3126587 failed with error code 80070490: error not found.  SURT didn't fix this problem, nor did Windows Repair.
Microsoft Fix It never fixed any of the above issues...