Windows Server 2012 Windows Update Error 80070246 + DISM Error 582 illegal character

More repairs incoming:
Step 1 - Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

Dropbox - COMPONENTS.zip

Step 2 - DISM /RestoreHealth Scan



  1. Right-click on the Start 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
 
Well, this time it was a different error. No sure if that's good or bad...

Here is the output.



C:\Windows\System32>Dism /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384


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


Error: 14098


The component store has been corrupted.


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


C:\Windows\System32>

And here are the CBS logs

https://providencecomputers-my.shar...BGjjO3-zUs__YBKvBaSKncTfoB44Hbct2f_A?e=MIxTh9
 
Thank you. Can you do this again with ProcMon and then provide that + a fresh COMPONENTS copy.

I've cleared out all the obvious ones, now I have to take care of a few more and see what happens.

Also, please try checking for updates.
 
Thanks for all your help! I appreciate it. I'll be with family most of the day tomorrow as it is Independence Day (I'm in the US), so I'll be on for maybe another hour tonight, and then won't be able to check back till tomorrow night.

thanks!
 
Step 1 - Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

Dropbox - COMPONENTS.zip

Step 2 - DISM /RestoreHealth Scan




  1. Right-click on the Start 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
 
Hi, I received the same message this time in DISM and Check for Updates.

Here are the CBS logs

https://providencecomputers-my.sharepoint.com/:u:/g/personal/provcom_providence-computers_com/EbPaX5QXWIRLmlI8wkOz8v4BUOGue6iTp4GYzGpANM2Usw?e=dbY5KQ

Thanks!
 
I know it doesn't, I'm still dealing with corruption. :) They will fail after this too, but some corruption will be fixed.

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 and if any fail, attach CBS.log.
 

Attachments

Here is the FRST64 Log

Fix result of Farbar Recovery Scan Tool (x64) Version: 20.06.2018
Ran by administrator (05-07-2018 18:15:59) Run:5
Running from C:\Users\Administrator\Downloads
Loaded Profiles: administrator (Available Profiles: QBDataServiceUser25 & administrator)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_156bf12fda7e51ddba3af531e16f46e1_31bf3856ad364e35_6.2.9200.17422_none_15201fbf2d0add30]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1562032e4a9aafbd19d8e149bebcce0b_31bf3856ad364e35_6.2.9200.20521_none_62bff03a61e7ece5]


StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_156bf12fda7e51ddba3af531e16f46e1_31bf3856ad364e35_6.2.9200.17422_none_15201fbf2d0add30]
"S256H"=hex:78,99,e9,5f,f7,14,91,9f,8a,be,4d,12,cc,35,fa,9c,7e,0f,9b,56,05,1d,\
e7,83,4a,70,6a,6f,d4,02,43,53
"identity"=hex:31,35,36,62,66,31,32,66,64,61,37,65,35,31,64,64,62,61,33,61,66,\
35,33,31,65,31,36,66,34,36,65,31,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,36,2e,32,2e,39,32,30,30,2e,31,37,34,\
32,32,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
"CF"=dword:0000000c
"c!156bf12fda7..531e16f46e1_31bf3856ad364e35_6.2.9200.17422_15201fbf2d0add30"=hex:




[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1562032e4a9aafbd19d8e149bebcce0b_31bf3856ad364e35_6.2.9200.20521_none_62bff03a61e7ece5]
"S256H"=hex:c1,ce,27,fe,c9,ee,98,a8,c2,9c,a8,80,23,aa,11,29,da,67,f0,50,a0,01,\
1f,5e,18,e7,de,13,bb,7a,66,f3
"identity"=hex:31,35,36,32,30,33,32,65,34,61,39,61,61,66,62,64,31,39,64,38,65,\
31,34,39,62,65,62,63,63,65,30,62,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,36,2e,32,2e,39,32,30,30,2e,32,30,35,\
32,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
"CF"=dword:0000000c
"c!1562032e4a9..149bebcce0b_31bf3856ad364e35_6.2.9200.20521_62bff03a61e7ece5"=hex:




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


Error: (0) Failed to create a restore point.


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_156bf12fda7e51ddba3af531e16f46e1_31bf3856ad364e35_6.2.9200.17422_none_15201fbf2d0add30" => removed successfully
"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1562032e4a9aafbd19d8e149bebcce0b_31bf3856ad364e35_6.2.9200.20521_none_62bff03a61e7ece5" => removed successfully


====> Registry


==== End of Fixlog 18:16:00 ====
 
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