[SOLVED] Win 7 x64 update problem

S

smagyar

Member
Joined
May 18, 2015
Posts
6
Hi there,

I have a problem with the a view Microsoft updates (see below example) and SFCFix reports a problem with SP1 for an AMD processor (see also below), but I have a Intel 64 bit processor
Hope that someone can help me because most of the security updates are failing.

Thanks!

==Update details==================================
Security Update for Microsoft .NET Framework 4.5, 4.5.1 and 4.5.2 on Windows 7, Vista, Server 2008, Server 2008 R2 x64 (KB3023224)Installation date: ‎18-‎5-‎2015 18:06
Installation status: Failed
Error details: Code 643
Update type: Important
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.
More information:
MS15-048: Description of the security update for the .NET Framework 4.5, 4.5.1, and 4.5.2 on Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, Windows Vista Service Pack 2, and Windows Server 2008 Service Pack 2: May 12, 2015
Help and Support:
Microsoft Support

==SFCFix.txt=====================================

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-19 08:27:20.502
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


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


Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2015-05-19 08:29:13.416
----------------------EOF-----------------------
 
I tried to upload the zipped CBS file but I was not able to.
The size of the file is 850MB, I guess this is too big for uploading.

I was able to upload the file CheckSUR.log
 

Attachments

Hi and welcome to Sysnative. Sorry for the delay.

I have a problem with the a view Microsoft updates (see below example) and SFCFix reports a problem with SP1 for an AMD processor (see also below), but I have a Intel 64 bit processor
Click to expand...

AMD is referring to a 64-bit architecture. It doesn't matter that you have an Intel. If you have a 64-bit processor, the internals refer to it as AMD. It goes way back as AMD was the first ones to build a 64-bit processor. So no worries here.

I see you have some corruption/missing files. Let's try to resolve that first. Please do the following.

Step#1 - Fix Corrupt Files
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.
  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files). If the Manifests folder doesn't exist within Winsxs you will need to create it.
    C:\Windows\Temp\CheckSur\Winsxs\Manifests
  6. Open the Packages folder and copy the files into the following folder (if there are any files). If the Packages folder doesn't exist within Servicing you will need to create it.
    C:\Windows\Temp\CheckSur\Servicing\Packages
  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, zip up and attach the following log file:
    C:\Windows\Logs\CBS\CheckSUR.persist.log

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 

Attachments

Hi Brian,

Many thanks for your reply.

I ran SURT again after copying the files you delivered in the zip file to the specified folders.
Please find attached the CheckSUR.Persist.zip file.
 

Attachments

OK, 15 more items to fix. Let's see how this goes. Please do the following.

Step#1 - 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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.


Items for your next post
1. SFCFix log
2. CheckSUR log
 

Attachments

Thanks again,
below the content of SFCFix.txt and attached the CheckSUR.log

==SFCFix.txt=====================================

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-22 16:14:21.309
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\stef\Downloads\SFCScript.zip [0]
Not using an additional text script file.

AutoAnalysis::
Success: File Placement Mode successfully identified and repaired all files and folders.
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2015-05-22 16:14:21.529
Script hash: +usgP+WV6uPcWw0l1flWC9+DLgGQLymPHe3KswlsoK0=
----------------------EOF-----------------------
 

Attachments

Oops, the wrong file was used. That was my fault. Please do the following. Please note that you will be using the file named SFCScript.txt this time.

Step#1 - 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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Items for your next post
1. SFCFix.txt
2. CheckSUR.log
 

Attachments

No problem, I am very happy that you are helping me.
below the content of SFCFix.txt and attached the CheckSUR.log

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-22 17:47:26.886
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\stef\Downloads\SFCScript.txt [1]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8add0fe0248..03e7e6e0a59_31bf3856ad364e35_6.1.7601.22920_9799a209c98b3fb2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d03182fa59d..97f7d297c91_31bf3856ad364e35_6.1.7601.18714_3d70ca2c32264204.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6246fa0aeaa..5d0158d591c_31bf3856ad364e35_6.1.7601.22920_63d4870363cb6c7c.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2b3b767663b..a5fbe895123_31bf3856ad364e35_6.1.7601.22920_8d0e2849d279ee12.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\497cf4fa8ae..e54db17e8e7_31bf3856ad364e35_6.1.7601.22920_d3172f782255b0d5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\579ec09eb62..1bb4514862b_31bf3856ad364e35_6.1.7601.22920_8d482f0d7d25e919.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8bd69a8e176..76ec728ad19_31bf3856ad364e35_6.1.7601.22920_5c9720cedd77da80.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9cce02942d3..5a76274521e_31bf3856ad364e35_6.1.7601.18714_2ebd55e9aec9f2cb.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6e9f1e04718..6cdda2711c9_31bf3856ad364e35_6.1.7601.18714_414c3dac33e74a26.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3f8918924e0..1a36765a72b_31bf3856ad364e35_6.1.7601.18714_2e0e9b2f308526bd.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7e2de961441..92c21ee6832_31bf3856ad364e35_6.1.7601.18714_8b2239a1a679d884.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7138f3e9cdd..2e2ae3c9226_31bf3856ad364e35_6.1.7601.18714_d564faa274879f4d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1a69969935e..5d5a4761e85_31bf3856ad364e35_6.1.7601.22920_d8432940a8314228.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9ffb23d582c..3d361a899fa_31bf3856ad364e35_6.1.7601.18714_4196a08c64dd770d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\836be6b443c..1448cf760f6_31bf3856ad364e35_6.1.7601.22920_bee99cefd63899d2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8add0fe0248..03e7e6e0a59_31bf3856ad364e35_6.1.7601.22920_9799a209c98b3fb2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d03182fa59d..97f7d297c91_31bf3856ad364e35_6.1.7601.18714_3d70ca2c32264204.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6246fa0aeaa..5d0158d591c_31bf3856ad364e35_6.1.7601.22920_63d4870363cb6c7c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2b3b767663b..a5fbe895123_31bf3856ad364e35_6.1.7601.22920_8d0e2849d279ee12.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\497cf4fa8ae..e54db17e8e7_31bf3856ad364e35_6.1.7601.22920_d3172f782255b0d5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\579ec09eb62..1bb4514862b_31bf3856ad364e35_6.1.7601.22920_8d482f0d7d25e919.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8bd69a8e176..76ec728ad19_31bf3856ad364e35_6.1.7601.22920_5c9720cedd77da80.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9cce02942d3..5a76274521e_31bf3856ad364e35_6.1.7601.18714_2ebd55e9aec9f2cb.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6e9f1e04718..6cdda2711c9_31bf3856ad364e35_6.1.7601.18714_414c3dac33e74a26.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3f8918924e0..1a36765a72b_31bf3856ad364e35_6.1.7601.18714_2e0e9b2f308526bd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7e2de961441..92c21ee6832_31bf3856ad364e35_6.1.7601.18714_8b2239a1a679d884.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7138f3e9cdd..2e2ae3c9226_31bf3856ad364e35_6.1.7601.18714_d564faa274879f4d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1a69969935e..5d5a4761e85_31bf3856ad364e35_6.1.7601.22920_d8432940a8314228.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9ffb23d582c..3d361a899fa_31bf3856ad364e35_6.1.7601.18714_4196a08c64dd770d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\836be6b443c..1448cf760f6_31bf3856ad364e35_6.1.7601.22920_bee99cefd63899d2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 26 datablocks.
Finish time: 2015-05-22 17:47:27.316
Script hash: +usgP+WV6uPcWw0l1flWC9+DLgGQLymPHe3KswlsoK0=
----------------------EOF-----------------------
 

Attachments

Yes you saved my computer :)
The updates were installed successfully.
Many thanks for your help.

Stef
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top