[SOLVED] Windows 10 update, feature install, SFC, DISM, SFCfix, and repair install all fail

d05062020

Member
Joined
Jun 16, 2018
Posts
10
I am hoping that I might be able to get some help with my problem: Windows Update, sfc, DISM, SFCfix, and repair install all fail on my Windows 10 Pro 64-bit machine (version 1709).


SFC doesn't work at all. It just says "Windows Resource Protection could not start the repair service."


Windows Update and DISM report error 0x8000FFFF. This also happens when trying to add/remove any Windows features.


The Windows repair install fails before the first reboot.


I tried safe mode, but it makes no difference.


I have attached logs, but SFCfix doesn't finish even after waiting for many hours, so I don't have the log file. It just halts after running DISM (DISM completes and displays the fail error, followed by the log file location) and there is no hard drive or CPU activity. Instead of the log, I just copied the command window output and saved that.


I ran chkdsk /r and it corrected errors with the volume bitmap. Also checked the SSD by running a long self test, and there were no problems.

Thanks for any help.
 
Last edited by a moderator:
Code:
2018-06-16 18:33:33, Info                  DISM   DISM Driver Manager: PID=10688 TID=11076 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-06-16 18:33:33, Error                 DISM   DISM Driver Manager: PID=10688 TID=11076 Failed trying to load drvstore.dll - CDmiApi::InternalInitialize(hr:0x8007007e)
2018-06-16 18:33:33, Error                 DISM   DISM Driver Manager: PID=10688 TID=11076 Failed to initialize the DMI API. - CDmiApi::get_DriverStore(hr:0x8007007e)
2018-06-16 18:33:33, Error                 DISM   DISM Driver Manager: PID=10688 TID=11076 Failed to open the driver store. - CDriverManager::GetDriverPackageCollection(hr:0x8007007e)
2018-06-16 18:33:33, Error                 DISM   API: PID=1788 TID=10880 Failed to retrieve drivers from image. AllDrivers=FALSE. - CGetDriversCommandObject::InternalExecute(hr:0x8007007e)
2018-06-16 18:33:33, Error                 DISM   API: PID=1788 TID=10880 InternalExecute failed - CBaseCommandObject::Execute(hr:0x8007007e)
2018-06-16 18:33:33, Error                 DISM   API: PID=1788 TID=6512 CGetDriversCommandObject failed - DismGetDriversExInternal(hr:0x8007007e)
2018-06-16 18:33:33, Info                  DISM   API: PID=1788 TID=6512 Leave DismGetDriversExInternal - DismGetDriversExInternal
2018-06-16 18:33:33, Error                 SP     Failed to get driver packages from the online system. Error: 0x8007007E[gle=0x0000007a]
2018-06-16 18:33:35, Error                 SP     Operation failed: Process Drivers for Migration. Error: 0x8007007E[gle=0x000000b7]
2018-06-16 18:33:35, Info                  SP     Operation can retry, we'll attempt to revert its execution.
2018-06-16 18:33:35, Info                  SP     Attempt to revert execution for operation 30
2018-06-16 18:33:35, Error                 SP     COperationQueue::Sort: Could not find an execution phase for 75
2018-06-16 18:33:35, Error                 SP     Operations can no longer be sorted following an attempt to retry a failed operation.
2018-06-16 18:33:35, Info                  MOUPG  PreFinalize: Registering Setup Platform error: [0x8007007E]
2018-06-16 18:33:35, Error                 SP     ExecuteOperations: Failed execution phase Pre-Finalize. Error: 0x8007007E
2018-06-16 18:33:35, Info                  MOUPG  MoSetupPlatform: SetupPlatform::INewSystem::ExecuteCurrentOperations returned: [0x4]
2018-06-16 18:33:35, Error                 MOUPG  MoSetupPlatform: ExecuteCurrentOperations reported failure!
2018-06-16 18:33:35, Error                 MOUPG  MoSetupPlatform: Using action error code: [0x8007007E]
2018-06-16 18:33:35, Error                 MOUPG  CDlpActionPreFinalize::ExecuteRoutine(545): Result = 0x8007007E

Looks like setup cannot get a list of installed drivers.

Code:
2018-06-16 13:48:31, Info                  CSI    00000046 Pending transaction content must be resolved, cannot begin another transaction yet
2018-06-16 13:48:31, Error                 CSI    00000047 (F) E_UNEXPECTED #1034084# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8000ffff]
2018-06-16 13:48:31, Info                  CBS    Not able to get CBS component onwers for component amd64_1394.inf_31bf3856ad364e35_10.0.16299.15_none_1e1b8291770c653c [HRESULT = 0x8000ffff - E_UNEXPECTED]
2018-06-16 13:48:31, Info                  CBS    Failed to create a new corrupted component entry. [HRESULT = 0x8000ffff - E_UNEXPECTED]

Please back up any important data before continuing.

Revert Pending Changes
1. Click your Start button so it brings up the Start Screen.
2. Hold down your left Shift button while you click the Power button in the upper-right and choose Restart. Note: Keep the shift button held down while the machine restarts until the Choose an Option screen shows.
View attachment 13059

3. Click the Troubleshoot button.
4. Click the Advanced Options button.
5. Choose the Command Prompt button.
6. Select your account and put in your password if prompted.
7. Once the command Window is displayed please follow the below steps.
8. Type notepad into the command prompt and hit enter.
9. Click the File menu in notepad and choose Open. Click on the This PC icon on the left hand side so that you see all the drive letters. You sill see Boot (X:) and likely others. Look for the drive letter that is associated to Local Disk. It won't be drive letter X. If you are unsure which one represents your local disk you can double-click on each drive and look to see if there is a Windows directory in it. That will be the drive letter we are interested in.
10. Once you've identified the driver letter you may cancel out of this screen and close notepad.
11. Now type the following into the Command Prompt replacing C (shown in red) with the drive letter you identified in bullet#9. Note: there is a space after C:\ as well as before the last forward slash.
DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

12. If all goes well you will see the following as the last few lines. Please let me know if you don't.
Code:
Reverting pending actions from the image...
The operation completed. Any revert of pending actions will be attempted after reboot.
The operation completed successfully.
 
Many thanks for the reply. I did that and received the successful message that you showed.

However, I'm afraid the problem is still not fixed (still sfc, DISM, repair install all fail). I have attached current CBS and DISM logs.
 
Last edited by a moderator:
Please try the following:

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    Dism /online /Get-Drivers

  4. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  5. Paste (Ctrl+V) it into your next post, then zip and attach C:\Windows\Logs\DISM\DISM.log please.
 
Thanks again for the reply. Unfortunately, it exited with an error, as in the attached log and command window output. I also included the CBS log again.


It's also worth noting that some packages are still "Install Pending", even after attempting to revert pending changes using the steps you gave me yesterday. The output of "dism /online /get-packages" includes the following two:
Package Identity : Package_for_KB4131372~31bf3856ad364e35~amd64~~16299.428.1.0
State : Install Pending
Release Type : Update
Install Time : 09/05/2018 15:38


Package Identity : Package_for_KB4134661~31bf3856ad364e35~amd64~~10.0.1.2
State : Install Pending
Release Type : Update
Install Time : 14/06/2018 15:32

Attempting to remove these packages to prevent the pending install does not work. I wonder if these packages could be the reason why the driver store cannot be fixed? I noticed a line in the cbs log about not proceeding because of pending transactions, and I assume it may be referring to these. I don't know how to force them to uninstall (or perhaps to manually remove these pending transactions?).
 
Last edited by a moderator:
Export Component Based Servicing

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

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  7. Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.

Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace
 
I am back now and have exported the registry key you requested - attached to this post.
 
Last edited by a moderator:
So sorry! I'm not sure how I missed this.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

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

Download SFCFix.zip from Sendspace.com - send big files the easy way

Once complete, try the upgrade to 1803 again. If you haven't already created USB installation media, use the tool here: Download Windows 10

Make sure to select the option to keep your files, settings, and apps.
 
Glad to help :thumbsup2:

I'll mark the thread solved. Please post back if you encounter any problems and I'll continue to assist you.
 

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

Back
Top