none
When Update Installation from windows 10 1607 (OS Build 14393.1066) to version 1703 Build15063 I get Error 0x8007001f

    Question

  • when installing windows 10 I get

    Something went wrong

    You can contact Microsoft Support for help with this error. Here is the error code 0x8007001f.

    here is the contents of setuperr.log

    "

    2017-04-28 16:21:36, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104
    2017-04-28 16:21:36, Error                 MOUPG  CSetupManager::ExecuteInstallMode(753): Result = 0x800705BB
    2017-04-28 16:21:36, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(396): Result = 0x800705BB
    2017-04-28 16:21:36, Error                 MOUPG  CSetupManager::Execute(232): Result = 0x800705BB
    2017-04-28 16:21:36, Error                 MOUPG  CSetupHost::Execute(368): Result = 0x800705BB
    2017-04-28 16:26:13, Error                 DU     DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for syswow64\drivers\aichargerplus.sys, 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for [syswow64\drivers\aichargerplus.sys] 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for syswow64\drivers\asio.sys, 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for [syswow64\drivers\asio.sys] 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for syswow64\drivers\asupio.sys, 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for [syswow64\drivers\asupio.sys] 0x80070003
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for c:\windows\system32\drivers\intelhaxm.sys, 0x80070005
    2017-04-28 16:27:32, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\intelhaxm.sys] 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for c:\windows\system32\drivers\vboxdrv.sys, 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\vboxdrv.sys] 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for c:\windows\system32\drivers\vboxnetlwf.sys, 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\vboxnetlwf.sys] 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for c:\windows\system32\drivers\vboxusbmon.sys, 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\vboxusbmon.sys] 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for c:\windows\system32\drivers\vmnetbridge.sys, 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\vmnetbridge.sys] 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for c:\windows\system32\drivers\vmnetuserif.sys, 0x80070005
    2017-04-28 16:27:33, Error                 CONX   Failed hashing for [c:\windows\system32\drivers\vmnetuserif.sys] 0x80070005

    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::XmlUtils::WriteProperty (587):   Could not write property value  32/3: [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::XmlUtils::WritePropertyList (539):   Could not write property in Inventory [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::XmlUtils::GetAndWritePropertyList (705):   Failed to write asset property list for Inventory [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::XmlUtils::WriteAsset (668):   Could not get and write Inventory property list: [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::XmlUtils::WriteAssets (639):   Failed writing asset [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:30:02, Error                 CONX   Windows::Compat::Appraiser::OutputEverything::DoOutput (212):   Writing Assets failed: [0xc00cee2b].[gle=0xc00cee2b]
    2017-04-28 16:31:46, Error                 CONX   ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found 2 compat info nodes for the specified driver package instead of just one.
    2017-04-28 16:31:46, Error                 CONX   ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found 2 compat info nodes for the specified driver package instead of just one.
    2017-04-28 16:31:55, Error      [0x0803b6] MIG    Can't retrieve group information for user NT SERVICE\SQLTELEMETRY$SQLEXPRESS. NetUserGetLocalGroups failed 0x000008AD
    2017-04-28 16:31:55, Error      [0x0803b6] MIG    Can't retrieve group information for user NT SERVICE\SQLTELEMETRY. NetUserGetLocalGroups failed 0x000008AD
    2017-04-28 16:33:49, Error      [0x08039d] MIG    Cannot add mapping for user profile C:\Users\SQLTELEMETRY. Error: 32: Win32Exception: The process cannot access the file because it is being used by another process. [0x00000020] __cdecl Mig::CIndirectKeyMapper::CIndirectKeyMapper(class UnBCL::String *,struct HKEY__ *,class UnBCL::String *,class UnBCL::String *,int,int,const Mig::HiveLoadRetryOptions *)[gle=0x000000cb]
    2017-04-28 16:33:49, Error      [0x080801] MIG    User profile loading error. Aborting due to external request.[gle=0x000000cb]
    2017-04-28 16:33:49, Error                        InitDownlevelOCMode caught exception: Win32Exception: User profile loading error. Aborting due to external request.: The specified user does not have a valid profile. [0x000004E5] class Mig::CUserContext *__cdecl Mig::COnlineWinNTPlatform::AddUserContext(class Mig::CRegistryDataStore *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::Array<class UnBCL::String *> *,int,struct _FILETIME,int,int,int,class UnBCL::String *,class UnBCL::String *)
    2017-04-28 16:33:49, Error                 MIG    OC Exception: OC::CDownlevelOCStore::CDownlevelOCStore: Engine's InitDownlevelOCMode failed.
    2017-04-28 16:33:49, Error                 SP     Could not save OC status. Error: 0x8007001F
    2017-04-28 16:34:09, Error      [0x0803b6] MIG    Can't retrieve group information for user NT SERVICE\SQLTELEMETRY$SQLEXPRESS. NetUserGetLocalGroups failed 0x000008AD
    2017-04-28 16:34:09, Error      [0x0803b6] MIG    Can't retrieve group information for user NT SERVICE\SQLTELEMETRY. NetUserGetLocalGroups failed 0x000008AD
    2017-04-28 16:36:03, Error      [0x08039d] MIG    Cannot add mapping for user profile C:\Users\SQLTELEMETRY. Error: 32: Win32Exception: The process cannot access the file because it is being used by another process. [0x00000020] __cdecl Mig::CIndirectKeyMapper::CIndirectKeyMapper(class UnBCL::String *,struct HKEY__ *,class UnBCL::String *,class UnBCL::String *,int,int,const Mig::HiveLoadRetryOptions *)[gle=0x000000cb]
    2017-04-28 16:36:03, Error      [0x080801] MIG    User profile loading error. Aborting due to external request.[gle=0x000000cb]
    2017-04-28 16:36:03, Error                        MigPlatformStartupOnline caught exception: Win32Exception: User profile loading error. Aborting due to external request.: The specified user does not have a valid profile. [0x000004E5] class Mig::CUserContext *__cdecl Mig::COnlineWinNTPlatform::AddUserContext(class Mig::CRegistryDataStore *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::String *,class UnBCL::Array<class UnBCL::String *> *,int,struct _FILETIME,int,int,int,class UnBCL::String *,class UnBCL::String *)
    2017-04-28 16:36:03, Error                 SP     pSPDoMainGather: Engine initialization failed with error: 0x00000004
    2017-04-28 16:36:03, Error                 SP     CGatherData: Migration phase failed. Status: 4[gle=0x00000012]
    2017-04-28 16:36:03, Error                 SP     Operation failed: Gather data, scope: EVERYTHING. Error: 0x8007001F[gle=0x000000b7]
    2017-04-28 16:36:03, Error                 MOUPG  MoSetupPlatform: ExecuteCurrentOperations reported failure!
    2017-04-28 16:36:03, Error                 MOUPG  MoSetupPlatform: Using action error code: [0x8007001F]
    2017-04-28 16:36:03, Error                 MOUPG  CDlpActionDataMigrate::MigrateData(1037): Result = 0x8007001F
    2017-04-28 16:36:03, Error                 MOUPG  CDlpActionDataMigrate::ExecuteRoutine(655): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CSetupManager::ExecuteTask(2083): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CSetupManager::ExecuteTask(2046): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CSetupManager::ExecuteInstallMode(833): Result = 0x8007001F
    2017-04-28 16:36:04, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(396): Result = 0x8007001F
    2017-04-28 16:36:16, Error                 MOUPG  CSetupManager::Execute(232): Result = 0x8007001F
    2017-04-28 16:36:16, Error                 MOUPG  CSetupHost::Execute(368): Result = 0x8007001F

    "

    I appreciate any help for resolving this problem.

    Thanks a lot


    Need Help please any body in the email programs


    Friday, April 28, 2017 1:47 PM

All replies

  • Hello,

    Try suggestions mentioned here and see if they helps:

    https://www.kapilarya.com/fix-windows-10-creators-update-failed-to-install

    Hope this helps, Good luck :)

    Microsoft MVP (Windows and Devices for IT)

    Windows Insider MVP

    Windows Help & Support [www.kapilarya.com]

    Saturday, April 29, 2017 3:15 AM
  • Please post the setupact.log

    Code
    8007001F - 0x4000D

    Cause
    General failure, a device attached to the system is not functioning.
        
    Mitigation
    Analyze log files in order to determine the device that is not functioning properly. Disconnect, update, or replace the device.

    See the link in the above post to perform steps 1 - 10.

    In addition please disconnect all possible devices.

    For the reliability control panel type reliability in the left lower corner search:

    https://www.howtogeek.com/166911/reliability-monitor-is-the-best-windows-troubleshooting-tool-you-arent-using/

    Make sure you place into clean boot:

    https://social.technet.microsoft.com/wiki/contents/articles/29876.how-to-perform-a-clean-boot-in-windows-10.aspx

    Also please create a new user profile to use for the upgrade.

    Then reattempt upgrade.

    If upgrade works great.

    If upgrade fails then please re-post both error logs again.



    Saturday, April 29, 2017 4:16 AM
  • Setupact.log contents

    I posted a link to my setupact.log contents... please help me.

    Also I have disabled all usb ports like headphone and camera and try to install the latest version of windows but I encounter the same problem.

    I appreciate any help


    Need Help please any body in the email programs

    Saturday, April 29, 2017 7:37 AM
  • Please indicate which steps you were able / not able to complete.

    1) run the windows update troubleshooter?

    2) clear temporary files/cache using disk cleanup utility in windows

    3) delete $WINDOWS.~BT folder

    4) rename the SoftwareDistribution folder to SoftwareDistribution.old

    5) clean boot

    6) Change power options.  Turn off fast start up.  Reboot and turn on fast startup. 

    7) View reliability control panel for any issues

    8) administrative command prompt sfc /scannow and dism /online /cleanup-image /restorehealth

    9) After the above 8 steps try to upgrade again with the new user name and in clean boot.  If it fails to upgrade again then using administrative command prompt type:  C:\$WINDOWS.~BT\Sources\Panther

    10) display a new onedrive log for each:

    setuperr.log

    setupact.log

    11) download windows 10 iso to the desktop as a virtual DVD

    https://www.microsoft.com/en-gb/software-download/windows10

    12) and copy the windows 10 iso to a USB flash drive to create a bootable windows 10 iso

    13) back up all files, save bookmarks, remember applications in case a clean install is needed to update

    14) Each computer manufacturer has a keyboard F key to boot using a USB.  Find out the F key for USB booting.


    In the first post I saw that you posted the setuperr.log  and missed the setupact.log

    Noted in the posted log were:

    Failed hashing for 7 different drivers.

    Problems with users:  NT SERVICE\SQLTELEMETRY and NT SERVICE\SQLTELEMETRY$SQLEXPRESS

    These may be related to:  https://docs.microsoft.com/en-us/sql/database-engine/install-windows/view-and-read-sql-server-setup-log-files

    See if you can find this log file:  %programfiles%\ Microsoft SQL Server\130\Setup Bootstrap\Log\\

    Did the second attempt to upgrade while in clean boot produce the same or a different error code?  Please post one drive links for each of the new log files.





    Saturday, April 29, 2017 8:59 AM
  • @questionsformicrosoftproducts

    I tried every thing up to step 9

    just sfc found an errors but doesn't fix them all ... and dism  didn't fid a source I downloaded an iso for 14393.0 and the same thing ( didn't find a source ) with this error

    ____________________________

    Error: 0x800f081f
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077
    .

    _________________

    I don't want to uninstall my windows

    and after all the steps I am having the same error


    Saturday, April 29, 2017 10:16 AM
  • The dism restorehealth should be working for version 1607.

    The dism restorehealth is malfunctioning for version 1703.

    Does windows upgrades work or are their failures?

    If there are/were failures what were the KB numbers?

    If the sfc scannow integrity violations are fixed this may enable you to upgrade.  We need more information.

    When sfc /scannow completed it displayed the location of the CBS files.

    And when Dism restorehealth completed it displayed the location of the DISM files.

    Click windows + r keys simultaneously and post your current version and build.

    Please use onedrive or any cloud source to post links for these 4 logs:

    cbs log

    dism log

    The repeat logs for each:

    setuperr.log

    setupact.log

    The alternatives now are to spend time working up the operating system integrity violations, perform a reset with save files and applications, an in place installation or a clean install.

    It is always best to have your files backed up.

    Were you able to create a bootable windows 10 iso?

    Saturday, April 29, 2017 8:28 PM
  • The heading of this post is confusing because it mixes versions and builds.

       1607 and 1703 are version names. 14393 and 15063 are the corresponding build numbers.


    Bill

    Sunday, April 30, 2017 5:06 AM
  • I updated the heading .

    I mean version 1703 Build 15063

    Sunday, April 30, 2017 8:42 AM
  • questionsformicrosoftproducts Hi

    Windows upgrade doesn't work.

    As I mentioned I have an error 0x8007001f.

    I have windows 10 version 1607 build 14393.1066.

    When I do dism I see 14393.0 is that ok ?.

    I attached the four files ( cbs.log, dism.log, setuperr.log, setupact.log ).

    CBS.log

    dism.log

    setuperr.log

    setupact.log

    I can boot from windows 10 iso but  I can't do upgrade from there because to do upgrade I must enter windows and upgrade from there

    thank you


    Need Help please any body in the email programs

    Friday, May 5, 2017 10:44 AM
  • The operating system/registry is corrupt and could not be fixed by scannow nor restorehealth.

    These are just some of the listed problems displayed in the log beginning on 4/27 and 4/28:


    2017-04-29 17:54:17, Error                 DISM   DISM Package Manager: PID=3492 TID=7916 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

    2017-04-27 19:10:04, Info                  DISM   API: PID=17060 TID=10356 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    2017-04-27 19:10:04, Info                  DISM   API: PID=17060 TID=10356 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    2017-04-27 19:10:04, Info                  DISM   DISM Provider Store: PID=17060 TID=16388 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-27 19:10:04, Warning               DISM   DISM Provider Store: PID=17060 TID=16388 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 19:10:07, Warning               DISM   DISM Provider Store: PID=17072 TID=11000 Failed to Load the provider: C:\Users\Ayman\AppData\Local\Temp\D1288903-934A-49E5-BA54-2C9078047F93\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 19:10:07, Info                  DISM   DISM Provider Store: PID=17072 TID=11000 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-27 21:27:20, Info                  DISM   API: PID=15832 TID=18472 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    2017-04-27 21:27:20, Info                  DISM   API: PID=15832 TID=18472 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    2017-04-27 21:27:20, Info                  DISM   DISM Provider Store: PID=15832 TID=6132 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-27 21:27:20, Warning               DISM   DISM Provider Store: PID=15832 TID=6132 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 21:27:20, Warning               DISM   DISM Provider Store: PID=15832 TID=6132 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 21:27:23, Warning               DISM   DISM Provider Store: PID=7796 TID=3320 Failed to Load the provider: C:\WINDOWS\TEMP\9111A610-B486-458D-BE4B-1BE824E84C55\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 21:27:20, Warning               DISM   DISM Provider Store: PID=15832 TID=6132 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-27 21:27:23, Info                  DISM   DISM Provider Store: PID=7796 TID=3320 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-28 10:32:02, Info                  DISM   API: PID=12420 TID=12464 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    2017-04-28 10:32:02, Info                  DISM   API: PID=12420 TID=12464 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    2017-04-28 10:32:02, Info                  DISM   DISM Provider Store: PID=12420 TID=8260 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-28 10:32:02, Warning               DISM   DISM Provider Store: PID=12420 TID=8260 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 10:32:02, Warning               DISM   DISM Provider Store: PID=12420 TID=8260 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    DISM   DISM Provider Store: PID=12844 TID=11216 Failed to Load the provider: C:\WINDOWS\TEMP\BCB5DB89-61AA-4FFC-BE0F-1C6818CE54F1\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    DISM   DISM Provider Store: PID=12844 TID=11216 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    DISM   API: PID=6536 TID=5604 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    DISM   API: PID=6536 TID=5604 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    DISM   DISM Provider Store: PID=6536 TID=8524 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

     DISM   DISM Provider Store: PID=6536 TID=8524 Failed to Load the provider: C:\WINDOWS\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    DISM   DISM Provider Store: PID=15100 TID=10112 Failed to Load the provider: C:\Users\Ayman\AppData\Local\Temp\C74D2C39-0DD7-412E-814D-EF90B711F413\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    DISM   DISM Provider Store: PID=15100 TID=10112 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    DISM   API: PID=14596 TID=15904 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    DISM   API: PID=14596 TID=15904 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    2017-04-28 15:20:39, Info                  DISM   DISM Provider Store: PID=14596 TID=9996 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-28 15:20:39, Warning               DISM   DISM Provider Store: PID=14596 TID=9996 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 15:20:39, Warning               DISM   DISM Provider Store: PID=14596 TID=9996 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 15:20:39, Warning               DISM   DISM Provider Store: PID=14596 TID=9996 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 16:26:54, Info                  DISM   API: PID=11196 TID=14548 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath

    2017-04-28 16:26:54, Info                  DISM   API: PID=11196 TID=14548 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath

    2017-04-28 16:26:54, Info                  DISM   DISM Provider Store: PID=11196 TID=9116 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2017-04-28 16:26:54, Warning               DISM   DISM Provider Store: PID=11196 TID=9116 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 16:26:54, Warning               DISM   DISM Provider Store: PID=11196 TID=9116 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 16:26:54, Warning               DISM   DISM Provider Store: PID=11196 TID=9116 Failed to Load the provider: C:\$WINDOWS.~BT\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 16:26:55, Warning               DISM   DISM Provider Store: PID=13000 TID=13748 Failed to Load the provider: C:\Users\Ayman\AppData\Local\Temp\954222FD-D50B-4190-B58D-B5CA63FEC2B4\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-28 16:26:55, Info                  DISM   DISM Provider Store: PID=13000 TID=13748 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect





    The setupact.log reported:
    failure to find drivers
    failure to add drivers
    failure to add services
    failed hashings
    failure to get imag paths
    etc


    There are many problems.

    Have you been able to back up your files?

    The possible options are to upgrade or repair.
    1) Upgrade:
    a) Using windows updates:

    win + r simultaneously then enter: ms-settings:windowsupdate

    b) With update assistant:

    https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

    c) With windows installation media, either bootable windows 10 iso or virtual DVD

    https://www.microsoft.com/en-us/software-download/windows10

    As an in place upgrade or a clean install.

    2) If upgrade does not work then you can use the windows troubleshooting options
    a) reset with save files
    b) reset with remove all files





    Let's perform some new steps and repeat or verify others.

    1) open control panel in large or small font then click troubleshooting and in the left panel click expand all.

    2) run the windows update troubleshooter

    https://support.microsoft.com/en-us/help/2970908/how-to-use-microsoft-easy-fix-solutions

    3) perform windows updates and see whether windows updates is malfunctioning or if you are able to update to the latest updates: version 1607 build 14393.1066

    Open administrative command prompt and type these commands:

    1) chkdsk

    2) winver

    3) sfc /scannow

    4) dism /online /cleanup-image /checkhealth

    5) dism /online /cleanup-image /scanhealth

    6) dism /online /cleanup-image /restorehealth

    On the top bar of the administrative command prompt right click then on the menu left click edit then select all.  Then right click the top bar again then left click copy and then paste into the forum so we can view the results of each 1 to 6.

    7) perform clean boot

    https://social.technet.microsoft.com/wiki/contents/articles/29876.how-to-perform-a-clean-boot-in-windows-10.aspx

    8) open windows updates ( win + r simultaneously then enter: ms-settings:windowsupdate) and look immediately below update history for:

    Good news!  The Windows 10 Creators Update is on its way.  Want to be one of the first to get it?

    Yes, show me how

    Plan to perform windows updates either from this window or with the bootable windows 10 iso.

    https://support.microsoft.com/en-us/help/12373/windows-update-faq

    You will need to know the F key to chose the boot device.  Each computer manufacturer has a different F key.  What is the make and model of your computer?

    9) open administrative command prompt and enter:

    a) net stop wuauserv

    b) net stop bits

    c) rename C:\Windows\SoftwareDistribution SoftwareDistribution.bak

    d) new start wuauserv

    e) net start bits

    https://www.howtogeek.com/247380/how-to-fix-windows-update-when-it-gets-stuck/

    https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components

    http://www.thewindowsclub.com/software-distribution-folder-in-windows

    10) search for $WINDOWS.~BT and delete it

    https://www.kapilarya.com/fix-windows-10-creators-update-failed-to-install

    11) attempt windows update in clean boot

    12) attempt windows upgrade in clean boot or reboot and use bootable windows 10 iso

    12) for any windows upgrade failure open administrative command prompt and enter:  C:\$WINDOWS.~BT\Sources\Panther

    13) post these two new logs:

    setuperr.log

    setupact.log

    Saturday, May 6, 2017 1:19 AM
  • Hi questionsformicrosoftproducts,

    I think dism isn't working well because I don't have an install.wim or install.esd for windows 10.0.14393.1066
    The component store is repairable.

    But there is no source for my version of windows.

    Please give me link to download this version ( 10.0.14393.1066 )

    And I think all the problems will go away.

    Thanks

    Thursday, May 11, 2017 2:35 PM
  • I followed the steps step by step

    and I get the following

    _________________________________

    C:\WINDOWS\system32>chkdsk
    The type of the file system is NTFS.
    WARNING!  /F parameter not specified.
    Running CHKDSK in read-only mode.
    Stage 1: Examining basic file system structure ...
      1990912 file records processed.
    File verification completed.
      20810 large file records processed.
      0 bad file records processed.
    Stage 2: Examining file name linkage ...
      2447410 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      228250 data files processed.
    CHKDSK is verifying Usn Journal...
      41612432 USN bytes processed.
    Usn Journal verification completed.
    Windows has scanned the file system and found no problems.
    No further action is required.
     999690239 KB total disk space.
     916063964 KB in 1656688 files.
        777736 KB in 228251 indexes.
             0 KB in bad sectors.
       2150359 KB in use by the system.
         65536 KB occupied by the log file.
      80698180 KB available on disk.
          4096 bytes in each allocation unit.
     249922559 total allocation units on disk.
      20174545 allocation units available on disk.
    C:\WINDOWS\system32>winver
    C:\WINDOWS\system32>sfc /scannow
    Beginning system scan.  This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0
    Image Version: 10.0.14393.0
    The component store is repairable.
    The operation completed successfully.
    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0
    Image Version: 10.0.14393.0
    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0
    Image Version: 10.0.14393.0
    [==========================100.0%==========================]
    Error: 0x800f081f
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    _________________________________

    and when I tried to upgrade the windows using the create tool and choose upgrade

    I get the following two directories

    $WINDOWS.~BT

    $Windows.~WS

    this rar is the content of my setuperr.log and setupact.log

    setupact_setuperr_contents


    Need Help please any body in the email programs

    Thursday, May 11, 2017 3:40 PM