jptheripper
Active member
- Dec 6, 2022
- 37
new ones just in case
[SOLVED] Server 2019 Essentials (Domain Controller) component store corruption
- Thread starter jptheripper
- Start date
Hi,
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
- Save any work you have open, and close all programs.
- Download the attachment SFCFix.zip and save it to your desktop.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Post the logfile (SFCFix.txt) as attachment in your next reply.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthjptheripper
Active member
- Dec 6, 2022
- 37
Microsoft Windows [Version 10.0.17763.3287]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1697
Image Version: 10.0.17763.3287
[==================== 35.2% ]
Error: 2
The system cannot find the file specified.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>
I do have the install iso, i could run dism with local files? although i never had success with trying that before
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1697
Image Version: 10.0.17763.3287
[==================== 35.2% ]
Error: 2
The system cannot find the file specified.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>
I do have the install iso, i could run dism with local files? although i never had success with trying that before
The ISO will not be helpful in this case, please post the latest CBS log(s) instead of the DISM log.
jptheripper
Active member
- Dec 6, 2022
- 37
thank you again
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
- Save any work you have open, and close all programs.
- Download the attachment SFCFix.zip and save it to your desktop.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Post the logfile (SFCFix.txt) as attachment in your next reply.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthjptheripper
Active member
- Dec 6, 2022
- 37
Microsoft Windows [Version 10.0.17763.3287]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1697
Image Version: 10.0.17763.3287
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>
AMAZING!!
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1697
Image Version: 10.0.17763.3287
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>
AMAZING!!
Great, please attempt to update. If it fails attach a new copy of the CBS log(s).
jptheripper
Active member
- Dec 6, 2022
- 37
First attempt at install caused a crash/reboot (Install of pending update)
Second attempt rechecked/redownloaded. Got to 100% and required reboot
Rebooted, update applied successfully
Successfully installed on 12/21/2022
System reboots Windows is up to date!!
You are amazing, thank you. Do donations go directly to you?
Are we done? or is there more to check
Second attempt rechecked/redownloaded. Got to 100% and required reboot
Rebooted, update applied successfully
Successfully installed on 12/21/2022
System reboots Windows is up to date!!
You are amazing, thank you. Do donations go directly to you?
Are we done? or is there more to check
Glad to hear the update(s) installed succesfully. If everything is up and running, then we are done...
For more information on how donations are spent I refer to one of the admins. @Will Watts
No, all of the donations are for Sysnative to host this forum, so we can provide this service as volunteers and researchers. As wel as in the future with other cases...
For more information on how donations are spent I refer to one of the admins. @Will Watts
jptheripper
Active member
- Dec 6, 2022
- 37
I ran sfc (which I was never able to run before)
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\WINDOWS\system32>
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\WINDOWS\system32>
Please run the System File Checker again, and let me know the result...
jptheripper
Active member
- Dec 6, 2022
- 37
Running a second time showed no errors. And Windows update seems to still be fine, should i run DISM with check health
jptheripper
Active member
- Dec 6, 2022
- 37
C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
[===========================94.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 Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
[===========================94.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 Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
jptheripper
Active member
- Dec 6, 2022
- 37
I hope i didnt do anything wrong and cause you more effort. the only thing i did was run sfc twice (as stated), run windows update (on windows defender update), and then run DISM (which now wont complete). Is it possible that sfc "fixing" the file broke something in DISM?
sorry if i am naïve, this is new to me.
sorry if i am naïve, this is new to me.
It seems the /CheckHealth parameter triggered some other issues. Let's repair them as well.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
- Save any work you have open, and close all programs.
- Download the attachment SFCFix.zip and save it to your desktop.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Post the logfile (SFCFix.txt) as attachment in your next reply.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthjptheripper
Active member
- Dec 6, 2022
- 37
I apologize, i thought checkhealth was read only, i wont be running that again
C:\WINDOWS\system32>dism /online /cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>sfc /scannow
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.
C:\WINDOWS\system32>dism /online /cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406
Image Version: 10.0.17763.3770
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>sfc /scannow
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.
Hi,
There is no need to apologize, after the succeded updates, I did not expect any new corruptions.
Are there any further issues or is everything up and running?
There is no need to apologize, after the succeded updates, I did not expect any new corruptions.
Are there any further issues or is everything up and running?
jptheripper
Active member
- Dec 6, 2022
- 37
Windows running well. crash due to
The computer has rebooted from a bugcheck.
The bugcheck was: 0x0000001a (0x0000000000041790, 0xffffa2001783a0a0, 0x000000000000014a, 0x00000000000001fd).
A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 81ce44b6-0680-4c1c-9076-b86d9c2e9cd0.
I think that cuased corruption in first place, but i am replacing hardware
The computer has rebooted from a bugcheck.
The bugcheck was: 0x0000001a (0x0000000000041790, 0xffffa2001783a0a0, 0x000000000000014a, 0x00000000000001fd).
A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 81ce44b6-0680-4c1c-9076-b86d9c2e9cd0.
I think that cuased corruption in first place, but i am replacing hardware
Has Sysnative Forums helped you? Please consider donating to help us support the site!