I have had this issue at a customer. We could not find out why the deployment stopped at various times. We did not find any pattern at all. The Advertisement status reported this error messages:
The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942977
Action output: *********SMSPKGD$***00114 before releasing
Released the resolved source ********.*****.******SMSPKGD$***00114InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia ), HRESULT=80070241 (e:nts_sms_fresmsclientosdeploymentapplyosapplyos.cpp,373)
WIM error:C:Program Files*************.***
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows)
Unable to apply (0×80070241)
Installation of image 1 in package ***00114 failed to complete..
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows). The operating system reported error 2147942977: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
And also this message:
The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147942977: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
I then started investigating the servers event logs. I found the following event in the application log when this happened: 
It turned out that the SCCM was installed on a x86 server and therefore SQL could not get enough ram to do its thing. Therefore when we deployed a machine the deployment was interrupted, because the server was forced to unload due to memory pressure.
So a solution is to move the installation to a X64 server with X64 version of SQL to get more memory. Or tune your current setup.
UPDATE: I have also seen this error if you are trying to deploy while the OS image is being distributed to another distribution point. (Install pending)
Newest Comments