Windows 8.1 component store got corrupt and can't start 32bit applications

I don't know whether installation of KB4016754 was successful, but I successfully removed it
 
FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB4016754 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Oops sorry. The attachment is correct so run SFCFix.exe
 
Restart the computer.
Check Windows Update again and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
the update was successful but sfc scannow still cannot restore some files
 

Attachments

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

It looks like SFC didn't find any issues this time.
Any remaining issues ?
 
this is a new cbs file just in case there is something wrong with the old one
 

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