[SOLVED] Unable to install Windows Management Framework 4.0

[webguy]

Having trouble updating computer to support Microsoft Windows Framework 4.0. When application launches get an error in the event log:

Windows update "Update for Windows (KB2819745)" could not be installed because of error 2147942438 "Reached the end of the file." (Command line: "wusa.exe "Windows6.1-KB2819745-x64-MultiPkg.msu")

Ran both SFC and System Update Readiness Tool. Both found issues but were unable to resolve problems. Appears to be an issue with one of the updates and the manifest files.

Finally ran SFCFix.exe as recommended by an number of other threads with similar issues, results below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-28 16:42:43.329
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Manifest damage on component "amd64_3a242cade673376d706603018d5cd359_31bf3856ad364e35_11.2.9600.17633_none_a1adfffe274471c9". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_4784084f494712101fec650c80ad955b_31bf3856ad364e35_11.2.9600.17633_none_4811ab31b40e1b34". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d8149b90c00a0b976076d4a3abb1b5ee_31bf3856ad364e35_11.2.9600.17633_none_44bade3dbcb91dcb". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.2.9600.17633_none_3e5fd1f886cd80df". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d3bc8be70b2f4a368440ffead8717eca_31bf3856ad364e35_11.2.9600.17633_none_fbd3a93809a38e64". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d6767569f493a0c6fff0278dc2ecb454_31bf3856ad364e35_11.2.9600.17633_none_8e63ccdaf6d81421". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_08f1c2f2cf9e320f2b91310801fe48b1_31bf3856ad364e35_11.2.9600.17633_none_d54383d5265dc02b". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_4e4ebdd6ea46fdcfa09484d7703161b0_31bf3856ad364e35_11.2.9600.17633_none_777894d64819bad8". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d525d505e4e717b0a362b5746aa68248_31bf3856ad364e35_11.2.9600.17633_none_cb300f88b4d2f9f1". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_0fa62f353d552d3d0199ebe78eba88c8_31bf3856ad364e35_11.2.9600.17633_none_2a1694d5414c2ff8". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_39d5d8d3317fda2058f0012131127146_31bf3856ad364e35_11.2.9600.17633_none_bac6b845009371fe". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_5cbc3fa886d3440974ae237e0064c143_31bf3856ad364e35_11.2.9600.17633_none_932f5edc97bb1888". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_c6c53c098a47c515558b4a68c089ee10_31bf3856ad364e35_11.2.9600.17633_none_1ac74758065425c8". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_22eeddadbdb2387883b32147bf169699_31bf3856ad364e35_11.2.9600.17633_none_8b93590cf2721965". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_233cda474d1449597302e0a1cbc7429b_31bf3856ad364e35_11.2.9600.17633_none_2a014e86e8f5abfa". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_28ec361063b91ba8cba945cb65db70c8_31bf3856ad364e35_11.2.9600.17633_none_55f5feb19b2d6788". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d6488218d79101b2f1c3981ff8551c00_31bf3856ad364e35_11.2.9600.17633_none_cd8e723586789dbe". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_a491d6029f7932ff6361b1fe56ceffd0_31bf3856ad364e35_11.2.9600.17633_none_c0c036035e6d306c". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_d9d20e8cfc86173df7845c73f8826442_31bf3856ad364e35_11.2.9600.17633_none_46f5d9f2b44ae5c2". See CBS logfile for more details.
WARNING: Manifest damage on component "amd64_c6660373e20ac054dfcdd1e7f2c50028_31bf3856ad364e35_11.2.9600.17633_none_f96fb6c9e158322a". See CBS logfile for more details.








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








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-07-28 16:43:00.734
----------------------EOF-----------------------

Any assistance would be greatly appreciated. Would prefer not to have to re-image this machine.

Paul

 

[Aura]

Hi webguy,

Do you still need assistance with this issue?

 

[webguy]

Yes, this issue is still occurring on this specific device. If there is a solution it would be great as the user is remote and reimaging the device is not necessarily an option.

 

[Aura]

Alright in that case let's get a more recent CheckSUR log.

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: Windows 7 x64
• 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)

 

[webguy]

Attached it the most recent CheckSUR.log as requested.

 

[Aura]

Alright, 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

 

[webguy]

As requested here is the updated logs.

 

[Aura]

Good :) Now please run SFC and provide me the CBS.txt log after.

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 and Windows 10, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
• Enter the command below and press on Enter;
  

  sfc /scannow

  Note: There's a space between "sfc" and "/scannow";
• Once the scan is complete, enter the command below and press on Enter
  

  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 have the information from the scan anymore. So archive it and upload it as soon as you can.

 

[webguy]

Here is the updated log.

 

[Aura]

Alright, SFC returned a clean CBS.log.

Now, where are you downloading WMF 4.0 from?

 

[webguy]

Directly from Microsoft. I will try to install now. And let you know.

 

[Aura]

Alright :) If it fails to install, upload the two logs below so I can review them.

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

 

[webguy]

Looks like everything installed correctly. Thank you for your assistance. Saved me from re-imaging the machine.

 

[Aura]

No problem webguy, you're welcome :)