[SOLVED] Windows 10 DISM.exe /online /Cleanup-Image /RestoreHealth Error:582

Do you know what the /ResetBase command is used for?
 
https://technet.microsoft.com/en-us/library/dn251565.aspx

Using the /ResetBase switch with the /StartComponentCleanup parameter of DISM.exe on a running version of Windows 8.1 removes all superseded versions of every component in the component store.
From an elevated command prompt, type the following:
Copy

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase




All existing service packs and updates cannot be uninstalled after this command is completed. This will not block the uninstallation of future service packs or updates.

[TH="align: left"]
IC174466.gif
Warning [/TH]
 
Do you use it to reduce the size of your WinSxS folder? Because other than that, there's no reason at all to use this command. If anything, we do not recommend it here as it cripples us when comes the time to troubleshoot Windows Update issues if we cannot uninstall them.
 
Yes, I do use it to reduce the size of my WinSys folder. I try to clear out as much of the old unused Windows components as much as possible and prevent "update cruft" from building up. I guess it's just another way for me to prevent needing to do a clean install of the OS, since that would entail having to reinstall and reconfigure every single program I currently use, which is a pain.

tl;dr ver. - Yes because clean installing Windows is a pain.
 
There's still no need to do that if you ask me. Even if you do use that command, you are still subject to Windows Update issues :) Also, the last step in solving Windows Update issues is a Repair Install and you lose practically nothing from it. I've successfully assisted users in over 250 threads now, all related to Windows Updates, and not a single time did I see that issue come up (or see them using /ResetBase). But maybe that's just me :P
 
No there's no need to right now :P Is it the first time that you used the /ResetBase command? When was the last time you used it?
 
I've used the /ResetBase just about a few weeks ago before the newest update that didn't include the usual Windows Defender Definitions. Maybe around Jan 2 I suppose?
 
Maybe it's throwing an error because there's nothing to Reset right now? We could wait until the next Patch Tuesday (which should be tomorrow) and once the updates are installed, you could try it again (even though my advice would be to never use that command again).
 
I see I see.

Since /ResetBase is such a problematic command, what other solutions would you recommend to shrink the WinSys directory, or at least remove the buildup of old components not being used? I've rellied on the Windows CleanUp utility for the longest time, but it doesn't always remove a lot of temporary or old files after a major update.
 
Like I said, I have no idea of why you would want to do that. The WinSxS folder isn't that big if you ask me. If you have a normally-sized SSD or HDD, you'll be just fine. Plus, you're really crippling yourself by doing that. If you encounter Windows Update issues in the future which requires you to uninstall updates as part of the troubleshooting process (and it happens often), you'll be in a dead-end, forcing you to do a Repair Install. One folder that can grow in size for nothing (if it cannot be emptied) is the C:\Windows\SoftwareDistribution\Download folder, you can freely delete everything in it after installing the Windows Updates if you want.
 
Thanks. I'll try and see after tomorrows patch if it work. Yeah, I've also been trying to empty the C:\Windows\SoftwareDistribution\Download folder too after every update, as I've heard that this folder too can get bloated after big patches.
 
No problem, let me know how it goes :)
 
The update just came out. Applied it and here are the results:
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

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

Error: 1

Incorrect function.

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

C:\WINDOWS\system32>

It's still giving me the error even after the update.
 
Send me both the DISM.log and CBS.log so I can check them please.
 
https://www.dropbox.com/s/t55eklc2tj1rjzc/DISM.zip?dl=0
https://www.dropbox.com/s/6gpmugwafhiqcf5/CBS.zip?dl=0

Code:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-12 15:37:19.158
Microsoft Windows 8.1  - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-01-12 15:47:00.618
----------------------EOF-----------------------
 
Here's the error you are getting:
Code:
2016-01-12 15:36:10, Info                  CBS    Maint: processing complete.  Session: 30494071_2223028086. [HRESULT = 0x80070001 - ERROR_INVALID_FUNCTION]
[b]2016-01-12 15:36:10, Error                 CBS    Session: 30494071_2223028086 failed to perform Synchronous Cleanup operation [HRESULT = 0x80070001 - ERROR_INVALID_FUNCTION][/b]
2016-01-12 15:36:10, Info                  CBS    Session: 30494071_2223028086 finalized. Reboot required: no [HRESULT = 0x80070001 - ERROR_INVALID_FUNCTION]
2016-01-12 15:36:10, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x80070001]
I cannot tell if this is related to Windows 10 or not. Personally, I would have to create a Windows 10 VM, fully update it and then use the /ResetBase command to see if it works or not. Apparently, that command wasn't working at one point under Windows 8.1 and Microsoft released a fix to issue it, so it could be the same under Windows 10.
 
I see. So should I just wait for the next Windows Update to hopefully address it?
 
I'll be creating a Windows 10 VM sometime this week. Once done, I'll update it then test the command to see if it works or not and I'll let you know.
 
Back
Top