[SOLVED] Error 8007371B - W 7 - 64

Clade · Jan 21, 2016

Follow log

[COSFCFix version 2.4.5.0 by niemiro.Start time: 2016-01-21 18:50:22.044
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Clade\Desktop\SFCFixScript.txt [0]

Collect:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 72 datablocks.
Finish time: 2016-01-21 18:51:15.975
----------------------EOF-------------------DE][/CODE]

Clade · Jan 21, 2016

Re: Logfile submission from Clade

[QUOTE = LogBot; 144148] apresentação Logfile do clado. Os arquivos de log estão disponíveis em: https://www.sysnative.com/niemiro/fileDistribution/2016-01/6951.zip [/ QUOTE]

Sorry! But I did not understand about it. . .

zcomputerwiz · Jan 21, 2016

Everything worked, you got it right :)

I had a problem with my first fix script, let's try this:

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

Once SFCFix has completed, run SURT again and attach CheckSUR.log with your reply.

Clade · Jan 21, 2016

Follow log SFCFix:

Code:

[SFCFix version 2.4.5.0 by niemiro.Start time: 2016-01-21 19:14:22.531
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Clade\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_e8823e7081249851.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_e8823e7081249851.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_e8823e7081249851.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 72 datablocks.
Finish time: 2016-01-21 19:14:23.012
Script hash: 0+jZLbIlS+549l0eo9JH87Rq4EErpiB8SO/I6Eet23A=
----------------------EOF-----------------------/CODE]

Clade · Jan 21, 2016

Follow CheckSUR log;

https://www.sendspace.com/file/obusaq

zcomputerwiz · Jan 25, 2016

I'd like to see the side by side branch of the registry.
Follow these instructions to export it:

Export registry as hive

Click on the Start

button and in the search box, type regedit
When you see regedit on the list, right-click on it and select Run as administrator
When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (*.*)
Name this file SideBySide (with no file extension) and save it to your Desktop.
Right click on the SideBySide file and choose Send To -> Compressed (zipped) Folder.
Attach the zip with your reply.

Clade · Jan 25, 2016

Follow log:

https://www.sendspace.com/file/3ug739

zcomputerwiz · Jan 26, 2016

Let's try reinstalling kb3102810.

Install Update with DISM

Download the update MSU here: Download Update for Windows 7 for x64-based Systems (KB3102810) from Official Microsoft Download Center
Copy the MSU file to a convenient location (such as C:\temp).
Click on the Start

button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, type the following commands into it, press enter after each

CD C:\temp

expand {update name}.msu -f:* C:\temp

replace {update name} with the name of the MSU file downloaded in step 1

DISM.exe /Online /Add-Package /PackagePath:C:\temp\{update name}.cab
You should receive the message:

The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now (Y/N)?
Make sure to allow the computer to restart if prompted.

If you receive any other message:
Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
Paste (Ctrl+V) it into your next post please.

Clade · Jan 26, 2016

File name was transferred to Temp folder

Windows6.1-KB3102810-x64

expand {Windows6.1-KB3102810-x64}.msu -f:* C:\temp

Message:

It is not possible to open the input file

zcomputerwiz · Jan 26, 2016

Try it again without the {} braces:

expand Windows6.1-KB3102810-x64.msu -f:* C:\temp

DISM.exe /Online /Add-Package /PackagePath:C:\temp\Windows6.1-KB3102810-x64.cab

Clade · Jan 26, 2016

4 files included in the previous command.

Dism was up 30.3%

Management tool and Deployment Image Servicing
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489

Processing 1 1 - Adding Package_for_KB3102810 31bf3856ad364e35 ~ package ~
MD64 ~~ 6.1.1.2
[================= 30.3%]
Error - Package_for_KB3102810 error: 0x80073712

Error: 14098

The component repository has been corrupted.

DISM log file can be located in C: \ Windows \ Logs \ DISM \ dism.log

Follog log DISM:

Code:

2016-01-26 19:35:04, Info DISM PID=8396 Scratch directory set to 'C:\Users\Clade\AppData\Local\Temp\'. - CDISMManager:

ut_ScratchDir2016-01-26 19:35:04, Info DISM PID=8396 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:04, Info DISM DISM Manager: PID=8396 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:04, Info DISM DISM.EXE:
2016-01-26 19:35:04, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2016-01-26 19:35:04, Info DISM DISM.EXE:
2016-01-26 19:35:04, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2016-01-26 19:35:04, Info DISM DISM.EXE: Executing command line: DISM.exe /Online /Add-Package /PackagePath:C:\temp\Windows6.1-KB3102810-x64.cab
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2016-01-26 19:35:04, Info DISM DISM Provider Store: PID=8396 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Manager: PID=8396 Successfully loaded the ImageSession at "C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189" - CDISMManager::LoadImageSession
2016-01-26 19:35:14, Info DISM DISM Image Session: PID=5132 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:14, Info DISM DISM OS Provider: PID=5132 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM OS Provider: PID=5132 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Getting Provider OSServices - CDISMProviderStore::GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Warning DISM DISM Provider Store: PID=5132 Failed to Load the provider: C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Manager: PID=8396 Image session successfully loaded from the temporary location: C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189 - CDISMManager::CreateImageSession
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Getting Provider OSServices - CDISMProviderStore::GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2016-01-26 19:35:14, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_SUCCESS
2016-01-26 19:35:14, Info DISM DISM.EXE: Target image information: OS Version=6.1.7601.18766, Image architecture=amd64
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:14, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:15, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:15, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:15, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2016-01-26 19:35:15, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_SUCCESS
2016-01-26 19:35:15, Info DISM DISM Package Manager: PID=5132 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2016-01-26 19:35:15, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2016-01-26 19:35:15, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_SUCCESS
2016-01-26 19:35:15, Info DISM DISM Package Manager: PID=5132 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2016-01-26 19:35:18, Info DISM DISM Package Manager: PID=5132 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2016-01-26 19:35:18, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\pkgmgr.exe" : got STATUS_SUCCESS
2016-01-26 19:35:18, Info DISM DISM OS Provider: PID=5132 Successfully loaded the hive. - CDISMOSServiceManager:

etermineBootDrive
2016-01-26 19:35:18, Info DISM DISM Driver Manager: PID=5132 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Loading Provider from location C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Connecting to the provider located at C:\Users\Clade\AppData\Local\Temp\6EB438CC-6771-4851-84C9-46CC91FB4189\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2016-01-26 19:35:18, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2016-01-26 19:35:18, Info DISM DISM Transmog Provider: PID=5132 Current image session is [ONLINE] - CTransmogManager::GetMode
2016-01-26 19:35:18, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2016-01-26 19:35:18, Info DISM DISM Provider Store: PID=5132 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-26 19:35:18, Info DISM DISM Package Manager: PID=5132 Processing the top level command token(add-package). - CPackageManagerCLIHandler:

rivate_ValidateCmdLine
2016-01-26 19:35:18, Info DISM DISM Package Manager: PID=5132 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2016-01-26 19:35:18, Info DISM DISM Package Manager: PID=5132 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2016-01-26 19:35:18, Info DISM DISM Package Manager: PID=5132 Encountered the option "packagepath" with value "C:\temp\Windows6.1-KB3102810-x64.cab" - CPackageManagerCLIHandler:

rivate_GetPackagesFromCommandLine
2016-01-26 19:35:19, Info DISM DISM Package Manager: PID=5132 Package Package_for_KB3102810~31bf3856ad364e35~amd64~~6.1.1.2 with CBS state 0(CbsInstallStateAbsent) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) - CDISMPackage::LogInstallStateMapping
2016-01-26 19:35:19, Info DISM DISM Package Manager: PID=5132 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
2016-01-26 19:36:26, Info DISM DISM Package Manager: PID=5132 Error in operation: (null) (CBS HRESULT=0x80073712) - CCbsConUIHandler::Error
2016-01-26 19:36:26, Error DISM DISM Package Manager: PID=5132 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
2016-01-26 19:36:26, Error DISM DISM Package Manager: PID=5132 Failed processing package changes - CDISMPackageManager:

rocessChanges(hr:0x80073712)
2016-01-26 19:36:26, Info DISM DISM Package Manager: PID=5132 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-01-26 19:36:26, Error DISM DISM Package Manager: PID=5132 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
2016-01-26 19:36:26, Info DISM DISM Package Manager: PID=5132 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-01-26 19:36:26, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712
2016-01-26 19:36:26, Info DISM DISM Image Session: PID=5132 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2016-01-26 19:36:26, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:26, Info DISM DISM Package Manager: PID=5132 Finalizing CBS core. - CDISMPackageManager::Finalize
2016-01-26 19:36:26, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:30, Info DISM DISM Provider Store: PID=5132 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:31, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2016-01-26 19:36:31, Info DISM DISM.EXE:
2016-01-26 19:36:31, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2016-01-26 19:36:31, Info DISM DISM.EXE:
2016-01-26 19:36:31, Info DISM DISM Image Session: PID=8396 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2016-01-26 19:36:31, Info DISM DISM Provider Store: PID=8396 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-26 19:36:31, Info DISM DISM Provider Store: PID=8396 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-01-26 19:36:31, Info DISM DISM Provider Store: PID=8396 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Code:

zcomputerwiz · Jan 27, 2016

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

Once SFCFix has completed, please run SURT again and attach CheckSUR.log with your reply.

Clade · Jan 27, 2016

Code:

 SFCFix versão 2.4.8.0 por niemiro.
Hora de início: 2016/01/27 14: 37: 02,027
Microsoft Windows 7 Service Pack 1 - amd64
Usando .zip arquivo de script em C: \ Users \ Clade \ Desktop \ SFCFix.zip [0]








RegistryScript ::
Levou com sucesso propriedade e as permissões para chaves do Registro HKEY_LOCAL_MACHINE \ Components \ \ CanonicalData implantações.
Levou com sucesso propriedade e as permissões para a chave de registro HKEY_LOCAL_MACHINE \ Components \ DerivedData \ Components.


Falha ao importar chave do Registro com código de erro 0x773C2F6D.
Falha ao importar chave do Registro com código de erro 0x773C2F6D.


Falha ao abrir chave do Registro com código de erro ERROR_FILE_NOT_FOUND.
Restaurado com sucesso propriedade e as permissões para chaves do Registro HKEY_LOCAL_MACHINE \ Components \ \ CanonicalData implantações.
Falha ao abrir chave do Registro com código de erro ERROR_FILE_NOT_FOUND.
Restaurado com sucesso propriedade e as permissões para a chave de registro HKEY_LOCAL_MACHINE \ Components \ DerivedData \ Components.
RegistryScript :: directiva não foi concluída com êxito.








Falha ao processar todas as directivas com sucesso.
SFCFix versão 2.4.8.0 por niemiro foi concluída.
Atualmente armazenar 75 blocos de dados.
Tempo de finalização: 2016/01/27 14: 37: 05,250
Hash de Script: pRw8zLJMqR + f6uxNSuOZ0AoC92O6CZqlkorP8OFtBt0 =
---------------------- ----------------------- EOF [/ code]



Follow log Checksur:

https://www.sendspace.com/file/5i3paz

zcomputerwiz · Jan 27, 2016

Let's try that again.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

Clade · Jan 27, 2016

follow log:

Code:

SFCFix version 2.4.9.0 by niemiro.Start time: 2016-01-28 00:52:00.196
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Clade\Desktop\SFCFix.zip [0]








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\DerivedData\Components.


Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\83f62977fbe..098bac30654_31bf3856ad364e35_7.6.7601.19046_b721cb40f3c902b9 with error code 0x773E2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_83f62977fbe800db22f67098bac30654_31bf3856ad364e35_7.6.7601.19046_none_b721cb40f3c902b9 with error code 0x773E2F6D.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\83f62977fbe..098bac30654_31bf3856ad364e35_7.6.7601.19046_b721cb40f3c902b9 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_83f62977fbe800db22f67098bac30654_31bf3856ad364e35_7.6.7601.19046_none_b721cb40f3c902b9 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 2.4.9.0 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2016-01-28 00:52:02.270
Script hash: IgrHKbgy/CS8UzMlEzUxtv+zFqtB1ne374zqrgwYbiM=
----------------------EOF-----------------------

I do not know if there is any correlation, but Wifi taking several minutes to connect after boot and the audio does not work, "No audio output device is installed."

Clade · Jan 28, 2016

I do not know if there is any correlation, but Wifi taking several minutes to connect after boot and the audio does not work, "No audio output device is installed."[/QUOTE]

Resolved

zcomputerwiz · Jan 28, 2016

I'll try making the replacement manually on my end.

Please turn off Windows Update:

Turn Off Windows Update

Open Windows Update by clicking the Start button.
In the search box, type Windows Update, and then, in the list of results, click Windows Update.
In the left pane, click Change settings.
Under Important updates, choose Never Check for Updates.
Under Recommended updates, select the Give me recommended updates the same way I receive important updates check box.
Click OK.

Then run this script to upload the Components hive again:

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.

[sfcfixdownload]Download SFCFix[/sfcfixdownload] (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u...eric/Collect/COMPONENTS/SFCFixScript.txt?dl=1

Clade · Jan 28, 2016

The first phase of the program failure when requesting the update SFCfix. Clicking on the sequence has the log:

Code:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-28 13:26:10.569
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Clade\Desktop\SFCFixScript.txt [0]








Collect::
Failed to generate a complete zip file. Upload aborted.
Collect:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2016-01-28 13:26:19.017
Script hash: duc6swbHUuscraK6n0RQWoNjUFLL0qXEg6xxnCShc8o=
----------------------EOF-----------------------

zcomputerwiz · Jan 28, 2016

Please reboot and try the collection script again.

Clade · Jan 28, 2016

The first phase of the program failure when requesting the update SFCfix. Clicking on the sequence has the log:

Code:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-28 13:26:10.569
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Clade\Desktop\SFCFixScript.txt [0]








Collect::
Failed to generate a complete zip file. Upload aborted.
Collect:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2016-01-28 13:26:19.017
Script hash: duc6swbHUuscraK6n0RQWoNjUFLL0qXEg6xxnCShc8o=
----------------------EOF-----------------------

[SOLVED] Error 8007371B - W 7 - 64

Well-known member

Well-known member

Windows Update Expert

Well-known member

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member