New
#750
Can anyone tell me the reason for that error: 6824 (below) when I run: "dism.exe /Online /Cleanup-Image /StartComponentCleanup"
I remember @CountMike answering to a post with someone with similar issue that his "Graphics were too slow". That was the first thing I did by downloading NVIDIA GeForce Experience which has updated my Display Adapter to the latest version. After that, I re-ran: "dism.exe /Online /Cleanup-Image /StartComponentCleanup" again and I still got the same error message.
That's the only issue I am facing with one of my machines (HP Envy). Any help would be greatly appreciated!
Last edited by IronZorg89; 10 Dec 2018 at 18:49.
Any info in the dism.log file?
Edit: I just tried it and I get the same error message. Something to do with the latest 1809 CU as it wasn't there prior to installing it.
Edit#2: I ran all the usual commands from inside a batch file:
>dismandsfc.bat
Mon 12/10/2018
04:58 PM
Dism /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.168
[===== 9.8% ]
[================ 28.6% ]
Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
...
Mon 12/10/2018
05:00 PM
Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.168
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
...
Mon 12/10/2018
05:01 PM
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.
Mon 12/10/2018
05:07 PM
Only StartComponentCleanup failed, the other two worked correctly.
I didn't see anything useful in the dism.log file.
You had exactly the same reaction as I did, i.e, running: sfc /scannow; Dism.exe /online /Cleanup-Image /restorehealth. No problem there either with both. I even went for a repair install in the hope that the issue would be fixed. No dice, instead after the in-place upgrade, I had to face quite another issue with Microsoft Edge which wouldn't launch no matter what: Repair, Reset and even those command lines in PowerShell:
Get-AppXPackage -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}
Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}
I had to roll back with a MR system image backup. I am glad in a way that I am not the only one facing this problem, meaning it is intrinsic somehow to the latest CU
I ran it in Safe Mode and it ran fine, no problems, no need to go back to a previous version. I wouldn't for that error anyway since everything else has been working fine for me since Oct 2nd.
Mon 12/10/2018
05:30 PM
Dism /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.168
[==========================100.0%==========================]
The operation completed successfully.
...
Mon 12/10/2018
05:47 PM
I did notice that Shift/Restart no longer works to get to Safe Mode. I used SafeModeCommandPrompt.vbs from WinAeroTweaker to add Safe Mode to the Desktop Context Menu. That still works great. When done, right click and select Exit Safe mode to return to normal mode.
Can't enter feedback, getting connecting problems:
![]()
Shift+Restart gets me to the Advanced Startup options, from where Trouibleshoot > Advanced options > Startup Settings lets me get to Safe Mode. This is the same for my 1809 17763.168 as on my 1803 17134.441.
Boot to Advanced Startup Options in Windows 10 | Tutorials
My Feedback Hub works in 1809 too.
So does Dism /Online /Cleanup-Image /StartComponentCleanup without using safe mode.
![]()