If you service the image by using the /PreventPending argument despite the presence of pended content, the package is falsely reported as "installed" even though no installation operation is complete. At this point, the only way to confirm which servicing operations were successfully completed is to boot into the image. This lets you verify what is installed.
If the image has pended content, you may continue with offline servicing. However, you should not use the /PreventPending argument. If you want to use the /PreventPending argument anyway, you should take one of the following actions:
- Boot the image. (This results in the pended content being installed.) Then, recapture the image to continue servicing.
- Discard the image, and then start again by using a clean image.
If you use the /PreventPending argument against an offline image that has pended content, the only way to confirm which servicing operations were actually performed and completed is to boot into the system. After the image is online, you can use the /Get-Packages option and other DISM inventory commands to review what is installed in the image. Or, you can recapture the image and continue to service the image offline. Pended content will be cleared from the image after you boot the image and then recapture the image. Querying the servicing state without booting the image will produce incorrect and false results.
For more information about the DISM command-line options, go to the following Microsoft TechNet website:
Article ID: 2749510 - Last Review: 17 Oct 2012 - Revision: 1