[SOLVED] [Win7SP1 x64] Windows update failed. Manifest file corrupted

Please find the result in SFCFix.txt below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-05-29 19:22:48.191
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\user\Desktop\SFCScript.txt [0]








RegistryScript::
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS. A root key cannot be created under this hive.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-05-29 19:22:48.243
Script hash: XOd9gVNcyQfpEDTnIaprkZw57TqgKfuXNDUc1XoM2ec=
----------------------EOF-----------------------
 
Please do the following.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Thank you and please find the content of Fixlog.txt below:

Fix result of Farbar Recovery Scan Tool (x64) Version: 28-05-2017
Ran by user (30-05-2017 12:03:10) Run:1
Running from C:\Users\user\Desktop
Loaded Profiles: user (Available Profiles: user)
Boot Mode: Normal
==============================================


fixlist content:
*****************
cmd: reg load hklm\components c:\windows\system32\config\components
cmd: reg query HKEY_LOCAL_MACHINE\COMPONENTS


*****************




========= reg load hklm\components c:\windows\system32\config\components =========


操作順利完成。




========= End of CMD: =========




========= reg query HKEY_LOCAL_MACHINE\COMPONENTS =========




HKEY_LOCAL_MACHINE\COMPONENTS
StoreFormatVersion REG_BINARY 30002E0030002E0030002E003600
StoreArchitecture REG_BINARY 09000000
LastScavengeCookie REG_QWORD 0x1d2d70295be933c
LastScavengeFlags REG_DWORD 0x7


HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData
HKEY_LOCAL_MACHINE\COMPONENTS\ccpinterface
HKEY_LOCAL_MACHINE\COMPONENTS\Configuration
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData
HKEY_LOCAL_MACHINE\COMPONENTS\Installers
HKEY_LOCAL_MACHINE\COMPONENTS\ServicingStackVersions


========= End of CMD: =========




==== End of Fixlog 12:03:11 ====
 
Please do the following. I need to verify the logs are clean before we continue again. Try not to get ahead of me as it can cause more issues which makes it harder to fix.

SFC Scan


  1. Click on the Start 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.

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.
 
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.
 
Thank you and please find the CheckSUR.log as attached below:-



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-06-03 02:24


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 1226
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
Linked here is an article which details how to enable or disable verbose Windows Installer logging. http://support.microsoft.com/kb/223300

I want you to:
1) Enable verbose Windows Installer logging (use the Fix-It at the above link)
2) Attempt to install only KB2901983.
3) Disable verbose Windows Installer logging using the matched pair Fix-It from the link I provided.
4) Run collect.exe and copy to Desktop, zip up & upload both %temp%\vslogs.cab & C:\Windows\Logs\CBS folder. See here for details: Instructions to collect .NET Framework 4 and Visual Studio 2010 setup logs - VarunGupta - Site Home - MSDN Blogs

.net issues are sometimes quite difficult to fix. If it's Windows Installer store corruption we don't have a chance. If it's most other things a forced uninstall will do the trick - but we first need to check whether there's anything which could make the situation more complicated or unstable. In such a situation we have to attempt a fix, and it's a bit hit and miss as to whether your error will be fixable or not. Still, we'll hope for the best. With any luck the logfiles will reveal some useful information we can make use of.
 
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