Windows 10 updating issue. - (KB3140741) - Error 0x800736b3

A

AMC

Member
Joined
Jun 1, 2016
Posts
16
Windows updates have been failing for a little while now, maybe 2 or 3 months(See figure.1), but I only recently started trying to fix the issue. Note that this installation is an upgrade from 8.1 to 10 as of ~8 months ago. Also No system restore point was created, but I have created one now today. I'd like to avoid having to do a clean install.

Things I've tried:
  1. Checking for virus'. All seems to be clean as usual.
  2. I tried switching to diagnostic startup, but msconfig would not allow it.(See Figure.2)
  3. I then instead turned on Safe Boot minimal, as well as network after. After booting into Safe Boot I proceeded to 'Action Center' -> 'All Settings' -> 'Update & security'. Upon clicking Update & security the window would close itself. After booting up normally things like the search box, networking, and audio were no longer working. I re-enabled there services, not sure why that happened.
  4. I then tried running system file checker(sfc /scannow) from an elevated command line. It would not run because of a service that was disable, but after fixing that it ran but was unable to fix. See Figure.3
  5. I tried running DISM to fix sfc (dism /online /cleanup-image /restorehealth) and received an error. See Figure.4
  6. I ran SFCfix.exe and it was unable to fix the problem. See figure.5

Figure.1:
Figure.2:
282600028f8198b3b6664f8ce2e6a7b1.gif

Figure.3:
Figure.4:
Figure.5:
Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2016-06-01 17:24:19.333
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component wiaky002.inf.Resources and file kywuds10.dll.mui. File is reported as corrupt by SFC.
CORRUPT: kywuds10.dll.mui of component wiaky002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcpst.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcpst.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcoin.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcoin.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file wiaxx002.inf_loc. File is reported as corrupt by SFC.
CORRUPT: wiaxx002.inf_loc of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcpl.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcpl.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWCtmg2.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWCtmg2.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPusd.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPusd.dll.mui of component wiaxx002.inf.Resources.








SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     7
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-06-01 17:38:29.357
----------------------EOF-----------------------
 
I was unable to finish the thread because I needed to restart, and now most services became disabled again for no apparent reason. I am currently typing from another device this time. Also how can I edit the orriginal post?
 
Hi AMC ... and welcome to the forums ...

Sounds like Windows 10 is pretty tangled up. You've already tried malware scans, very good. Another item I like to get out of the way before engaging in trick software puzzles is a run of diagnostics on the hardware. That way no time is lost unnecessarily chasing hardware issues with software fixes (doesn't work). If your system has diagnostics built-in - run those. Otherwise use bootable utility CDs to test the memory (MemTest86+ is good) and the hard drives (diagnostics from the hard drive manufacturer's support site are best) ... MemTest86+ and some hard drive diagnostics can be found on the free bootable utility CD called "UBCD". Instructions on how to download and create it are on their website
Ultimate Boot CD - Overview

Should the hardware test OK, it seems your best two choices are:

1) [the longer road to a repair] Post this same question in our Windows Updates forum here at SysNative, where techs with special training in Windows Updates and system image corruption can give you help customized to your exact troubles. The SFCfix app is best used under their care and customization. Here's a link to the posting instructions for the Windows Update forum:
https://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html

2) [the quick-fix lottery chance] Try an in-place repair reinstall, which keeps your personal data and your installed programs intact. There are three or four ways to perform it .... a few of our visitors here at SysNative have had good luck with the online method, where you simply visit the Microsoft site and "upgrade" to Windows 10 on top of itself. Here's a link to a tutorial on in-place repair reinstalls for Windows 10:
Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

Hope it turns out well either way!


[late edit: just saw your second post: it is possible to edit a post up to fifteen minutes after it has been posted (the "Edit" button will still work). After fifteen minutes, just add an update with an additional post. I believe the restrictions are built-into the software used to create our forums.]
 
Updated first post.

Windows updates have been failing for a little while now, maybe 2 or 3 months(See figure.1), but I only recently started trying to fix the issue. Note that this installation is an upgrade from 8.1 to 10 as of ~8 months ago. Also No system restore point was created, but I have created one now today. I'd like to avoid having to do a clean install.

Things I've tried:
  1. Checking for virus'. All seems to be clean as usual.
  2. I tried switching to diagnostic startup, but msconfig would not allow it.(See Figure.2)
  3. I then instead turned on Safe Boot minimal, as well as network after. After booting into Safe Boot I proceeded to 'Action Center' -> 'All Settings' -> 'Update & security'. Upon clicking Update & security the window would close itself. After booting up normally things like the search box, networking, and audio were no longer working. I re-enabled there services, not sure why that happened.
  4. I then tried running system file checker(sfc /scannow) from an elevated command line. It would not run because of a service that was disable, but after fixing that it ran but was unable to fix. See Figure.3
  5. I tried running DISM to fix sfc (dism /online /cleanup-image /restorehealth) and received an error. See Figure.4
  6. At this point the search bar once again stopped working. See Figure.5
  7. I ran SFCfix.exe and it was unable to fix the problem. See figure.6
  8. I also purged the download cache which was successful but had no effect on the problem.
Note, ran dism and sfc again to capture figures for this post.

Figure.1:
Code: 
Update for Windows 10 Version 1511 for x64-based Systems (KB3140741) - Error 0x800736b3
b1366c8135186c00179c82bb8f97eee9.png

Figure.2:
282600028f8198b3b6664f8ce2e6a7b1.gif

Figure.3:
f1b7ba75dfcc978ca2ed48eb7263a98f.png

Figure.4:
e7e53a516178166ad73f2a50bf94848e.png

Code: 
2016-06-01 18:42:48, Info                  DISM   PID=5720 TID=6548 Scratch directory set to 'C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2016-06-01 18:42:48, Info                  DISM   PID=5720 TID=6548 DismCore.dll version: 10.0.10586.0 - CDISMManager::FinalConstruct
2016-06-01 18:42:48, Info                  DISM   PID=5720 TID=6548 Successfully loaded the ImageSession at "C:\WINDOWS\System32\Dism" - CDISMManager::LoadLocalImageSession
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: 
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: 
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=8
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10586.0
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: Executing command line: dism  /online /cleanup-image /restorehealth
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Loading Provider from location C:\WINDOWS\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Connecting to the provider located at C:\WINDOWS\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 physical location path: C:\ - CDISMManager::CreateImageSession
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Event name for current DISM session is Global\{9A6B44A2-E346-4F93-8F30-F9CD1529F1B6} - CDISMManager::CheckSessionAndLock
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Create session event 0x164 for current DISM session and event name is Global\{9A6B44A2-E346-4F93-8F30-F9CD1529F1B6}  - CDISMManager::CheckSessionAndLock
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Successfully loaded the ImageSession at "C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391" - CDISMManager::LoadRemoteImageSession
2016-06-01 18:42:48, Info                  DISM   DISM Image Session: PID=5636 TID=4388 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM OS Provider: PID=5636 TID=4388 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM OS Provider: PID=5636 TID=4388 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM OS Provider: PID=5636 TID=4388 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2016-06-01 18:42:48, Warning               DISM   DISM OS Provider: PID=5636 TID=4388 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Warning               DISM   DISM Provider Store: PID=5636 TID=4388 Failed to Load the provider: C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Manager: PID=5720 TID=6548 Image session successfully loaded from the temporary location: C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391 - CDISMManager::CreateImageSession
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Getting Provider OSServices - CDISMProviderStore::GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.10586.0, Image architecture=amd64
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2016-06-01 18:42:48, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2016-06-01 18:42:48, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\IBSProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:48, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM OS Provider: PID=5636 TID=4388 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2016-06-01 18:42:49, Info                  DISM   DISM Driver Manager: PID=5636 TID=4388 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\Wow64provider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Warning               DISM   DISM Provider Store: PID=5636 TID=4388 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
2016-06-01 18:42:49, Warning               DISM   DISM Provider Store: PID=5636 TID=4388 Failed to Load the provider: C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\EmbeddedProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Warning               DISM   DISM Provider Store: PID=5636 TID=4388 Failed to Load the provider: C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\AppxProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\ProvProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\AssocProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\GenericProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\OfflineSetupProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Loading Provider from location C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Connecting to the provider located at C:\Users\[USERNAME-REMOVED]\AppData\Local\Temp\A7D4E474-72C9-4B36-8B0C-3EF060AEF391\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2016-06-01 18:42:49, Info                  DISM   DISM Transmog Provider: PID=5636 TID=4388 Current image session is [ONLINE] - CTransmogManager::GetMode
2016-06-01 18:42:49, Info                  DISM   DISM Transmog Provider: PID=5636 TID=4388 Audit Mode: [No] - CTransmogManager::Initialize
2016-06-01 18:42:49, Info                  DISM   DISM Transmog Provider: PID=5636 TID=4388 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2016-06-01 18:42:49, Info                  DISM   DISM Transmog Provider: PID=5636 TID=4388 Product Type: [WinNT] - CTransmogManager::Initialize
2016-06-01 18:42:49, Info                  DISM   DISM Transmog Provider: PID=5636 TID=4388 Product Type ServerNT : [No] - CTransmogManager::Initialize
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2016-06-01 18:42:49, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-06-01 18:42:49, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2016-06-01 18:42:49, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2016-06-01 18:42:49, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2016-06-01 18:42:49, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize
2016-06-01 18:45:24, Info                  DISM   DISM Package Manager: PID=5636 TID=4396  Error in operation: (null) (CBS HRESULT=0x80070246) - CCbsConUIHandler::Error
2016-06-01 18:45:24, Error                 DISM   DISM Package Manager: PID=5636 TID=4388 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070246)
2016-06-01 18:45:24, Error                 DISM   DISM Package Manager: PID=5636 TID=4388 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070246)
2016-06-01 18:45:24, Error                 DISM   DISM Package Manager: PID=5636 TID=4388 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070246)
2016-06-01 18:45:24, Error                 DISM   DISM Package Manager: PID=5636 TID=4388 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070246)
2016-06-01 18:45:24, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-06-01 18:45:24, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070246
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Package Manager: PID=5636 TID=4388 Finalizing CBS core. - CDISMPackageManager::Finalize
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5636 TID=4388 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Manager: PID=5720 TID=6548 Closing session event handle 0x164 - CDISMManager::CloseImageSession
2016-06-01 18:45:24, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-06-01 18:45:24, Info                  DISM   DISM.EXE: 
2016-06-01 18:45:24, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-06-01 18:45:24, Info                  DISM   DISM.EXE: 
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-06-01 18:45:24, Info                  DISM   DISM Provider Store: PID=5720 TID=6548 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
Figure.5:
[windows key] + --> Typed in a search. No keys or mouse movements after during the duration of this gif.
b603ead8b225213997e6f988e45b3a26.gif

Figure.6:
Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2016-06-01 17:24:19.333
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component wiaky002.inf.Resources and file kywuds10.dll.mui. File is reported as corrupt by SFC.
CORRUPT: kywuds10.dll.mui of component wiaky002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcpst.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcpst.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcoin.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcoin.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file wiaxx002.inf_loc. File is reported as corrupt by SFC.
CORRUPT: wiaxx002.inf_loc of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPcpl.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPcpl.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWCtmg2.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWCtmg2.dll.mui of component wiaxx002.inf.Resources.


WARNING: Failed to get store name from identity name with return code 2 for component wiaxx002.inf.Resources and file xrWPusd.dll.mui. File is reported as corrupt by SFC.
CORRUPT: xrWPusd.dll.mui of component wiaxx002.inf.Resources.








SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     7
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-06-01 17:38:29.357
----------------------EOF-----------------------
 
Thanks for updating your post --- makes the details pretty clear. Funny I mentioned about editing ... I just noticed a type in my last post ("trick software puzzles" should have read "tricky software puzzles" ...

If you have time, let us know if you decide to post in the Windows Update forum, or if you decide on the in-place install (or want to try any other of several options) here in this forum ...

Thanks!
 
OldGrayGary said:
Thanks for updating your post --- makes the details pretty clear. Funny I mentioned about editing ... I just noticed a type in my last post ("trick software puzzles" should have read "tricky software puzzles" ...

If you have time, let us know if you decide to post in the Windows Update forum, or if you decide on the in-place install (or want to try any other of several options) here in this forum ...

Thanks!
Click to expand...

Still working on the Ultimate boot cd option... Note I do not have a disk drive and am trying via a live USB. I tried several different downloads from the link and burned to a USB but it fails to boot from it each time, as well as from my laptop. Other live usb media that I have on hand and have used in the past all work fine.
 
Hi again

CD
I generally use a CD (since it's just so darn easy). If you have a friend who can lend you an external, that would do.

USB
The instructions on creating a bootable floppy on the UBCD website are a bit dated. I think you'll have a much easier time using a tool called "Rufus" to create a bootable USB from the UBCD iso file.

Rufus
Here's are two popular tutorials on how to create bootable USB drives with Rufus:
How to Use Rufus (with Pictures) - wikiHow
How to use Rufus to create a bootable USB drive to install (almost) any OS - TechRepublic

Let us know if you have any other questions.
 
OldGrayGary said:
Hi again

CD
I generally use a CD (since it's just so darn easy). If you have a friend who can lend you an external, that would do.

USB
The instructions on creating a bootable floppy on the UBCD website are a bit dated. I think you'll have a much easier time using a tool called "Rufus" to create a bootable USB from the UBCD iso file.

Rufus
Here's are two popular tutorials on how to create bootable USB drives with Rufus:
How to Use Rufus (with Pictures) - wikiHow
How to use Rufus to create a bootable USB drive to install (almost) any OS - TechRepublic

Let us know if you have any other questions.
Click to expand...

Still won't boot into it. I have tried 3 different mirrors of each the CD version and usb version including the torrent one and checked the hash of the files each time and all were fine. I also tried making the media in three different USB media tools, including RUFUS. I made sure the USB drive was set to first on the boot list in BIOS as well. It hits the boot screen twice before just going to Windows meaning nothing is happening in UBCD...
 
Very sorry that the bootable USB method is proving so troublesome. One last try, I suppose, might be to try MemTest86+'s own "Auto-installer for USB key"
Memtest86+ - Advanced Memory Diagnostic Tool

If that doesn't work, ask around to see if anyone you know has an external DVD/CD drive you could borrow for a day. The hard drive diagnostics are usually available from the manufacturer support sites as I mentioned earlier.... The most common tools are DataLifeGuard for Western Digital and SeaTools for Seagate/Maxtor. Hitachi/IBM drives have a test called "Drive Fitness Test"....

If the diagnostics prove to troublesome to run beforehand, you do have the option to skip them & take your chances with the in-place upgrade or to visit our Windows Update forum. I think it's handy experience, if nothing else, to know what diagnostics work for your system: it can give you a bit more peace of mind that the hardware is working properly.

If a setting has changed in your PC's BIOS - that could also cause the problem with booting from a USB. You could check in the BIOS just to see if anything looks different. For many UEFI based motherboards, "Secure Boot" or "Safe Boot" has to be disabled, and sometimes a "Legacy Bios" option needs to be enabled, to boot from a USB or CD. Security minded folks generally like to re-enable "Secure Boot" and such after the diagnostics have run.

Let us know if you have any questions.
 
You know, I was thinking of another "just to see" quick fix try:
See if installing KB3140741 manually works. Using Internet Explorer, visit the link below, and download & install it from the Microsoft Update Catalog:
Microsoft Update Catalog

Probably won't work, but won't hurt to try.
 
OldGrayGary said:
Very sorry that the bootable USB method is proving so troublesome. One last try, I suppose, might be to try MemTest86+'s own "Auto-installer for USB key"
Memtest86+ - Advanced Memory Diagnostic Tool

If that doesn't work, ask around to see if anyone you know has an external DVD/CD drive you could borrow for a day. The hard drive diagnostics are usually available from the manufacturer support sites as I mentioned earlier.... The most common tools are DataLifeGuard for Western Digital and SeaTools for Seagate/Maxtor. Hitachi/IBM drives have a test called "Drive Fitness Test"....

If the diagnostics prove to troublesome to run beforehand, you do have the option to skip them & take your chances with the in-place upgrade or to visit our Windows Update forum. I think it's handy experience, if nothing else, to know what diagnostics work for your system: it can give you a bit more peace of mind that the hardware is working properly.

If a setting has changed in your PC's BIOS - that could also cause the problem with booting from a USB. You could check in the BIOS just to see if anything looks different. For many UEFI based motherboards, "Secure Boot" or "Safe Boot" has to be disabled, and sometimes a "Legacy Bios" option needs to be enabled, to boot from a USB or CD. Security minded folks generally like to re-enable "Secure Boot" and such after the diagnostics have run.

Let us know if you have any questions.
Click to expand...

I had already thought of the secure boot option immediately when I was doing it, what turned out to be the problem was booting in UEFI vs Legacy. Been running memtest86 via UBCD for about 9 and a half hours now with over 65,000 errors, that can't be right, right? My computer never crashes nor have I realized any data loss.
 

Attachments

  • 0602161219.jpg
    0602161219.jpg
    206.5 KB · Views: 1
Hmmm .... somehow you ended up with MemTest86 version 4.3.1 instead of MemTest86+ version 5.01. See if you can try again with MemTest86+ version 5.01. The "plus sign" indicates the newer program, and it's versions are different from the older program.

I'm also curious how things go if you try a manual install of the Cumulative Update using Internet Explorer, and downloading from the Windows Update Calalog (you should be able to go directly there from the link in my post #10 in this thread).

I'll stay tuned....
 
OldGrayGary said:
Hmmm .... somehow you ended up with MemTest86 version 4.3.1 instead of MemTest86+ version 5.01. See if you can try again with MemTest86+ version 5.01. The "plus sign" indicates the newer program, and it's versions are different from the older program.

I'm also curious how things go if you try a manual install of the Cumulative Update using Internet Explorer, and downloading from the Windows Update Calalog (you should be able to go directly there from the link in my post #10 in this thread).

I'll stay tuned....
Click to expand...

Going to be away from that machine for a few days, but I will try all of that when I get back. The fact that I can't use search definitely pises more of an annoyance when doing these things. I did see the memtest86+ option but I didn't know which to run. If that still returns failure I'll have to test each RAM stick. I read heat could be a problem, although my temps are all around 30°C
 
The temperature reading of 30 degrees Celsius isn't bad - especially if that was the temperature shown during the testing (which is fairly intensive). Hope things test well on the second try. No rush!
 
OldGrayGary said:
The temperature reading of 30 degrees Celsius isn't bad - especially if that was the temperature shown during the testing (which is fairly intensive). Hope things test well on the second try. No rush!
Click to expand...

No it was around 33, and that was after rebooting. I have now redone the test with memtest86+ and still received many errors.

1ad70f3d96ec57d57abab13884eff6c9.jpg
 
The search bar seems to be working now. No changes were made to make this happen. Pretty odd.
 
About MemTest86+ errors
It's possible that MemTest86+ has trouble testing on systems with certain motherboard/UEFI versions. See if you limit things to use just one processor, and run MemTest86+ with just the single cpu setting. See if the memory errors disappear. I haven't had this happen to any of the machines here in my work (or home, for that matter) ... but I have heard a few mentions here and there.

Search bar
I wonder - if you go into Windows Update > Advanced Options > View your update history ... if anything has managed to successfully install recently.
 
***UPDATE***
I did a little research, and it looks like only MemTest86 version 6.1 has been updated to work accurately with the most recent hardware/BIOS/UEFI configurations.


Sorry that I hadn't seen this before. So = try the memory tests again, using MemTest86 version 6.1 (or newer, if an update happens to show up in the meantime).


Here's a link to that info, from a tech replying to a system with memory test errors similar to yours:
memtest86 and memtest86+ discrepancies




Looks like I'll be updating my toolkit.
 
OldGrayGary said:
***UPDATE***
I did a little research, and it looks like only MemTest86 version 6.1 has been updated to work accurately with the most recent hardware/BIOS/UEFI configurations.


Sorry that I hadn't seen this before. So = try the memory tests again, using MemTest86 version 6.1 (or newer, if an update happens to show up in the meantime).


Here's a link to that info, from a tech replying to a system with memory test errors similar to yours:
memtest86 and memtest86+ discrepancies




Looks like I'll be updating my toolkit.
Click to expand...

I checked each ram stick and various slots and it seems just one ram stick is getting trouble, I'll try again with the newer version though.

EDIT: Using one working ram stick and going to setting to go to update, freezes that window upon clicking "Update and Security"
 
While looking through BIOS I noticed the frequency for my ram was wrong. I modified that to the correct higher frequency trying with both sticks and it causes problems with Windows making it unusable. This could explain why it seemed fine before. Going to try just the good stick now at the proper frequency.

EDIT1: The one stick at the proper frequency of 2400mhz still causes problems in Windows. It's possibly a compatibility issue since the RAM possibly came out after the motherboard it's not listed in the manual.

EDIT2: Even at the auto frequency now the single working stick boots into windows with a flickering windows explorer.

Can you run 24mhz ram in Crosshair V Formula-Z stock?
This is not the RAM I have but the motherboard, and this thread I found explained to me why it's not running 2400
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top