[SOLVED] Problem Installing Windows 7 Security Update for x64-based Systems (KB3067903)

sdjoseph · Aug 12, 2015

Tried installing the update through Windows update and got an error code (80073712).
I ran SFCfix and here is the log file for that:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-08-12 10:49:24.460
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
WARNING: Manifest damage on component "amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941". See CBS logfile for more details.

FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\utc.app.json.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\telemetry.ASM-WindowsDefault.json.

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 4
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 2
SURT total detected corruption count: 30
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-08-12 11:18:13.117
----------------------EOF-----------------------

I zipped the CBS log file but I can't seem to attach it here. The upload tool just spins and spins but nothing is ever uploaded.

Can someone help me with this?

Thanks,
Susan

Aura · Aug 12, 2015

Hi sdjoseph :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;

Download the right version of SURT for your system;
- Your version of Windows is:
Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
Attach this log in your next reply;

Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)

sdjoseph · Aug 12, 2015

Aura said:
Hi sdjoseph :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;

Download the right version of SURT for your system;

Your version of Windows is:

Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);

On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;

Attach this log in your next reply;

Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)

OK I downloaded the tool and ran it. I have attached the file (CheckSUR.log) to this message.

SusanView attachment CheckSUR.log

Aura · Aug 12, 2015

Good :) Follow the instructions below please.

System Update Readiness Tool (SURT) - Fix

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to fix the errors reported by the System Update Readiness Tool (SURT);

Download the attached archive file, Packs.zip and save it on your Desktop;
Once it's downloaded, right-click on it and select Extract All...;
Check the Show extracted files when complete checkbox, and click on Extract;
On completion, a folder will open with two folders inside it, Manifests and Packages;
- Copy and paste the files of the Manifests folder (if there are any) inside C:\Windows\Temp\CheckSur\winsxs\Manifests
- Copy and paste the files of the Packages folder (if there are any) inside C:\Windows\Temp\CheckSur\servicing\Packages
Run the System Update Readiness Tool (SURT) again;
On completion, attach the log located at C:\Windows\Logs\CBS\CheckSUR.log in your next reply;

View attachment Packs.zip

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

Download SFCFix and move the executable on your Desktop;
On your Desktop, right-click and select New, then Text Document. Give it the name SFCFixScript (it should be a .txt) extension;

Open the SFCFixScript.txt file you just created, and copy/paste the following in it;

Code:

Trace::
amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30
x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa
amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941
x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_beeed4ad7884e80b

Save any work you have open, and close every programs;
Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it;
SFCFix will launch, let it complete;
Once done, a file will appear on your Desktop, called SFCFix.txt;
Open the file, then copy and paste its content in your next reply;

Your next reply should include:

CheckSUR.log (attached or copy/pasted here);
SFCFix log (attached or copy/pasted here);

sdjoseph · Aug 12, 2015

OK so I did both but the second one didn't seem to work correctly. Here are the logs:

CheckSUR.log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-08-12 15:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_13_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_13_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_13_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_14_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_14_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_14_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_73_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_73_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_73_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_74_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_74_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_74_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3065987_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB3065987_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB3065987_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB3065987~31bf3856ad364e35~amd64~~6.1.2.0.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7601.18917_none_a3f78987ce3af290.manifest amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7601.18917_none_a3f78987ce3af290
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7601.18917_none_a3f78987ce3af290.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_cd770cee78d61d2b.manifest amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_cd770cee78d61d2b
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_cd770cee78d61d2b.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_d7cbb740ad36df26.manifest wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_d7cbb740ad36df26
(fix) CSI Manifest All Zeros CSI File Replaced File: wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18917_none_d7cbb740ad36df26.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_e7079fd814572cf4.manifest amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_e7079fd814572cf4
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_e7079fd814572cf4.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_f15c4a2a48b7eeef.manifest wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_f15c4a2a48b7eeef
(fix) CSI Manifest All Zeros CSI File Replaced File: wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18917_en-us_f15c4a2a48b7eeef.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_7781cd2f1e8d4f27.manifest amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_7781cd2f1e8d4f27
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_7781cd2f1e8d4f27.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_81d6778152ee1122.manifest wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_81d6778152ee1122
(fix) CSI Manifest All Zeros CSI File Replaced File: wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18917_none_81d6778152ee1122.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.18917_none_e765d2a26515c428.manifest amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.18917_none_e765d2a26515c428
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.18917_none_e765d2a26515c428.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa

And the SFCFix.txt:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-08-12 16:04:29.701
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\HomeComputer\Desktop\SFCFixScript.txt [0]

Trace::
Failed to trace component amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30 with return code -3.

Failed to trace component x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa with return code -3.

Failed to trace component amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941 with return code -3.

Failed to trace component x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_beeed4ad7884e80b with return code -3.
Trace:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-08-12 16:04:30.325
Script hash: pRkVGre2RaaxTZUUuzJ3ElgirA72S8gKgx5Vw6o0UYk=
----------------------EOF-----------------------

Aura · Aug 12, 2015

SFCFix couldn't trace the manifests files to the package they come from (in other words, the update). It's fine though, I found them on my VM :) Follow the instructions below please.

System Update Readiness Tool (SURT) - Fix

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to fix the errors reported by the System Update Readiness Tool (SURT);

Download the attached archive file, Packs.zip and save it on your Desktop;
Once it's downloaded, right-click on it and select Extract All...;
Check the Show extracted files when complete checkbox, and click on Extract;
On completion, a folder will open with two folders inside it, Manifests and Packages;
- Copy and paste the files of the Manifests folder (if there are any) inside C:\Windows\Temp\CheckSur\winsxs\Manifests
- Copy and paste the files of the Packages folder (if there are any) inside C:\Windows\Temp\CheckSur\servicing\Packages
Run the System Update Readiness Tool (SURT) again;
On completion, attach the log located at C:\Windows\Logs\CBS\CheckSUR.log in your next reply;

Packs.zip

sdjoseph · Aug 13, 2015

OK I did what you asked and here is the log file results:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-08-13 08:47

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa
(fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941.manifest amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941
(fix) CSI Manifest All Zeros CSI File Replaced File: amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_1b0d703130e25941.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_beeed4ad7884e80b.manifest x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_beeed4ad7884e80b
(fix) CSI Manifest All Zeros CSI File Replaced File: x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.23075_none_beeed4ad7884e80b.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab

Summary:
Seconds executed: 746
Found 4 errors
Fixed 4 errors
CSI Manifest All Zeros Total count: 4
Fixed: CSI Manifest All Zeros. Total count: 4

Aura · Aug 13, 2015

Good, SURT now returns a clean log. Let's see if it's the same for SFC.

System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;

On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select

Run as Administrator
On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
Enter the command below and press on Enter;
Code:
```
sfc /scannow
```
Note: There's a space between "sfc" and "/scannow";
Once the scan is complete, enter the command below and press on Enter
Code:
```
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
```
A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.

sdjoseph · Aug 13, 2015

OK, I did everything and here is the link to the file in dropbox:

https://www.dropbox.com/s/k4suncdral5ht1s/cbs.txt?dl=0

Aura · Aug 13, 2015

Alright the CBS.log is clean. Can you try to install your Windows Update again? If they fail, upload the following files for me please.

C:\Windows\WindowsUpdate.log
C:\Windows\Logs\CBS\CBS.log

sdjoseph · Aug 13, 2015

Yeah!!! It worked!! Thank you for all your help. It is so annoying that it is this hard to patch Microsoft OS.

Aura · Aug 13, 2015

No problem joseph, you're welcome :) Luckily we are here to assist users when Microsoft can't

Search

Search

[SOLVED] Problem Installing Windows 7 Security Update for x64-based Systems (KB3067903)

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst

sdjoseph

Member

Aura

Sysnative Staff, Security Analyst