Update problem after installing new CPU

The real problem comes from the KB2952664. The missing files reported by SURT is what's holding you back. I cannot source them because they come from 4 different versions of the KB2952664, and it's really, really hard to find older versions of an update (you need to find somewhere on the web the direct download link for it), even less when it was never in the Microsoft Download Center. I'll ask my colleagues if they can source these files, otherwise we'll have to clean the Registry manually from the KB2952664, but it'll be a real pain :P
 
Thing is that I have found all packages that are reported missing in SURT log (all file versions) and after running SURT again I have no result in fixing it. It seems to me that this may be result of my previous effort to remove/disable this Microsoft malware. At first I solved it by removing it from startup (schedule tasks) by deleting entries there. t worked for some time but bugger started to come back using some different scheme, so I changed ownership of files in GWX directory and deleted files there. Again it was good for some time when it started to appear again - with no GWX.exe on system. So I thought they must have started using it as rootkit, so I found all in one solution called "GWX Control Panel" which effectively disabled it and deleted unwanted malware installation of Win10, as well as disabled "OS upgrade". All this was restore able, so when problem emerged I switched everything back - but had no result on failed updates (malware was up and running).

So anyhow - registry seems to be only thing left to do. Would it be sufficient to delete every entry that has KB2952664 in its name or there is something more?
 
Thing is that I have found all packages that are reported missing in SURT log (all file versions)
Click to expand...

Where did you find them? Can you link them for me?

At first I solved it by removing it from startup (schedule tasks) by deleting entries there. t worked for some time but bugger started to come back using some different scheme, so I changed ownership of files in GWX directory and deleted files there. Again it was good for some time when it started to appear again - with no GWX.exe on system.
Click to expand...

You should never, ever remove any files in the Windows directory like that. This is what creates corruption on a Windows system and lead us to source and replace missing payloads, packages, manifests, etc. If you want to get rid of a file, you need to uninstall the update associated with it. If it's a core Windows file, you have to leave it be.
 
Where did you find these files? On your system, or online?
 
In that case, please run SURT once more so I can see what needs to be done, since I want to see what the fix you attempted changed.

IGJdB0T.png
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)
 
Awesome, let's try this.

IGJdB0T.png
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
 
Good :) Alright, what is KB number of the update that is failing?
 
Actually there are 4 updates failing - I just selected one to get faster result.

They are: KB3060716, KB3071756, KB3101746 and KB3080149
 
Instead of deleting CBS.log, I suggest you to rename it (to CBS_old.log) as it's possible that in the future, you might want to refer to it. If you want to force the creation of a new CBS.log, run a SFC scan, then try to install the update again and upload the two files (WindowsUpdate.log and CBS.log) once for me please since I need both of them to identify the problem.
 
Follow the instructions below please.

rONW46K.png
Uninstall a Windows Update - Command Prompt
Follow the instructions below to uninstall a Windows Update manually via the command prompt.
  • 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 (you can copy/paste it, to paste in the command prompt, right-click inside it and select Paste):
    Code: 
    wusa /uninstall /KB:2922229
  • Let me know the outcome of the command: either it uninstall the update or either it says that the update isn't installed on the system;
 
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