Remove From My Forums

Unable to install Security Update for Windows 7 for x64-based Systems (KB2847311)

Question

Hi,

With the latest security updates release in october 2013, the update KB2847311 for x64 won't install on several PC (340 out of 1100 using SCCM 2007). I tried to do a manual installation and same result.

Here the cbs.log :

2013-10-24 10:27:05, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateFailed
2013-10-24 10:27:05, Info                  CSI    00000010 Performing 2 operations; 2 are not lock/unlock and follow:
  Install (5): flags: 0 tlc: [65d33ad308914579e80ef4e979752b4e, Version = 6.1.7601.18177, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:154{77}]"Package_2_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-5_neutral_GDR" ncdata: [l:2{1}]"2") thumbprint: (null)
  Install (5): flags: 0 tlc: [449dd8313096e8ea0b2798f052e79452, Version = 6.1.7601.18177, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:154{77}]"Package_3_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-8_neutral_GDR" ncdata: [l:2{1}]"2") thumbprint: (null)
2013-10-24 10:27:06, Info                  CSI    00000011 Component change list:   { 6.1.7601.18032 -> 6.1.7601.18177 Microsoft-Windows-GDI, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { 6.1.7601.18032 -> 6.1.7601.18177 Microsoft-Windows-GDI, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { (null) -> 6.1.7601.18177 65d33ad308914579e80ef4e979752b4e, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
  { (null) -> 6.1.7601.18177 449dd8313096e8ea0b2798f052e79452, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral }
2013-10-24 10:27:06, Error                 CSI    00000012 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6524# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x123e5d0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[116]"\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18032_none_07e15d357138149f.manifest"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x123e650, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000013@2013/10/24:14:27:06.168 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error c0000279 [Error,Facility=(system),Code=633 (0x0279)] originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-10-24 10:27:06, Error                 CSI    00000014 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6523# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemFile(flags = (FileMissingIsOk), da = (DELETE|SYNCHRONIZE), fn = [l:232{116}]"\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18032_none_07e15d357138149f.manifest", sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)
[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000015 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6092# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000016 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #3887# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000017 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #3886# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000018 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #3885# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000019 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #3884# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    0000001a (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #7963# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x123e150->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[116]"\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18032_none_07e15d357138149f.manifest"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x123e1d0, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    0000001b@2013/10/24:14:27:06.417 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error c0000279 [Error,Facility=(system),Code=633 (0x0279)] originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-10-24 10:27:06, Error                 CSI    0000001c (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #7962# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemFile(flags = (FileMissingIsOk), da = (DELETE|SYNCHRONIZE), fn = [l:232{116}]"\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18032_none_07e15d357138149f.manifest", sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)
[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    0000001d (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #7715# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    0000001e (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6529# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    0000001f (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6528# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000020 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6527# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000021 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #6526# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0000279]
2013-10-24 10:27:06, Error                 CSI    00000022 (F) HRESULT_FROM_WIN32(1920) #3676# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80070780]
2013-10-24 10:27:06, Error                 CSI    00000023 (F) HRESULT_FROM_WIN32(1920) #3402# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80070780]
2013-10-24 10:27:06, Error                 CSI    00000024 (F) HRESULT_FROM_WIN32(1920) #3401# 1004416 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x80070780]
2013-10-24 10:27:06, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2013-10-24 10:27:06, Info                  CBS    Setting RollbackFailed flag to 0
2013-10-24 10:27:06, Info                  CBS    Clearing HangDetect value
2013-10-24 10:27:06, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2013-10-24 10:27:06, Info                  CBS    Exec: Restoring driver operations because of a CSI commit failure.
2013-10-24 10:27:06, Error                 CBS    Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x80070780 - ERROR_CANT_ACCESS_FILE]
2013-10-24 10:27:06, Info                  CSI    00000025@2013/10/24:14:27:06.542 CSI Transaction @0x385c80 destroyed
2013-10-24 10:27:06, Info                  CBS    Perf: InstallUninstallChain complete.
2013-10-24 10:27:06, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x80070780 - ERROR_CANT_ACCESS_FILE]
2013-10-24 10:27:06, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070780 - ERROR_CANT_ACCESS_FILE]
2013-10-24 10:27:06, Info                  CBS    WER: Generating failure report for package: Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2, status: 0x80070780, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2013-10-24 10:27:06, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-10-24 10:27:06, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
2013-10-24 10:27:06, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
2013-10-24 10:27:06, Info                  CBS    Reboot mark refs: 0
2013-10-24 10:27:06, Info                  CBS    SQM: Reporting package change for package: Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2, current: Staged, pending: Default, start: Staged, applicable: Installed, target: Installed, limit: Installed, hotpatch status: DisabledBecauseNoHotpatchPackagesInitiated, status: 0x0, failure source: Execute, reboot required: False, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 303, first merged sequence: 303
2013-10-24 10:27:07, Info                  CBS    SQM: Upload requested for report: PackageChangeBegin_Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2, session id: 142859, sample type: Standard
2013-10-24 10:27:07, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2013-10-24 10:27:07, Info                  CBS    SQM: Reporting package change completion for package: Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2, current: Staged, original: Staged, target: Installed, status: 0x80070780, failure source: Execute, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 303, first merged sequence: 303
2013-10-24 10:27:07, Info                  CBS    SQM: execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-10-24 10:27:07, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2, session id: 142862, sample type: Standard
2013-10-24 10:27:07, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2013-10-24 10:27:07, Info                  CBS    Enabling LKG boot option
2013-10-24 10:27:07, Info                  CBS    Exec: End: nested restore point - complete.
2013-10-24 10:27:07, Info                  CBS    Restored system sleep block state: 0x80000000
2013-10-24 10:27:07, Info                  CBS    Exec: Processing complete.  Session: 30331077_474411094, Package: Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2 [HRESULT = 0x80070780 - ERROR_CANT_ACCESS_FILE]
2013-10-24 10:33:34, Info                  CBS    Session: 30331078_81655798 initialized by client Software Explorer.
2013-10-24 10:33:44, Info                  CBS    Session: 30331078_185135798 initialized by client Software Explorer.
2013-10-24 10:33:44, Info                  CBS    Session: 30331078_185605798 initialized by client Software Explorer.

Edited by Eric Pare Thursday, October 24, 2013 3:06 PM

Thursday, October 24, 2013 2:42 PM

Answers

0

Sign in to vote
Also check this, http://support.microsoft.com/kb/822798/en-gb

Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked as answer by Cloud_TS Monday, November 11, 2013 4:17 AM
Thursday, October 24, 2013 2:51 PM

Method 1:Run the Windows Update troubleshooter

To start the Windows Update Troubleshooter, click the following Fix it button:

The Automatically diagnose and fix common problems with Windows Update troubleshooter may automatically fix the problem described in this article.

This troubleshooter fixes many problems. learn more

run now

Method 2: Run the System Update Readiness tool (Checksur.exe)

Download and run the System Update Readiness tool. This tool runs a one-time scan for inconsistencies that may prevent future problems with installing updates or service packs. To download and run the System Update Readiness tool (Checksur.exe), go to the following Microsoft website:
What is the System Update Readiness Tool?
Install the updates again.

If you still cannot install the updates or turn on Windows features, go to Method 2.

Method 3: Install the latest service pack for your version of Windows.

If you do not have the latest service pack for your version of Windows installed, go to the Service Pack Center to download and install the latest service pack.

Click the following link:
Service Pack Center
Click the service pack download link for your version of Windows.
Follow the instructions to download, and install the latest service pack.
Restart your computer.
Try to install the updates again.

If you still cannot install updates or turn on Windows features, go to Method 3.

Method 4: Run the System File Checker (SFC.exe) tool with the sfc /scannow command

To run System File Checker, follow these steps:

Click Start, type cmd in the Start Search box (Windows Vista) or the Search programs and files box (Windows 7), and then press Enter.
Right-click cmd.exe, and then click Run as administrator. Click Continue if you are the administrator or type the administrator password, and then click Continue.
In the command box window, type Sfc /scannow, and then press Enter. Note that there is a space before the forward slash in this command.

The scan may take some time, so be patient. Windows will repair any corrupted or missing files that it finds. If information from the installation DVD is needed to repair the problem, you may be prompted to insert your Windows Vista or Windows 7 DVD.

After the scan is complete, try to install the updates again. If you still can't install the updates or turn on Windows features, go to Method 4.

Method 5: Perform an in-place upgrade

Important You should use an in-place upgrade only as the final alternative if the previous methods don't resolve your issue.
Be aware that it takes the same amount of time to do the upgrade as it does to reinstall Windows. Also, some of your customized Windows settings may be lost during this process.

Note Performing a repair installation will not damage files and applications that are currently installed on your computer.

To perform an in-place upgrade, follow these steps:

Close all applications.
Insert the Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 DVD in the computer's DVD drive.
In the Setup window, click Install Now.

If Windows does not automatically detect the DVD, follow these steps:
1. Click Start, and then type Drive:\setup.exe in the Start Search box. Note: The Drive placeholder is the drive letter of the computer's DVD drive.
2. In the Programs list, click Setup.exe.
3. In the Setup window, click Install Now.
Click Go online to obtain the latest updates for installation (recommended).
Type the product key if you are prompted to do this.
In the Install Windows screen, select the operating system that you want to Upgrade or Inplace.
Click Yes to accept the Microsoft Software License Terms.
In the Which type of installation do you want? screen, click Upgrade.
When the installation is complete, restart your computer.

After your in-place upgrade is complete, try to run Windows Update or try to turn Windows features off and on to see whether the problem is resolved. If you still cannot install Windows Updates or turn on Windows features, go to the following Microsoft website to contact support: http://support.microsoft.com/contactus

Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Proposed as answer by Andre.Ziegler Thursday, October 24, 2013 7:29 PM
Marked as answer by arnavsharma Saturday, November 2, 2013 3:55 AM

Thursday, October 24, 2013 4:48 PM

All replies

0

Sign in to vote

PLease post windowsupdate.log file.
Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thursday, October 24, 2013 2:51 PM
0

Sign in to vote
Also check this, http://support.microsoft.com/kb/822798/en-gb

Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked as answer by Cloud_TS Monday, November 11, 2013 4:17 AM
Thursday, October 24, 2013 2:51 PM

Windowsupdate.log

2013-10-24	10:26:57:354	 568	984	Agent	*************
2013-10-24	10:26:57:354	 568	984	Agent	** START **  Agent: Installing updates [CallerId = wusa]
2013-10-24	10:26:57:354	 568	984	Agent	*********
2013-10-24	10:26:57:354	 568	984	Agent	  * Updates to install = 1
2013-10-24	10:26:57:354	4924	9a4	COMAPI	  - Updates to install = 1
2013-10-24	10:26:57:354	4924	9a4	COMAPI	<<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]
2013-10-24	10:26:57:354	 568	984	Agent	  *   Title = Security Update for Windows (KB2847311)
2013-10-24	10:26:57:354	 568	984	Agent	  *   UpdateId = {2D1BC714-AA4D-4863-AAA2-E8F077CDA9AA}.501
2013-10-24	10:26:57:354	 568	984	Agent	  *     Bundles 1 updates:
2013-10-24	10:26:57:354	 568	984	Agent	  *       {1415CBFE-49EE-4D90-B3A3-7CF0B022F4DB}.501
2013-10-24	10:27:03:952	 568	984	Handler	Attempting to create remote handler process as DNET\AdmPareE in session 2
2013-10-24	10:27:04:108	 568	984	DnldMgr	Preparing update for install, updateId = {1415CBFE-49EE-4D90-B3A3-7CF0B022F4DB}.501.
2013-10-24	10:27:04:171	2568	109c	Misc	===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========
2013-10-24	10:27:04:171	2568	109c	Misc	  = Process: C:\WINDOWS\system32\wuauclt.exe
2013-10-24	10:27:04:171	2568	109c	Misc	  = Module: C:\WINDOWS\system32\wuaueng.dll
2013-10-24	10:27:04:124	2568	109c	Handler	:::::::::::::
2013-10-24	10:27:04:171	2568	109c	Handler	:: START ::  Handler: CBS Install
2013-10-24	10:27:04:171	2568	109c	Handler	:::::::::
2013-10-24	10:27:04:186	2568	109c	Handler	Starting install of CBS update 1415CBFE-49EE-4D90-B3A3-7CF0B022F4DB
2013-10-24	10:27:04:186	2568	109c	Handler	CBS package identity: Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2
2013-10-24	10:27:04:218	2568	109c	Handler	Installing self-contained with source=C:\WINDOWS\SoftwareDistribution\Download\57d50897fd0eca1689e3076b3e3720c2\windows6.1-kb2847311-x64.cab, workingdir=C:\WINDOWS\SoftwareDistribution\Download\57d50897fd0eca1689e3076b3e3720c2\inst
2013-10-24	10:27:07:650	2568	b50	Handler	FATAL: CBS called Error with 0x80070780, 
2013-10-24	10:27:07:696	2568	109c	Handler	FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070780
2013-10-24	10:27:07:696	2568	109c	Handler	:::::::::
2013-10-24	10:27:07:696	2568	109c	Handler	::  END  ::  Handler: CBS Install
2013-10-24	10:27:07:696	2568	109c	Handler	:::::::::::::
2013-10-24	10:27:07:774	 568	fe8	AU	Can not perform non-interactive scan if AU is interactive-only
2013-10-24	10:27:07:774	 568	984	Agent	*********
2013-10-24	10:27:07:774	 568	984	Agent	**  END  **  Agent: Installing updates [CallerId = wusa]
2013-10-24	10:27:07:774	 568	984	Agent	*************
2013-10-24	10:27:07:774	4924	de8	COMAPI	>>--  RESUMED  -- COMAPI: Install [ClientId = wusa]
2013-10-24	10:27:07:774	4924	de8	COMAPI	  - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
2013-10-24	10:27:07:774	4924	de8	COMAPI	  - Reboot required = No
2013-10-24	10:27:07:774	4924	de8	COMAPI	  - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
2013-10-24	10:27:07:774	4924	de8	COMAPI	---------
2013-10-24	10:27:07:774	4924	de8	COMAPI	--  END  --  COMAPI: Install [ClientId = wusa]
2013-10-24	10:27:07:774	4924	de8	COMAPI	-------------
2013-10-24	10:27:12:704	 568	124c	Report	REPORT EVENT: {D36A4F71-26FE-42F4-8C44-4A2176C3822C}	2013-10-24 10:27:07:696-0400	1	182	101	{2D1BC714-AA4D-4863-AAA2-E8F077CDA9AA}	501	80070780	wusa	Failure	Content Install	Installation Failure: Windows failed to install the following update with error 0x80070780: Security Update for Windows (KB2847311).
2013-10-24	10:27:13:156	 568	124c	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-10-24	10:27:13:156	 568	124c	Report	WER Report sent: 7.6.7600.256 0x80070780 2D1BC714-AA4D-4863-AAA2-E8F077CDA9AA Install 101 Unmanaged
2013-10-24	10:27:13:156	 568	124c	Report	CWERReporter finishing event handling. (00000000)

Thursday, October 24, 2013 3:03 PM

Method 1:Run the Windows Update troubleshooter

To start the Windows Update Troubleshooter, click the following Fix it button:

The Automatically diagnose and fix common problems with Windows Update troubleshooter may automatically fix the problem described in this article.

This troubleshooter fixes many problems. learn more

run now

Method 2: Run the System Update Readiness tool (Checksur.exe)

Download and run the System Update Readiness tool. This tool runs a one-time scan for inconsistencies that may prevent future problems with installing updates or service packs. To download and run the System Update Readiness tool (Checksur.exe), go to the following Microsoft website:
What is the System Update Readiness Tool?
Install the updates again.

If you still cannot install the updates or turn on Windows features, go to Method 2.

Method 3: Install the latest service pack for your version of Windows.

If you do not have the latest service pack for your version of Windows installed, go to the Service Pack Center to download and install the latest service pack.

Click the following link:
Service Pack Center
Click the service pack download link for your version of Windows.
Follow the instructions to download, and install the latest service pack.
Restart your computer.
Try to install the updates again.

If you still cannot install updates or turn on Windows features, go to Method 3.

Method 4: Run the System File Checker (SFC.exe) tool with the sfc /scannow command

To run System File Checker, follow these steps:

Click Start, type cmd in the Start Search box (Windows Vista) or the Search programs and files box (Windows 7), and then press Enter.
Right-click cmd.exe, and then click Run as administrator. Click Continue if you are the administrator or type the administrator password, and then click Continue.
In the command box window, type Sfc /scannow, and then press Enter. Note that there is a space before the forward slash in this command.

Method 5: Perform an in-place upgrade

Close all applications.
Insert the Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 DVD in the computer's DVD drive.
In the Setup window, click Install Now.

If Windows does not automatically detect the DVD, follow these steps:
1. Click Start, and then type Drive:\setup.exe in the Start Search box. Note: The Drive placeholder is the drive letter of the computer's DVD drive.
2. In the Programs list, click Setup.exe.
3. In the Setup window, click Install Now.
Click Go online to obtain the latest updates for installation (recommended).
Type the product key if you are prompted to do this.
In the Install Windows screen, select the operating system that you want to Upgrade or Inplace.
Click Yes to accept the Microsoft Software License Terms.
In the Which type of installation do you want? screen, click Upgrade.
When the installation is complete, restart your computer.

Proposed as answer by Andre.Ziegler Thursday, October 24, 2013 7:29 PM
Marked as answer by arnavsharma Saturday, November 2, 2013 3:55 AM

Thursday, October 24, 2013 4:48 PM

1

Sign in to vote

I tried method 1-2-4 and the update won't install

Win7 SP1 is already installed.

Method 5 is a no go for us.

I've heard that Microsoft is receiving many incident regarding MS13-080 and MS13-081. I guess I will keep this update out of our SCCM deployment management until I have more details.

Thursday, October 24, 2013 7:52 PM
0

Sign in to vote

I think MS has already released a fix for that. Can you re-sync SCCM and check for any new patches?
Arnav Sharma | Facebook | Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Friday, October 25, 2013 4:19 AM
0

Sign in to vote

They didn't release a new version yet. I also checked http://support.microsoft.com/kb/2847311/en-us and the last revision date is October 8th

Friday, October 25, 2013 2:30 PM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Answered by:

Unable to install Security Update for Windows 7 for x64-based Systems (KB2847311)

Question

Answers

Method 1:Run the Windows Update troubleshooter

Method 2: Run the System Update Readiness tool (Checksur.exe)

Method 3: Install the latest service pack for your version of Windows.

Method 4: Run the System File Checker (SFC.exe) tool with the sfc /scannow command

Method 5: Perform an in-place upgrade

All replies

Method 1:Run the Windows Update troubleshooter

Method 2: Run the System Update Readiness tool (Checksur.exe)

Method 3: Install the latest service pack for your version of Windows.

Method 4: Run the System File Checker (SFC.exe) tool with the sfc /scannow command

Method 5: Perform an in-place upgrade