inetres.admx Corrupted Since Langa's Non-Destruct Win. 7 Upgrade- Cannot Be Repaired

DKW3 · Mar 24, 2016

Okay,

See the attached, which I had trouble using both 7-zip & Winzip to upload (maybe the file is a bit over 7mb), but WinRar did the trick. I know there are many in need of help here, but I hope you'll have time to see and help me towards wrapping repairs up tomorrow, the multiple issues are making it tough to do some work-arounds. Thanks.

zcomputerwiz · Mar 25, 2016

Code:

2016-03-24 16:35:01, Info                  CSI    000003d2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-inetres-adm_31bf3856ad364e35_9.4.8112.16737_none_6328d01c6a79e95a\inetres.admx do not match actual file [l:24{12}]"inetres.admx" :
  Found: {l:32 b:uoYoD3+uypyRJ3mdL5y8as252yzzCH6BsmYg4/kL/e4=} Expected: {l:32 b:DjclSPQ+c3ju7E53XXW47eR94SH7ICruHSUKg8YAkO0=}
2016-03-24 16:35:01, Info                  CSI    000003d3 [SR] Cannot repair member file [l:24{12}]"inetres.admx" of Microsoft-Windows-InetRes-Adm, Version = 9.4.8112.16737, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-03-24 16:35:01, Info                  CSI    000003d4 [SR] This component was referenced by [l:156{78}]"Package_3_for_KB3124275~31bf3856ad364e35~amd64~~9.4.1.0.3124275-50_neutral_GDR"

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

I will be out of town from 4PM today until Monday, but I'll do my best to reply as quickly as possible today.

DKW3 · Mar 25, 2016

Hope I did this correctly with the code tags, here is the txt file.

zcomputerwiz · Mar 25, 2016

Looks good.

Please run SFC again to verify the files.

SFC Scan

Click on the Start

button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.

DKW3 · Mar 31, 2016

Hi,

Sorry it has taken a while to get back to you; but the issues I'd been having before you created the fixes for me were a walk-in-the-park before that Friday afternoon, when I foolishly installed the wrong Intel Chipset driver (Based on that stupid intel auto-detect!) for my MSI P-33 Combo, which created an infinite loop that defied the start-up repair, F8 advanced & Restore point options, & even Macrium Restores of late Feb. & early March Windows images I'd created.

I had to end-up carefully saving all of the files and programs I could, doing a clean re-install of Windows, install the original MSI chipset drivers from my DVD, do a Windows upgrade, then download all of the Windows & 3rd Party updates; it was only yesterday that I was finally at a point to implement your custom SFC.fix for me, and had to do the earlier Checksur fix with the packages you gave me, over again.

For now, I have refrained from re-installing Office 2010 & Acrobat Pro, since both programs once again got corrupted at some point with an update I did before doing your fixes, of which I'm clueless as to why.

Most particularly the Office 2010 re-install with all of the updates, though the updated Microsoft-Tech version setup I was given after they repaired it has much less to update than with the original disc I have, is SO tedious to keep having to do over and over again. I wish I knew what causes the corruption proactively to avoid the problem as much as possible, & I use every known method of completely cleaning the install out each time before re-installing, believe me.

But it looks like this can be a frequent problem for unlucky users with all versions of windows & Office, with no easy answers.

Anyway, only the Secpol.msc issue remains, with the only other difference after the 2nd Check-sur fix, is that the KB3104002 package now seems to "not be applicable" to my windows installation, if that is going to make a negative difference with my installation. See all 3 current result logs attached. Thanks.

-DKW3

DKW3 · Apr 1, 2016

Just to let you know, I re-installed Office & all of the updates Thursday, along with Acrobat Pro, am hoping for the best, there.

I just checked "Event Viewer" after getting the "The Group Policy settings That Apply..." Secpol.msc error again, and THAT is working 100% now, thanks.

zcomputerwiz · Apr 1, 2016

Wow, quite a bit has happened!

Good job on getting your machine running again :thumbsup2:

Try running esentutl /p %windir%\security\Database\secedit.sdb
then run esentutl /d %windir%\security\Database\secedit.sdb

After this, restart your machine and see if gpedit produces the same error message.

DKW3 · Apr 1, 2016

Hello, and thanks.

Below are the Results, based on the 1st run command (I had run a sucessful chkdsk /r before I booted up this morning), please advise:

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.1
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
Database: C:\Windows\security\Database\secedit.sdb
Temp. Database: TEMPREPAIR4992.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the 'Recovery' operation

Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................

Integrity check successful.

Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.

Operation completed successfully in 10.920 seconds.

C:\Users\xxxxxxxxx>

DKW3 · Apr 4, 2016

Tried it again after doing some PC cleanup, and FYI, everything else is still clean on the pc, but now I'm getting this:

Error: Access to source database 'C:\Windows\security\Database\secedit.sdb' fail
ed with Jet error -1032.

"Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access fi
le, the file is locked or in use) after 20.46 seconds."

zcomputerwiz · Apr 4, 2016

I would suspect the file is locked by another application.

Disable your antivirus software and try a clean boot to check that theory:
Clean Boot

Click the Start button, then type msconfig in the search box.
Click msconfig in the results list.
On the General tab, click the Selective startup option, and then click to clear the Load startup items check box.
On the Services tab of the System Configuration dialog box, click to select the Hide all Microsoft services check box, and then tap or click Disable all.

https://support.microsoft.com/en-us/kb/929135

DKW3 · Apr 4, 2016

Hi, see the attached. I should ask, if there is anything in particular I should be configuring in my GPO settings for secpol that could pertain to this error, or something as to where I may have accidentally added a particular user or group for my "permissions", that would make my PC think I have a server set-up, which I currently don't?

In any case, I am Rebooting now, and hoping for the best. One more little thing; Since Friday, I am getting a "Item not Found" error whenever I move or rename something on my desktop, though if I hit "Try Again", it works.

DKW3 · Apr 4, 2016

Nope, didn't work.

zcomputerwiz · Apr 6, 2016

Have you configured any local security policies on this machine?

DKW3 · Apr 6, 2016

Hi,

Yes, but not as many as the extensive GPO policies, which do not come-up with any issues, only Secpol. So I'm hoping that Secpol can be fixed separately, or it will have to be 3 hours of resetting all of those GPO settings as a last resort.

DKW3 · Apr 6, 2016

By the way, I just did a prescan with Tweaking all-in-one because my WSUS has been hanging doing updates lately, & it states that 366 files are missing of that SFC won't be able to replace them all, and there are Reparse issues as well, of that I don't even know the definition of. I had 1286 missing files initially that sfc /scannow and ran SFC.fix took care of the bulk except the remaining 366 but hopefully, another sfc scan can help, and Tweaking can help with all of the latter reparse issues, see below:

│ These Files Are Missing: (Total: 366)
C:\Windows\servicing\Packages\Microsoft-Windows-RDP-BlueIP-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.2.7601.16415.cat
C:\Windows\servicing\Packages\Microsoft-Windows-RDP-BlueIP-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.2.7601.16415.mum
C:\Windows\servicing\Packages\Microsoft-Windows-RDP-BlueIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.2.7601.16415.cat
C:\Windows\servicing\Packages\Microsoft-Windows-RDP-BlueIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.2.7601.16415.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_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_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_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_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_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_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_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_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_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_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_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_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_117_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_117_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_118_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_118_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_119_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_119_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_120_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_120_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_121_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_121_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_123_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_123_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_124_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_124_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_125_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_125_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_126_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_126_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.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_127_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_127_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_13_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_13_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_13_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_13_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_13_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_13_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_14_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_14_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_14_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_14_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_14_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_14_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.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.15.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.15.2.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_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3032655~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_KB3093513~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3093513~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3099862~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3099862~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3121461~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB3121461~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_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.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_KB3072633~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3072633~31bf3856ad364e35~amd64~~6.1.1.1.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_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.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_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3124000~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3124000~31bf3856ad364e35~amd64~~6.1.1.0.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_38_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_38_for_KB3121212~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_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.15.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.15.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_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3032655~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_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.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_3_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3124000~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3124000~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_51_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_51_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_51_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_51_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_52_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_52_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_52_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_52_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_53_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_53_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_53_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_53_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_54_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_54_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_54_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_54_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_58_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_58_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_58_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_59_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_59_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_59_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_59_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_60_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_60_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_60_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_60_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_61_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_61_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_61_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_61_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_62_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_62_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_62_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_62_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_63_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_63_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_63_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_63_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_64_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_64_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_64_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_64_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_73_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_73_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_73_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_73_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_73_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_73_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_74_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_74_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_74_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_74_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_74_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_74_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_74_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_74_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_79_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_79_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_79_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_79_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_91_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_91_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_91_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_91_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_92_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_92_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_92_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_92_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.15.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.15.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.15.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.15.2.mum
C:\Windows\servicing\Packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3006226_SP1~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3006226_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3032655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3032655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3065987_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3065987_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3069392_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3069392_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3072633_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3072633_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3072633~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3072633~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3076895_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3076895_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3076895~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3076895~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3077715_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3077715_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3077715~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3080446_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3080446_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3080446~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3081320_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3081320_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3081320~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3087918_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3087918_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3087918~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3087918~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3093513_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3093513_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3093513~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3093513~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3097877_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3097877_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3099862_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3099862_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3099862~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3099862~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3100213_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3100213_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3100213~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3100773_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3100773_RTM~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3100773~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3101246_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3101246_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3101246~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3101746_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3101746_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3102810_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3102810_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3104002_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3104002_RTM~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3104002~31bf3856ad364e35~amd64~~9.4.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3112343_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3112343_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3112343~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3121212_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3121212_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3121212~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3121461_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3121461_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3121461~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3121461~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3121918_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3121918_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3121918~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3124000_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3124000_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3124000~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3124000~31bf3856ad364e35~amd64~~

------------------------------------------------------------------------------------------------------
Missing Default Reparse Point: (Original Path: C:\ProgramData\Application Data) (Target Path: C:\ProgramData)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\mnt\Documents\My Music) (Target Path: C:\Users\mnt\Music)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\mnt\Documents\My Pictures) (Target Path: C:\Users\mnt\Pictures)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Missing Default Reparse Point: (Original Path: C:\Users\mnt\Documents\My Videos) (Target Path: C:\Users\mnt\Videos)
│ A Default Reparse Point is missing and this can cause problems on the system.
│
│ Problems were found with the Reparse Points.
│ You can use the Repair Reparse Points Tool at the bottom of this Window to try and fix these problems.

zcomputerwiz · Apr 6, 2016

Please run the System Update Readiness Tool. Once it finishes, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

DKW3 · Apr 6, 2016

Will do.

DKW3 · Apr 6, 2016

With all of the missing KB updates, how long do you estimate this should be running? It's been on "Initializing installation..." & "Installing" for almost an hour now, & I just want to ensure that it's not hanging up...

zcomputerwiz · Apr 6, 2016

It usually is rather quick but can take quite a while. If it runs longer than 2 hours cancel it and restart the computer, then run it again.

DKW3 · Apr 6, 2016

Okay, thanks.

inetres.admx Corrupted Since Langa's Non-Destruct Win. 7 Upgrade- Cannot Be Repaired

Contributor

Attachments

Windows Update Expert

Contributor

Attachments

Windows Update Expert

Contributor

Attachments

Contributor

Windows Update Expert

Contributor

Contributor

Windows Update Expert

Contributor

Attachments

Contributor

Windows Update Expert

Contributor

Contributor

Windows Update Expert

Contributor

Contributor

Windows Update Expert

Contributor