[SOLVED] [WinServer2012 x64] WU 80070246. DISM Error: 582 illegal character was encountered.

Sysnative Windows Update · Sep 1, 2017

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

jwolber · Sep 1, 2017

Ran fix:

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-01 19:50:37.808
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-packagemanager_31bf3856ad364e35_6.2.9200.16384_none_e982cffcc4ab0a68.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-packagemanager_31bf3856ad364e35_6.2.9200.16384_none_e982cffcc4ab0a68.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-packagemanager_31bf3856ad364e35_6.2.9200.16384_none_e982cffcc4ab0a68.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2017-09-01 19:50:38.574
Script hash: 6KVqHV+21CGT8acwN+DiMK4ZTo82czJSYAfv220cqi4=
----------------------EOF-----------------------

Also ran DISM again with proc mon running - CBS log is attached. Here is a link to the new logfile.pml - https://netorg2466719-my.sharepoint...5d6410c9363b2&authkey=ATxFKGgeVL19t7Ura-BbCJQ

Thank you again!

Sysnative Windows Update · Sep 2, 2017

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.

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

jwolber · Sep 2, 2017

Here is the result;

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-02 13:37:44.925
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2017-09-02 13:37:44.925
Script hash: bvlNUN73P3Gik921jng2jsf93Bhvq9oidi4cXjmoQ08=
----------------------EOF-----------------------

I again ran dism while proc mon was running. CBS log is attached and here is a link to the Logfile.pml - https://netorg2466719-my.sharepoint...cdb8e79e19635&authkey=ARjqM8qy4yBZ5KibFh0a2y4

Thanks!

Sysnative Windows Update · Sep 2, 2017

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.

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

jwolber · Sep 4, 2017

Sorry for the delay, here are the results;

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-04 19:13:14.987
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [1]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16384_none_37aba8e28c19a5f9.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16384_none_37aba8e28c19a5f9.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16384_none_37aba8e28c19a5f9.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2017-09-04 19:13:15.801
Script hash: k9jhl7VUJBqyhiAaiqwNHC7hYMDjMVneUz0Fc3ByBV8=
----------------------EOF-----------------------

Ran dism with proc mon running. Here is a link to the logfile - https://netorg2466719-my.sharepoint...5d0b903d47ae2&authkey=ATPMfzBs8iP7u3kMlHa3jtk

CBS log is attached. Thanks!

Sysnative Windows Update · Sep 5, 2017

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

jwolber · Sep 5, 2017

Results from script:

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-05 14:57:57.508
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [1]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16420_none_37e889288bec961e.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16420_none_37e889288bec961e.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16420_none_37e889288bec961e.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2017-09-05 14:57:58.289
Script hash: Xf+NxObWCpooalrr4h0Rd1g1eDASPBZs+iXe1ve/JUU=
----------------------EOF-----------------------

Also ran DISM with ProcMon running, same results; Error Code 14005 here is a link to the logfile.pml - https://netorg2466719-my.sharepoint...48a2fe6bcb994&authkey=AaBT5Q6mUPKKiNS7rzOm7zk

CBS log is attached.

Thanks again!

Sysnative Windows Update · Sep 5, 2017

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

cd c:\windows\winsxs\manifests

wait a few seconds then when a new line appears copy and paste:

dir /s x86_ntprint.inf_31bf3856ad364e35_6.2.9200* >%userprofile%\desktop\ntprint.txt

You should then see a file on your desktop called: ntprint.txt

Attach it to your next reply.

jwolber · Sep 5, 2017

Here you go. Thanks!

Sysnative Windows Update · Sep 5, 2017

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.

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

jwolber · Sep 5, 2017

This has been run here are the results;

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-05 20:26:13.927
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16430_none_37ddb93c8bf4b20f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16451_none_37c919ae8c040348.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17072_none_37b45bc08c137986.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17104_none_38020dae8bd8e5c4.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17170_none_37b25d128c1543ff.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20521_none_3873263da5094f3f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20531_none_38685651a5116b30.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20555_none_3856b7a1a51e086e.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21191_none_38275869a54237db.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21220_none_38720979a50a5814.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16430_none_37ddb93c8bf4b20f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16451_none_37c919ae8c040348.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17072_none_37b45bc08c137986.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17104_none_38020dae8bd8e5c4.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17170_none_37b25d128c1543ff.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20521_none_3873263da5094f3f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20531_none_38685651a5116b30.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20555_none_3856b7a1a51e086e.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21191_none_38275869a54237db.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21220_none_38720979a50a5814.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16430_none_37ddb93c8bf4b20f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.16451_none_37c919ae8c040348.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17072_none_37b45bc08c137986.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17104_none_38020dae8bd8e5c4.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.17170_none_37b25d128c1543ff.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20521_none_3873263da5094f3f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20531_none_38685651a5116b30.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.20555_none_3856b7a1a51e086e.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21191_none_38275869a54237db.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ntprint.inf_31bf3856ad364e35_6.2.9200.21220_none_38720979a50a5814.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 18 datablocks.
Finish time: 2017-09-05 20:26:14.414
Script hash: SInrL/F6gexdy3XOHnQt2YNXS1hza/gCW4Sd540shM8=
----------------------EOF-----------------------

I also ran DISM with PROCMON running here is a link to the logfile.pml - https://netorg2466719-my.sharepoint...4cf0a4412df25&authkey=Ae7JEF_P14Eitd_AWE7ksk4

CBS log is attached.

Sysnative Windows Update · Sep 5, 2017

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

cd c:\windows\winsxs\manifests

wait a few seconds then when a new line appears copy and paste:

dir /s x86_prnms003.inf_31bf3856ad364e35_6.2.9200* >%userprofile%\desktop\prnms003.txt

You should then see a file on your desktop called: prnms003.txt

Attach it to your next reply.

jwolber · Sep 5, 2017

Here ya go!

Sysnative Windows Update · Sep 5, 2017

Before running DISM again, please set a capture filter in Process Monitor to only capture where Process Name = TiWorker.exe. You can do this using Filter menu.
Also, make sure you select Drop Filtered Events before you start the capture.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

jwolber · Sep 6, 2017

Alright it looks like we are getting somewhere;

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-09-06 00:42:46.078
Microsoft Windows Server 2012  - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16384_none_4f7a847fa546ca5d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16420_none_4fb764c5a519ba82.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16451_none_4f97f54ba53127ac.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16518_none_4fca38e7a50a6670.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16676_none_4f875ab1a53cd88f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17170_none_4f8138afa5426863.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20521_none_504201dabe3673a3.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20555_none_5025933ebe4b2cd2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20623_none_50440454be34a378.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20784_none_500426fcbe64619c.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16384_none_4f7a847fa546ca5d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16420_none_4fb764c5a519ba82.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16451_none_4f97f54ba53127ac.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16518_none_4fca38e7a50a6670.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16676_none_4f875ab1a53cd88f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17170_none_4f8138afa5426863.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20521_none_504201dabe3673a3.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20555_none_5025933ebe4b2cd2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20623_none_50440454be34a378.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20784_none_500426fcbe64619c.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16384_none_4f7a847fa546ca5d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16420_none_4fb764c5a519ba82.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16451_none_4f97f54ba53127ac.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16518_none_4fca38e7a50a6670.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.16676_none_4f875ab1a53cd88f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17170_none_4f8138afa5426863.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20521_none_504201dabe3673a3.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20555_none_5025933ebe4b2cd2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20623_none_50440454be34a378.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_prnms003.inf_31bf3856ad364e35_6.2.9200.20784_none_500426fcbe64619c.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 28 datablocks.
Finish time: 2017-09-06 00:42:46.625
Script hash: QNXSJX9GAMpgaIn+kIJGLBoTK/7fpVfSUi2plYK3Nz0=
----------------------EOF-----------------------

I again ran Dism /Online /Cleanup-Image /Restorehealth with ProcMon running - this time instead of getting to 20% and failing with error 14005 - it advanced to 40% but then threw an error of 0x800f081f - Either the repair source was not found or the Component Store cannot be repaired. Here is a link to my Logfile.PML - https://netorg2466719-my.sharepoint...1c1818713f2e3&authkey=AT2bNTanxWihr4wfactF3Vk

CBS log is attached!

Sysnative Windows Update · Sep 6, 2017

SFC Scan

Click on the Start

button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

jwolber · Sep 7, 2017

SFC /SCANNOW has been ran. It said it found corrupt files but they were all repaired. I again ran DISM /online /cleanup-image /restore health with PROCMON running and it failed again with the same error. Here is the link to the logfile.pml - https://netorg2466719-my.sharepoint...d243e58b56d2c&authkey=AYExq_LaD74HCbqteoIOs1E

CBS file is attached. Thanks!

Sysnative Windows Update · Sep 7, 2017

Please attach:

C:\Windows\WindowsUpdate.log
C:\Windows\Logs\DISM\dism.log

jwolber · Sep 7, 2017

Here you go!

[SOLVED] [WinServer2012 x64] WU 80070246. DISM Error: 582 illegal character was encountered.

Inactive

Attachments

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments