Anniversary and earlier updates fail with DISM error 582

shlondon

Member
Joined
Nov 6, 2016
Posts
5
Hi!
I ran the SFCFix, but this hardly produced any output, which is most likely due to the above error:
Code:
>dism /Online /Cleanup-Image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.10586.0

Abbildversion: 10.0.10586.0

[==========================100.0%==========================]

Fehler: 582

Ein unzulässiges Zeichen wurde gefunden. Bei einem Mehrbyte-Zeichensatz  schließt dies ein führendes Byte ohne nachfolgendes Byte ein. Beim  Unicode-Zeichensatz sind dies die Zeichen 0xFFFF und 0xFFFE.

Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".

Windows update reports this error indirectly as 0x80070246 illegal character too. It would be great to learn how I can recover from this error as I would really like to know what might have caused this.
Many thanks for looking into this.
Best regards,
Stefan
View attachment 23315
 
Hi there Stefan,

It appears that the attachment didn't work.

DISM /RestoreHealth Scan

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. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
Apologies, I lost track of your reply. I repeated thes suggested process and I keep getting the error message about a forbidden character, error number 582
The log files have been uploaded to:
https://1drv.ms/u/s!Ap5MxLrBr2TMmAPAMk8_AwlMmRW-
If you are still able to look into this you might also be interested in the other post where I already placed a copy of the component hive perhaps you can help me understand which bit of my registry is requiring some TLC:
https://www.sysnative.com/forums/wi...aracter-post173603.html?highlight=#post173603
Many thanks in advance!
Stefan
 
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 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 - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

DISM /RestoreHealth Scan

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. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
This time I got a different error about the source not being available...
Internet was up and running the whole time.
However I am glad that the illegal character is gone, although I needed to amend the registry entry manually to the provided binary value. Thanks a lot for the help so far. I am not sure if they will help but the logs are available at:
https://1drv.ms/u/s!Ap5MxLrBr2TMmATxMMGMRi-Gmkqf
Many thanks again!
Stefan
 
Very good.

Have you tested the memory in this system? There seem to be a number of keys missing their identities.

If you have already tested the memory, please try upgrading to the latest version of Windows 10 here: Windows 10

If the installation fails, zip and attach C:\Windows.~bt\Sources\Panther\SetupAct.log with your reply.
 
This is a relatively old installation in the sense that is was upgraded from win7 to win8 and now 10. I also use the intel z68 chipset's feature of an ssd, which might be adding to it. I will do some ram testing. Thanks again and I will let you know if anything wierd happens during the update.
 

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

Back
Top