This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 99%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
Have two customers with SCCM 2107 with HF Rollup that can't update anymore the default SCCM boot images. The process starts and ends with several red ticks. Have clean up all the outdated drivers, but this doesnt makes a difference.
Have then examined dism.log and found a very strange behaviour. When updating the boot image in the SCCM admin console, dism.exe logs entries like the following:
2021-11-25 18:30:41, Info DISM DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /image:"C:\Windows\TEMP\BootImages{83D93D6A-1AF2-4D17-A693-04E95067E12A}\mount" /Add-Driver /Driver:"\srv-sccm01\CM_OSDeployment\DriverSources\Lenovo-WinPE-270\WIN10\64\rtux64w10.INF"
What I can't understand at all is where and why SCCM is adding the parameter "/add-driver..." to the dism.exe process. The Lenovo driver logged above is indeed outdated. Has anyone a hint or idea where SCCM is taken this information from, and how we can delete this?
Thanky you all in advance for any help.
Franz
Thank you for your proposal.
According our experience, it takes hours of phone calls and log collections when opening a Microsoft support case until they even start to looking at the problem (despite we are a MS Gold Partner).
What we have done is that we imported the x64 vanilla boot image from ADK and customized it in the SCCM Admin console identically like the non working boot image. This new boot image can be distributed and works fine.
What do you meen with "file feedback"? We have the following options in the Console:
If we can help locating bugs with a resonable effort, we certainly do that. But like I wrote before, the last time we have choosen this way, we had to spend far more than one day of work and haven't got any information or help from Microsoft for almost two months! We opened this support case because of the partially not working Software Center after the SCCM 2010 release at the end of October 2020. In Jaunuary 2021, Microsoft finally released the Hotfix Rollup that acknowledged and fixed the problem.
Send a frown, a smile or a suggestion depending on how you wish to characterize the feedback.
For your previous case, we can't and don't just instantly fix things necessarily -- that's not how software engineering works for a product as large as ConfigMgr. As noted, many issues are configuration or environmental in nature and we must investigate to evaluate and troubleshoot each issue individually to determine root cause and path to address. However, your experience sounds atypical as you 100% should have had an on-going conversation. If not, you can always escalate the case and work with your Microsoft account team to have your concerns addressed.