Forum Discussion
DISM Headache
It started out as a mission to update my secure boot certificates. I made some progress using powershell and got the certificates onto my windows install, but they didnt get written to the firmware. I tried various online suggestions from AI and one led me down the path to run DISM. I ran DISM online for 3.5 hours. I tailed the cbs log to verify the tool was still working. After spending 3.5 hours the tool finished and reported 1632 errors of which it repaired zero. The complaint was it “looked everywhere but couldn’t find the necessary content”. My internet connection was good. If DISM cant get content from MS servers what good is the online switch. Suggestion say to mount the OS image and point to that when i restart DISM. I dont have the image for 24h2 and the specific build number. Furthermore Windows Update has not offered 25H2 to me yet. So disappointing. If DISM cant talk to MS servers tell me that in the first 5 minutes. Not after 3.5 hours.
2 Replies
Your suggestion makes a lot of sense: DISM should provide early, clear feedback if it can't reach Microsoft servers or retrieve the required files. Waiting hours for a failed process isn't ideal, especially when the root cause could be identified much sooner.
DISM online relies on Windows Update or the Microsoft Servicing stack to fetch necessary files.
If DISM can't contact MS servers, it won't be able to repair or mount images, and this should ideally be reported early.
Running for hours without clear failure messages wastes time and causes confusion.
