[SOLVED] How Can I Get Rid Of The KB3035583 Update (GWX) When There Is An Error: 14098??

D

DKW3

Contributor
Joined
Feb 8, 2015
Posts
129
Location
San Diego, CA
The KB3035583 GWX update has really messed-up my windows 7, after it sneakily got reinstalled by my having checked that "Give me recommended updates the same way..." option.

I learned this the hard way after I manually deleted what I thought were leftover GWX files; so now I have component store corruption that won't allow me to uninstall it in Windows Updates, via the basic "KB" removal command, or via DISM in CMD, without getting the SAME "Error: 14098".

The latest installed version of KB 3022345 couldn't get rid it either, due to the corruption caused by the missing "Manifest"; so that update will be the next to go; but for now, the corrupted remnants of KB3035583 is the priority.

"The Update readiness tool" is no good for this either, since it hasn't been updated since late 2014 in order to deal with GWX, clearly something that Microsoft doesn't mind.

I used both SFC /Scannow and SFC.fix, both of which tried to repair GWX, the exact opposite of what I want, unless it could've restored the elements necessary to do a complete uninstalling.

After just ditching my online subscription of Office 2013, I don't dare reinstall my office 2010 until this matter is resolved, don't want to risk any hiccups that will force another cumbersome re-install.

If I had the know-how to remove the remnants manually, I would; but doing that with side-by-side components when you don't have clue as to what ELSE you may be deleting, is VERY risky business.


Any help to get GWX out of my windows asap will be appreciated, or it's using a Macrium Windows image saved 2 weeks back as a last resort; but with quite a few updates and new program installs since, I would really like to avoid that, if possible. See attached CBS & SFC.fix logs for details-Thanks.
 

Attachments

Hi and welcome to Sysnative.

What problems did KB3035583 cause?

This may take a couple rounds but let's fix your corruption.

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 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Items for your next post
1. SFCFix.txt
2. CBS.txt
 
Thanks Brian,
here are the contents:
---------------------------------------

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-31 12:50:34.032
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Derwin's Work\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4bf5400abf9d60b7\mfc90.dll
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.4148_none_51ca66a2bbe76806\ATL90.dll

Successfully copied file C:\Users\Derwin's Work\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4bf5400abf9d60b7\mfc90.dll to C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4bf5400abf9d60b7\mfc90.dll.
WARNING: File C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Derwin's Work\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL to C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL.
Successfully copied file C:\Users\Derwin's Work\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.4148_none_51ca66a2bbe76806\ATL90.dll to C:\Windows\winsxs\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.4148_none_51ca66a2bbe76806\ATL90.dll.

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4bf5400abf9d60b7\mfc90.dll
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4bf5400abf9d60b7\mfc90.dll
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9\MFC90CHT.DLL
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.4148_none_51ca66a2bbe76806\ATL90.dll
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.4148_none_51ca66a2bbe76806\ATL90.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2015-05-31 12:50:35.160
Script hash: Wp6Hun/0Cco1r5CDR7lgbgHRsYPpnfUBMvJjqHWgY7U=
----------------------EOF-----------------------
 
Done.

I had some problems using Firefox (a few crashes), and for some reason it corrupted WUSA, had to reset the the components with the "Tweaking.com" fix. Now, I don't know what version of KB3035583 was unknowingly installed ( Microsoft re-re-re-issues controversial Windows 10 patch KB 3035583 | InfoWorld), but hopefully, you can see within the log.

FYI, I did go ahead and re-install Office 2010 after using a VBS scrub, since I realy rely on Word & Oultook use, daily. Thanks again, and I hope we can wrap this issue up.
 

Attachments

Thanks for the info. Another round of corruption fixes are needed. Hopefully the last one. 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 - SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Items for your next post
1. SFCFix.txt
2. CBS.txt
 
Actually things look much better. We don't need to worry about the Telemetry items. It's a known issue and Microsoft is working on a fix. It doesn't affect the Windows Updates or Servicing. More info on that is below.

https://support.microsoft.com/en-us/kb/3022345

quote_icon.png
Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.
Click to expand...


So, now let's see if you can go to Add/Remove programs and remove the update KB3035583.
 
If you are unable to remove the update, please do the following.

Step#1 - 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.
 
Hi I couldn't find "GWX" within the text, but this was via doing the suggested "system update readiness tool", which didn't work when I used it myself, before I posted my issue. Please let me know what the attached CBS and Deep Clean files mean, particularly if it means GOOD NEWS. Thanks.

-DKW3
 

Attachments

I see one issue in the log but I'd really like you to try the System Update Readiness tool following my instructions and let me know exactly what issues or errors you get. I'd like to look at that log.
Code: 
2015-05-31 22:59:47, Error                 CBS    Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]

Step#1 - 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.
 
Okay will do, sorry about that.

By the way, both times when I've posted about an issue, and tried to use the following suggested command inputting my user name within the %userprofile%, it simply doesn't work (copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt).

I'd like to know exactly what I'm doing wrong, there; are you supposed to input your specific computer name for the %windir% dialog, as well?

-DKW3
 
%userprofile% and %windir% are system variables so you wouldn't change anything.

For example if I say to copy and paste the following into a command-prompt, you would do just that. Copy the following line and then right-click and paste it into the command prompt window. Make sense?
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
 
Yes. But here is what happens when I do that in command prompt, running as an Admin: (I changed my actual name)

"C:\Users\Dwayne's Work>copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.
txt
The syntax of the command is incorrect."

Okay, the system readiness tool has just finished, I've attached the file from where you suggested.

-DKW3



View attachment CheckSUR.zip
 
I just did that on HERE, not in the command. Let me know if you find that one issue again in the log, and what can be done about it; It will be nice to have a 100% clean, working Windows, again-thank you.
 
Some things to fix. Please do the following.

Step#1 - Fix Corrupt/Missing 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. We will ignore the packages folder in this instance.
  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.log
 

Attachments

5 corruptions were fixed. Only 12 left. We'll take a look at your command issue after we fix the corruptions.

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. Re-run this.
2. 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

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