[SOLVED] [Win7SP1] KB3097989 fails multiple times with error: WindowsUpdate_800B0100

B

bobmac1547

Contributor
Joined
Feb 26, 2017
Posts
12
Challenging problem. So I ran SFCFix.exe and SURT. Logs are attached. Any help?

(CBS.zip will follow)
 

Attachments

Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

bobmac1547 said:
(CBS.zip will follow)
Click to expand...

Cannot upload the file; when I drop the SFCFix.txt on SFCFix.exe, here's what I get...

Welcome to SFCFix by niemiro and sysnative.com.
Checking for updates . . .
No new update is available at this time.
Detected logfile supplied as script. Script blocked.
Press any key to exit . . .​

Any suggestions?
 
Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

I tried it and just got the message: The following updates were not installed: Security Update for Windows (KB3097989)
 
Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

Please zip up and attach your c:\windows\logs\cbs\cbs.log

If it is more than ~7MB zipped you will need to upload it to a site such as SendSpace or Dropbox and provde a link in your next reply. Thanks.
 
Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

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
 

Attachments

Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

Here's the contents of SFCFix.txt...

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-02-27 18:50:57.068
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at D:\Ken\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Servicing\Packages

Successfully copied file D:\Ken\AppData\Local\niemiro\Archive\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat.
Successfully copied file D:\Ken\AppData\Local\niemiro\Archive\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum.
Successfully copied file D:\Ken\AppData\Local\niemiro\Archive\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat.
Successfully copied file D:\Ken\AppData\Local\niemiro\Archive\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum.

Successfully restored ownership for C:\Windows\Temp\CheckSur\Servicing\Packages
Successfully restored permissions on C:\Windows\Temp\CheckSur\Servicing\Packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-02-27 18:50:57.518
Script hash: JphJpP9/U6d/Uv0dIDj0NzbdFZqfkMgGCaBk11CNaJE=
----------------------EOF-----------------------
​
​
 
Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

UGH! Same thing: The following updates were not installed: Security Update for Windows (KB3097989)

BTW, I REALLY appreciate your efforts. Let it not go unsaid!
 
Re: KB3097989 fails multiple times with error: WindowsUpdate_800B0100

No problem. Can you please zip up and attach your c:\windows\logs\cbs\cbs.log?

Thank you.
 
Thanks. Please do the following.

Step#1 - ChkDsk Scan
1. Right-click your Start button and select Command Prompt (Admin). Answer Yes to allow if the User Account Control dialog comes up.
2. You should now have a black window open that you can type in to.
3. Please type chkdsk and then press enter.
4. Chkdsk will start to run. Please allow it to finish. You will know it is running when you see text as follows.
Chkdsk.JPG


5. Download ListChkdskResult.exe by SleepyDude and save it on your desktop. If it's already downloaded to your desktop, just skip this step.
6. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.
 
ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 2/28/2017 7:50:05 PM >------
Category: 0
Computer Name: Kenny
Event Code: 26212
Record Number: 6144
Source Name: Chkdsk
Time Written: 03-01-2017 @ 03:49:35
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
384256 file records processed.

File verification completed.
480 large file records processed.

0 bad file records processed.

2 EA records processed.

28 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
437306 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
384256 file SDs/SIDs processed.

Cleaning up 1692 unused index entries from index $SII of file 0x9.
Cleaning up 1692 unused index entries from index $SDH of file 0x9.
Cleaning up 1692 unused security descriptors.
Security descriptor verification completed.
26526 data files processed.

CHKDSK is verifying Usn Journal...
33811808 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

244093951 KB total disk space.
102387868 KB in 120414 files.
78556 KB in 26527 indexes.
0 KB in bad sectors.
492647 KB in use by the system.
65536 KB occupied by the log file.
141134880 KB available on disk.

4096 bytes in each allocation unit.
61023487 total allocation units on disk.
35283720 allocation units available on disk.

-----------------------------------------------------------------------
 
Thanks. Now I need the following logs.

Using the .NET Collect Utility


  1. Download collect.exe and save to your desktop.
  2. Go ahead and run the tool
  3. The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab.
  4. Please zip/attach to this post or if too large, send using a service such as SendSpace.
 
Here You Go: Dropbox - vslogs.zip

And a million thanks for sticking with me on this. You must be as stubborn as I am. I just run out of knowledge and experience. But you are a TERRIFIC resource!!!
 
Yes I would say I'm a little stubborn. :r1:

UnInstall Update with DISM

  1. Download this update and save to your desktop. The file name will be Windows6.1-KB3097989-x64.cab.zip.
  2. Right-click on this file and select Extract All... Keep the defaults and click the Extract button. You can close the folder window that opens.
  3. Right-click your Start button and select Command Prompt (Admin). If a user account control prompt comes up, please allow.
  4. Copy and paste the following command into the command prompt window and press enter.

    dism /online /remove-package /packagepath:%userprofile%\desktop\Windows6.1-KB3097989-x64.cab.zip\Windows6.1-KB3097989-x64.cab
  5. You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation. <---You may not get this line.
    Do you want to restart the computer now (Y/N)? <---You may not get this line.

Go ahead and do so if prompted. Let me know what errors if any come up.
 
OK. Did it, but DISM failed. Here's what I got in the command prompt window...
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489

Processing 1 of 1 -
An error occurred - Package_for_KB3097989 Error: 0x800b0100

Error: 0x800b0100

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
​


And, here is the contents of the dism.log...
2017-03-01 10:51:26, Info DISM PID=9468 Scratch directory set to 'D:\Ken\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2017-03-01 10:51:26, Info DISM PID=9468 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:26, Info DISM DISM Manager: PID=9468 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:26, Info DISM DISM.EXE:
2017-03-01 10:51:26, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2017-03-01 10:51:26, Info DISM DISM.EXE:
2017-03-01 10:51:26, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=8
2017-03-01 10:51:26, Info DISM DISM.EXE: Executing command line: dism /online /remove-package /packagepath:D:\Ken\desktop\Windows6.1-KB3097989-x64.cab\Windows6.1-KB3097989-x64.cab
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2017-03-01 10:51:26, Info DISM DISM Provider Store: PID=9468 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Manager: PID=9468 Successfully loaded the ImageSession at "D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837" - CDISMManager::LoadImageSession
2017-03-01 10:51:27, Info DISM DISM Image Session: PID=6160 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM OS Provider: PID=6160 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM OS Provider: PID=6160 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider OSServices - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Warning DISM DISM Provider Store: PID=6160 Failed to Load the provider: D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Manager: PID=9468 Image session successfully loaded from the temporary location: D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837 - CDISMManager::CreateImageSession
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider OSServices - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2017-03-01 10:51:27, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2017-03-01 10:51:27, Info DISM DISM.EXE: Target image information: OS Version=6.1.7601.17592, Image architecture=amd64
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2017-03-01 10:51:27, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2017-03-01 10:51:27, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2017-03-01 10:51:27, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2017-03-01 10:51:27, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2017-03-01 10:51:27, Info DISM DISM OS Provider: PID=6160 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2017-03-01 10:51:27, Info DISM DISM Driver Manager: PID=6160 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Loading Provider from location D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Connecting to the provider located at D:\Ken\AppData\Local\Temp\1DC3D0D1-538D-4A81-A3F2-15152917A837\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2017-03-01 10:51:27, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2017-03-01 10:51:27, Info DISM DISM Transmog Provider: PID=6160 Current image session is [ONLINE] - CTransmogManager::GetMode
2017-03-01 10:51:27, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2017-03-01 10:51:27, Info DISM DISM Provider Store: PID=6160 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Processing the top level command token(remove-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Encountered the option "packagepath" with value "D:\Ken\desktop\Windows6.1-KB3097989-x64.cab\Windows6.1-KB3097989-x64.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Package Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2017-03-01 10:51:27, Info DISM DISM Package Manager: PID=6160 Initiating Changes on Package with values: 5, 0 - CDISMPackage::Internal_ChangePackageState
2017-03-01 10:51:32, Info DISM DISM Package Manager: PID=6160 Error in operation: (null) (CBS HRESULT=0x800b0100) - CCbsConUIHandler::Error
2017-03-01 10:51:32, Error DISM DISM Package Manager: PID=6160 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800b0100)
2017-03-01 10:51:32, Error DISM DISM Package Manager: PID=6160 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800b0100)
2017-03-01 10:51:32, Info DISM DISM Package Manager: PID=6160 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2017-03-01 10:51:32, Error DISM DISM Package Manager: PID=6160 Failed while processing command remove-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800b0100)
2017-03-01 10:51:32, Info DISM DISM Package Manager: PID=6160 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2017-03-01 10:51:32, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800B0100
2017-03-01 10:51:32, Info DISM DISM Image Session: PID=6160 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Package Manager: PID=6160 Finalizing CBS core. - CDISMPackageManager::Finalize
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=6160 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2017-03-01 10:51:32, Info DISM DISM.EXE:
2017-03-01 10:51:32, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2017-03-01 10:51:32, Info DISM DISM.EXE:
2017-03-01 10:51:32, Info DISM DISM Image Session: PID=9468 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=9468 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=9468 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-03-01 10:51:32, Info DISM DISM Provider Store: PID=9468 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
​
 
Please do the following again. Thanks.

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.
 
The log was only 2K big, so here's the contents...

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-03-01 12:13

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 97
Found 2 errors
Fixed 2 errors
CBS MUM Corrupt Total count: 2
Fixed: CBS MUM Corrupt. Total count: 2
Fixed: CBS Paired File. Total count: 2


​
 
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