[SOLVED] DISM Error 582; SFC doesn't work

[ayy]

Hello Sysnative,

this is my first time seeking help for computer-related stuffs for I can absolutely not pinpoint what the problem is this time nor how to fix it. Help would be highly appreciated :)

Dism /Online /Cleanup-Image /RestoreHealth

returns

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==                         4.5%                           ]
Error: 582

An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

sfc /scannow

returns

Windows Resource Protection could not perform the requested operation.

After having searched for a while, I assume that the following files are needed, thus here are the links:

COMPONENENTS file: Dropbox - COMPONENTS.zip
dism.log file: Dropbox - dism.zip

Thank you very much for the help and merry Christmas (or soon-to-be),
- ayy

 

[ayy]

EDIT: I forgot to include the following log: Dropbox - CBS.zip

 

[BrianDrab]

Hi and welcome to Sysnative. The only way to diagnose your error is to do the following.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run Dism /Online /Cleanup-Image /RestoreHealth just like you have in the past.
3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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.

 

[ayy]

Thank you for the quick reply!

LogFile -> Dropbox - Logfile.zip

CBS -> Dropbox - CBS.zip

 

[BrianDrab]

Thanks. That identified it. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
2. Download the file below, SFCScript.txt, and save this to your Desktop.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
5. Drag the file SFCScript.txt 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

 

[ayy]

Thank you for the quick reply, once again :)

Here's the result:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-27 22:34:01.363
Microsoft Windows 10 Build 14393 - amd64
Using .txt script file at C:\Users\chris\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.14393.0_none_abbad8648de9a324.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.14393.0_none_abbad8648de9a324.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.14393.0_none_abbad8648de9a324.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.14393.0_none_abbad8648de9a324 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.14393.0_none_abbad8648de9a324.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-12-27 22:34:01.814
Script hash: Q1B1cA3Bud6Q31/waLedvvp5hiyMfWfoF987f4sRdVk=
----------------------EOF-----------------------

I'm currently testing out if that fixed it, and so far so good as sfc /scannow currently works (I'm at 20% right now).
I'll attempt to run dism shortly after and update you with the results

 

[ayy]

Here are the results of the commands I was initially seeking help with:

sfc /scannow

Runs successfully and returns

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Dism /Online /Cleanup-Image /StartComponentCleanup

Runs successfully and returns

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================]
The operation completed successfully.

But unfortunately, another error is showing up with RestoreHealth:

Dism /Online /Cleanup-Image /RestoreHealth

Returns

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

Weirdly enough, running that same using command but using a mounted image gives me the same result:

Dism /Online /Cleanup-Image /RestoreHealth /Source:J:\sources\install.wim /LimitAccess

returns

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[===========================93.3%======================    ]
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

 

[BrianDrab]

I'll need your CBS.log to identify the culprit.

 

[ayy]

Oh, sorry about that!

Here's the CSB log: Dropbox - CBS_2.zip

 

[BrianDrab]

This should fix you up.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
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

 

[ayy]

Below is the result

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-28 14:21:28.547
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\chris\Desktop\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.0_none_f0bc8f87e59a3022
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.14393.0_en-us_d0169eb8b2387c9c

Successfully copied file C:\Users\chris\AppData\Local\niemiro\Archive\Winsxs\wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.0_none_f0bc8f87e59a3022\win32k.sys to C:\WINDOWS\Winsxs\wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.0_none_f0bc8f87e59a3022\win32k.sys.
Successfully copied file C:\Users\chris\AppData\Local\niemiro\Archive\Winsxs\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.14393.0_en-us_d0169eb8b2387c9c\WWAHost.exe.mui to C:\WINDOWS\Winsxs\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.14393.0_en-us_d0169eb8b2387c9c\WWAHost.exe.mui.

Successfully restored ownership for C:\WINDOWS\Winsxs\wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.0_none_f0bc8f87e59a3022
Successfully restored permissions on C:\WINDOWS\Winsxs\wow64_microsoft-windows-win32k_31bf3856ad364e35_10.0.14393.0_none_f0bc8f87e59a3022
Successfully restored ownership for C:\WINDOWS\Winsxs\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.14393.0_en-us_d0169eb8b2387c9c
Successfully restored permissions on C:\WINDOWS\Winsxs\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.14393.0_en-us_d0169eb8b2387c9c
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-12-28 14:21:29.063
Script hash: LFpnGBhYIf5UHD0ECI+tTtX0fzdio+1IJXd5ObWMPIY=
----------------------EOF-----------------------

I'd just like to thank you for all the time you're sparing in order to help me, it is very appreciated.

One more thing, I'm not sure if this is really worth mentionning though.
Running

Dism /Online /Cleanup-Image /RestoreHealth

will fail on the first try and return this

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==                         4.5%                           ]
Error: 1726

The remote procedure call failed.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

But running the same command again right after will return this:

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Quite frankly, I don't think this is really an issue, but the fact that there is no new line after the percentage level ([==...=100.0==...=]) coupled with the fact that the first attempt always fails does intrigue me a little bit ands leads me to believe that there may still be a problem.
Should I be worried as this might escalate into another problem in the future, or should I simply ignore it?

In case it might lead to a problem, here's the CBS.log generated after I ran the command twice in a row, one which resulted in an error and one which completed successfully: Dropbox - CBS_3.zip

Thank you again,
- Ayy

 

[BrianDrab]

Quite frankly, I don't think this is really an issue, but the fact that there is no new line after the percentage level ([==...=100.0==...=]) coupled with the fact that the first attempt always fails does intrigue me a little bit ands leads me to believe that there may still be a problem.
Should I be worried as this might escalate into another problem in the future, or should I simply ignore it?

I personally think you can ignore this if it works the second time without error. It's likley trying to start a service and isn't starting fast enough the first time through. If you have an issue in the future, feel free to come back. Take care.