Windows 8 Update error 800703F1

Alright so the file loads fine which is odd. Looking in the file it appears to have a pending transaction in place. I had another thread earlier on that had the same entry. I wonder if this is linked.

Alright so before we start trying to fix these manually lets try a less aggressive way first:
Boot into the Windows RE mode: How to use the Windows 8 System Recovery Environment Command Prompt

Once the command Window is displayed please follow the below steps.

First command to enter is wmic logicaldisk get name. you will be given a similar output to:

Code: 
X:\Sources>wmic logicaldisk get name
Name
C:
D:
E:
X:

Now when you are in the RE the drive letters will often move around. start with the first letter that was provided in the list and enter in the following command (for this example we will use C:\ as it is the first one)

dir C:\
-This will display all the folders in the root drive of C

Can you see a folder called C:\Windows in list?
-If you can see C:\Windows then run the DISM command as DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

If you can not see the Windows folder move onto the next Drive letter that we obtained with wmic logicaldisk get name and type in dir <DRIVE LETTER> (replace <DRIVE LETTER> with the drive you would like to check), can you see the Windows Folder?
-If yes, enter in the following command DISM /Image:C:\ /Cleanup-Image /RevertPendingActions and changed the C to what ever Drive letter has the Windows folder

Its just a case of going through each drive letter that was produced from the first list until the Windows folder is found then run the DISM command on that drive

Read More:
 
OK following those instructions I was able to locate the Windows folder in the X: Drive, which happened to the first choice. I entered in the DISM command listed in your post for the X: Drive and received the following messages in return:

"Error 87: The /Image option that is specific points to a running Windows installation. To service the running operating system, use the /Online option. For more information, refer to the help by running DISM.exe /Online /7. The Dism log file can be found at X:\windows\Log\DISM\dism. log"

I ran through the steps one more time and got the following:

"Error 87: The cleanup-image option is unknown. For more information, refer to the help by running DISM.exe /?. The Dism log file can be found at X:\windows\Log\DISM\dism. log"
 
That is rather odd. Lets look at another method:

Please navigate to C:\Windows\winsxs and copy any files with a similar name to pending.xml (e.g. pending.xml, pending.xml.bad, pending.xml_dfsadf78 etc.) to your folder on the Desktop [there may not be any, just if there are]. Then zip up this folder and attach it to your next post.

  1. Rlick on the Start button -> click on Command prompt as Administrator
  2. Inside the Command Prompt windows copy and paste the following command
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG QUERY HKLM\COMPONENTS >1&& notepad 1
  3. Please wait for this to Finish before continuing with rest of the steps.
Please also export the following registry keys, add them into a zip and attach to this post:

  1. Right click on the Start button -> Click on Run -> type regedit
  2. Once 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\WindowsUpdate\

  3. Once selected, click File > Export....
  4. Change the Save as type: to Registry Hive Files (*.*)
  5. Name this file Update (with no file extension) and save it to your Desktop.


Once done please upload this file via Dropbox or One Drive
 
First, start an Elevated Command Prompt: https://www.sysnative.com/forums/wind...vista-7-a.html
and copy and paste in the following:

fsutil resource setautoreset true %SystemDrive%\

attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
del %SystemRoot%\System32\Config\TxR\*

attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
del %SystemRoot%\System32\SMI\Store\Machine\*.blf
del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
REG DELETE HKLM\COMPONENTS /V PendingXmlIdentifier
REG DELETE HKLM\COMPONENTS /V ExecutionState


Restart your computer and try windows update again, if it fails please provide the Pending.xml file sgain
 
OK so when I tried to run that script as Administrator, I got the following results:

what it look like.PNG

basically it looked like a few of the locations could be found so not everything on the script was able to be executed.

Here is a link to the new pending.xml files as per your request (this time around there was no plain 'pending.xml' file any longer):

https://www.dropbox.com/s/u8f0k48aqi0r5vx/new pending.zip?dl=0
 
Thats fine, that basically means there were none of these files to delete.

Can you please upload another COMPONENTS hive for me? I will have to manually make the change.
 
Thank you.

Before continuing, please back up the COMPONENTS hive.

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 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.

SFC /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive
 
Code: 
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-03-04 18:30:47.849
Microsoft Windows 8  - amd64
Using .zip script file at C:\Users\Gordon\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\config\COMPONENTS


The file \\?\C:\Windows\Sysnative\config\COMPONENTS is in use and must be replaced over a reboot.


Successfully pended file for replace over reboot: \\?\C:\Windows\Sysnative\config\COMPONENTS
PowerCopy:: directive completed successfully.








Reboot:: directive completed successfully.








PostRebootCorruptionDetection::
Hash failure for file \\?\C:\Windows\Sysnative\config\COMPONENTS.
 Expected: kieeUPwuyRZE5C2z+eD2t2197zIzGcS3Hfbjksgt8TA=
 Found: Failed to generate hash - file may be in use.
PostRebootCorruptionDetection:: directive failed to complete successfully.








PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\Sysnative\config\COMPONENTS
Successfully restored permissions on C:\Windows\Sysnative\config\COMPONENTS
PostRebootRestorePermissions:: directive completed successfully.








Failed to process all directives successfully.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-03-04 21:45:51.404
----------------------EOF-----------------------



Here is the requested CBS.txt file:

https://www.dropbox.com/s/mm4zod3rxm1kgl1/cbs.txt?dl=0


Thanks!
 
Dam, can you please upload the following:

Export CBS folder

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on File Explorer
  3. Double-click on the C: drive, scroll down to, and double click on the Windows folder.
  4. Find and double click on the Logs folder.
  5. Right-click on the CBS folder, and select Copy.
  6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  7. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
  9. Attach this to your next post please.
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Windows Update Log

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run Inside the Run box copy and paste the following command
    cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
  3. Please go to your desktop and attach WindowsUpdate.txt to your next post
 
This one has been a bit of a puzzle, but this may be the issue here:

Code: 
2015-03-10 21:54:16, Info                  CSI    0000001a Unable to prestage file [l:36{18}]"FlashPlayerApp.exe" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    0000001b The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    0000001c Unable to prestage file [l:22{11}]"activex.vch" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    0000001d The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    0000001e Unable to prestage file [l:42{21}]"FlashPlayerCPLApp.cpl" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    0000001f The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    00000020 Unable to prestage file [l:42{21}]"FlashUtil_ActiveX.dll" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    00000021 The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    00000022 Unable to prestage file [l:42{21}]"FlashUtil_ActiveX.exe" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    00000023 The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    00000024 Unable to prestage file [l:18{9}]"Flash.ocx" for component [ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821".
2015-03-10 21:54:16, Info                  CSI    00000025 The payload directory for the candidate component ([ml:280{140},l:166{83}]"wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_8fa23c48408dcafa") does not exist
2015-03-10 21:54:16, Info                  CSI    00000026 Unable to prestage file [l:22{11}]"activex.vch" for component [ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626".
2015-03-10 21:54:16, Info                  CSI    00000027 The payload directory for the candidate component ([ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_854d91f60c2d08ff") does not exist
2015-03-10 21:54:16, Info                  CSI    00000028 Unable to prestage file [l:42{21}]"FlashUtil_ActiveX.dll" for component [ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626".
2015-03-10 21:54:16, Info                  CSI    00000029 The payload directory for the candidate component ([ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_854d91f60c2d08ff") does not exist
2015-03-10 21:54:16, Info                  CSI    0000002a Unable to prestage file [l:42{21}]"FlashUtil_ActiveX.exe" for component [ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626".
2015-03-10 21:54:16, Info                  CSI    0000002b The payload directory for the candidate component ([ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_854d91f60c2d08ff") does not exist
2015-03-10 21:54:16, Info                  CSI    0000002c Unable to prestage file [l:18{9}]"Flash.ocx" for component [ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626".
2015-03-10 21:54:16, Info                  CSI    0000002d The payload directory for the candidate component ([ml:280{140},l:166{83}]"amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.21408_none_854d91f60c2d08ff") does not exist
2015-03-10 21:54:17, Error                 CSI    00000001 (F) HRESULT_FROM_WIN32(1009) #1# from LoadStore(target = NULL)
[gle=0x80004005]
2015-03-10 21:54:17, Error                 CSI    0000002e@2015/3/11:02:54:17.062 (F) base\wcp\componentstore\com\store.cpp(4878): Error NTSTATUS_FROM_WIN32(1009) originated in function Windows::COM::CComponentStore::MountSMISchemaHive expression: MountSMISchemaHive
[gle=0x80004005]
2015-03-10 21:54:17, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2015-03-10 21:54:17, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20150310011030.log to WER report.
2015-03-10 21:54:17, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20150309235431.log to WER report.
2015-03-10 21:54:17, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20150309192819.log to WER report.
2015-03-10 21:54:17, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20150309153142.log to WER report.
2015-03-10 21:54:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20150309035311.log to WER report.
2015-03-10 21:54:18, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-10 21:54:18, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-10 21:55:46, Error                 CSI    0000002f (F) HRESULT_FROM_WIN32(1009) #307987# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x800703f1]
2015-03-10 21:55:46, Error                 CSI    00000030 (F) HRESULT_FROM_WIN32(1009) #307985# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 38 (0x00000026), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x800703f1]
2015-03-10 21:55:46, Error                 CSI    00000031 (F) HRESULT_FROM_WIN32(1009) #307984# 167473631 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000026, pSink = NULL, disp = 0)
[gle=0x800703f1]
2015-03-10 21:55:46, Error                 CBS    Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x800703f1 - ERROR_BADDB]
2015-03-10 21:55:46, Info                  CSI    00000032@2015/3/11:02:55:46.905 CSI Transaction @0xb86c66a710 destroyed
2015-03-10 21:55:46, Info                  CBS    Perf: Resolve chain complete.
2015-03-10 21:55:46, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x800703f1 - ERROR_BADDB]
2015-03-10 21:55:46, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800703f1 - ERROR_BADDB]
2015-03-10 21:55:46, Info                  CBS    WER: Generating failure report for package: Package_for_KB3044132~31bf3856ad364e35~amd64~~6.2.1.1, status: 0x800703f1, failure source: Resolve, start state: Absent, target state: Staged, client id: WindowsUpdateAgent

Can you please go into C:\Windows\WinSxS\Manifests\
Do you have the following files?
amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626
wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821

If yes can you please upload them to your next post for me?
 
Thanks!

Can you please go into C:\Windows\WinSxS and look for the follow folders:
amd64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_845ba1f2f35eb626
wow64_adobe-flash-for-windows_31bf3856ad364e35_6.2.9200.17291_none_8eb04c4527bf7821

Can you see them? If yes can you please open each one up and post a screenshot back here?
 
Thanks, that would explain why SFC can not find them.


DISM Scan

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command DISM /Online /Cleanup-Image /RestoreHealth
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt, please rename this file to CBS_{Insert forum username here}_{insert todays Date here}.txt For example "CBS_Go The Power_1803.txt"
  5. Please upload CBS_{Username}_{Date}.txt to this thread.
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive
 
You must log in or register to reply here.

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

Back
Top