[SOLVED] Windows 10 - Error 0x80070246; DISM Error 582; SFC doesn't work

R

r2ots

Contributor
Joined
Jun 18, 2019
Posts
11
Hello Sysnative !

I am looking for some help as I have no idea on how to fix the following issues:

1. Windows Update doesn't work anymore and returns the following error: 0x80070246, while trying to install the following update: KB4503327

2. Command "Dism /Online /Cleanup-Image /RestoreHealth" returns the following message:

Code: 
Deployment Image Servicing and Management tool

Version: 10.0.17763.1

Image Version: 10.0.17763.503

[==                         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

3. Command "sfc /scannow" returns:

Code: 
Windows Resource Protection could not perform the requested operation.


--> So as advised on the forum, I tried to run SFCfix but it did not work. DISM returned an error 582 (see attached screenshot and log file. Sorry for the french language in the screenshot. The text is similar to the one posted at point 2.) I also joined my CBS and DISM logfile.

For information I already tried to reset Windows 10 but I did not work. Thus I have no idea on what to do next, and any help would be greatly appreciated!

Many thanks.
 

Attachments

Hello,

Thank you for your answer. The test ended with no errors. Please see the attached log file.
 

Attachments

Hi!

Please 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. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as the it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.
 
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 the attached fixlist.txt 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.
 

Attachments

Hello,

Here is the content of the fixlog file. Some of it is in french so please tell me if you need any translation.

Thank you !

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 30-06-2019
Exécuté par Mathieu (02-07-2019 07:22:55) Run:1
Exécuté depuis C:\Users\Mathieu\Desktop\sysnative\Farbar
Profils chargés: Mathieu (Profils disponibles: Mathieu)
Mode d'amorçage: Normal
==============================================

fixlist contenu:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
CreateRestorePoint:
[-HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..onal-keyboard-kbdbr_31bf3856ad364e35_10.0.17763.1_none_6715cd97721e9106]

*****************


========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========

L'op‚ration a r‚ussi.


========= Fin de CMD: =========

Le Point de restauration a été créé avec succès.
HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..onal-keyboard-kbdbr_31bf3856ad364e35_10.0.17763.1_none_6715cd97721e9106 => supprimé(es) avec succès

==== Fin de Fixlog 07:23:32 ====
Click to expand...
 
Hi!

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 the attached fixlist.txt 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.
 

Attachments

Hi,

Here is the log:

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 3-07-2019
Exécuté par Mathieu (05-07-2019 07:14:46) Run:2
Exécuté depuis C:\Users\Mathieu\Desktop\sysnative\FRST2
Profils chargés: Mathieu (Profils disponibles: Mathieu)
Mode d'amorçage: Normal
==============================================

fixlist contenu:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
CreateRestorePoint:
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..onal-keyboard-kbdcr_31bf3856ad364e35_10.0.17763.1_none_678754c571d5958d]
"S256H"=hex:e8,16,9e,3f,74,8f,d8,71,49,f7,0d,56,78,f1,78,ae,90,3a,c8,42,6e,e8,\
59,fe,92,71,6c,68,33,a6,61,2e
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,49,6e,74,\
65,72,6e,61,74,69,6f,6e,61,6c,2d,4b,65,79,62,6f,61,72,64,2d,4b,42,44,43,52,\
2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,61,6c,2c,20,56,65,72,73,69,6f,\
6e,3d,31,30,2e,30,2e,31,37,37,36,33,2e,31,2c,20,50,75,62,6c,69,63,4b,65,79,\
54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,\
72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,\
34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"c!microsoft-w..-deployment_31bf3856ad364e35_10.0.17763.1_aed55bf4d2e1818d"=hex:
"f!kbdcr.dll"=dword:00000001
EndRegedit:
*****************


========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========

L'op‚ration a r‚ussi.


========= Fin de CMD: =========

Le Point de restauration a été créé avec succès.
Registre ====> L'op�ration a r�ussi.


==== Fin de Fixlog 07:15:17 ====
Click to expand...
 
Hello,

Evrything seems to be working now! Windows Update is working as well as the commande sfc/ SCANNOW, which I runned and reported no errors. Many thanks for your help !

Do you think there is anything else I should do now ?
 
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