You are using DISM to offline inject a hotfix into a WIM image, or directly into an offline image. The hotfix services boot files which reside on the EFI system partition such as bootmgrfw.efi. In this scenario, DISM reports that the fix has been successfully injected into the image, however, the boot files are not actually updated on the EFI system partition.
In the case where Setup is used to deploy, the EFI boot files will be updated by Setup. In the case where a generalized image which has had a hotfix which services the boot files injected into it offline is applied using tools such as DISM or another imaging tool, Setup will update the boot files after the first boot, (and therefore may still encounter any issues addressed by the hotfix on the first boot). In the case where a hotfix which services the boot files is applied offline to a fully deployed system with an existing EFI system partition, the boot files will not be updated until the hotfix is installed online or the specific binaries serviced by the hotfix are superseded by Windows Update or a later hotfix installed online.
- You must inject the hotfix into the install.wim (on all image indexes) prior to running Setup.exe in order to have Setup properly deploy the updated boot files.
- You may manually extract the boot files from the hotfix and manually copy them into place on the EFI partition.
- You may apply the hotfixes online, for example during Audit mode. Online installation will successfully locate and service the EFI boot files.
Known hotfixes which require this workaround in offline injection scenarios at the time of writing this article. This list is subject to change:
Known files which typically reside on the EFI boot partition which will be affected at the time of writing this article. This list is subject to change: