Add DISM and SFC commands to the script?

[macnaughtani]

Hello. Please let me know if this is not the appropriate channel for this.

Thank you for this script. It is working great (although I've not been able to get it working from Intune yet - another story). I've found at least a couple of times that after the W11 upgrade fails, I've run DISM and SFC commands (see below), kicked off the script again and the W11 upgrade succeeds. Could these be incorporated into the script or is that a bad idea?

I can see that DISM is used in the script but I think for different purposes. I can also probably figure out how to incorporate it myself but my PowerShell is clearly not at the same level as yours so thought I'd ask here first.

These are the commands I ran after first W11 upgrade was not successful:

DISM.exe /Online /Cleanup-image /Restorehealth

Followed by:

sfc /scannow

In at least one case, SFC reported some corrupt files that it fixed. Unfortunately, I can't be sure which, both or even if these commands helped the second upgrade attempt to be successful. And we don't have a big sample yet so maybe I was just lucky on the second attempts. In any case, I figured no harm in asking.

Thanks.

[pjm-powerstacks]

This would be pretty easy. Would you want it to always run before the upgrade starts?Sent from my iPhone, please excuse the typosOn Jul 28, 2025, at 7:24 PM, Ian ***@***.***> wrote:macnaughtani created an issue (powerstacks-corp/UpgradeWindows#8) Hello. Please let me know if this is not the appropriate channel for this. Thank you for this script. It is working great (although I've not been able to get it working from Intune yet - another story). I've found at least a couple of times that after the W11 upgrade fails, I've run DISM and SFC commands (see below), kicked off the script again and the W11 upgrade succeeds. Could these be incorporated into the script or is that a bad idea? I can see that DISM is used in the script but I think for different purposes. I can also probably figure out how to incorporate it myself but my PowerShell is clearly not at the same level as yours so thought I'd ask here first. These are the commands I ran after first W11 upgrade was not successful: DISM.exe /Online /Cleanup-image /Restorehealth Followed by: sfc /scannow In at least one case, SFC reported some corrupt files that it fixed. Unfortunately, I can't be sure which, both or even if these commands helped the second upgrade attempt to be successful. And we don't have a big sample yet so maybe I was just lucky on the second attempts. In any case, I figured no harm in asking. Thanks. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[macnaughtani]

Thanks for reply. I don't think there are any major issues with running it every time before the upgrade. And if it helps make the first upgrade succeed without risks of causing other issues, then that would certainly save time. But we're a bit new at trying to automate the upgrade so I may not be aware of an issue with running those commands before the upgrade.

In the past, we've mostly done the upgrade manually and when we strike a failed upgrade like this, we've tended to go all nuclear and wipe, re-install OS and apps instead of troubleshooting why the upgrade is failing!

[pjm-powerstacks]

I can add it into the clean up anctions and add a parameter to enable/disable it. That’s super easy. On Jul 29, 2025, at 6:53 PM, Ian ***@***.***> wrote:macnaughtani left a comment (powerstacks-corp/UpgradeWindows#8) Thanks for reply. I don't think there are any major issues with running it every time before the upgrade. And if it helps make the first upgrade succeed without risks of causing other issues, then that would certainly save time. But we're a bit new at trying to automate the upgrade so I may not be aware of an issue with running those commands before the upgrade. In the past, we've mostly done the upgrade manually and when we strike a failed upgrade like this, we've tended to go all nuclear and wipe, re-install OS and apps instead of troubleshooting why the upgrade is failing! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[macnaughtani]

Thanks and sorry for long delay in responding. That sounds great. Will keep my eye out for it.