Server2012R2 Dism Error 0x800f081f - No Updates possible -

We still have some fixing to do.


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 attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

Skript worked fine.
but still no updates.
here is the CBS.log after the update.

FCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-15 10:54:09.623
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\administrator.BVM\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2019-01-15 10:54:09.998
 

Attachments

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 attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

Skipt worked fine.

a Silverlight Update also worked, but no windows Updates.

I also add the CBS folder.

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-16 12:38:45.861
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\administrator.BVM\Desktop\SFCFixScript.txt [1]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.18458_none_a6d23d3905c82dc6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d2f3f83768e..0e682cba416_31bf3856ad364e35_6.3.9600.18458_079661d9f75fd032.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2019-01-16 12:38:46.830
Script hash: Kx3+mIy3yyZI78HjAIpPNyujAjJfTd+arkc3vdIfliY=
----------------------EOF-----------------------

Dropbox - Cbslog.zip
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
I see you have removed the files I requested earlier, please retry updates with ProcMon and post new logs for me so I can diagnose the corruption within the COMPONENTS hive. Thanks.
 
I know. This is going to be the case for a good long while, because there are a number of issue to resolve here before the machine successfully updates.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates with ProcMon and if any fail, attach CBS.log and ProcMon log
 

Attachments

Hi guys,
sorry for the delay but I catched a strange infection.

Ok here I go again.

I ran the script and tried a update. some are working.The security and Quality rollup Updates still not work.

logfile.zip
 

Attachments

Please try installing only KB4483187 with ProcMon enabled and attach CBS log + ProcMon.log uploaded somewhere.

If it reverts, make sure to include the setupapi.dev.log which can be found at: C:\Windows\Inf
 
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