En mettant à jour un serveur dédié Windows Server 2003 Standard Edition, via le Windows Update classique, le service d’installation d’updates s’est arrété brutalement lors du SP1 de .Net Framework 3.0. Le SP1 du .Net Framework 2.0 s’était bien déroulé, à la ligne précédente.

Il s’avère que c’est un problème qui est lié au fait que le Print Spooler n’est pas démarré. On ne rigole pas dans les rangs.

“There is an issue in the XPS component that is a prerequisite for the .NET Framework 3.0, 3.0 SP1 and 3.5 that can cause each of these versions of the .NET Framework to fail to install on Windows XP and Windows Server 2003.  The XPS component can fail to install correctly if the Print Spooler service is not running on the system, and that in turn will cause the .NET Framework 3.0 or 3.5 setup to fail.  In most cases of this error that we've seen so far, an Visual C++ runtime error dialog appears during .NET Framework 3.0, 3.0 SP1 or 3.5 setup with the following text on it:

The application has requested the Runtime to terminate it in an unusual way.

This error usually occurs while the PrintFilterPipelineSvc.exe process is being run during the installation of the XPS component that is a prerequisite for the .NET Framework 3.0, 3.0 SP1 and 3.5 on Windows XP and Windows Server 2003 operating systems.  We have not yet heard of a case of this particular error affecting Windows Vista or later operating systems because the necessary XPS components are already present as a part of the OS, and therefore .NET Framework setup does not need to run PrintFilterPipelineSvc.exe.”

Source: ce post sur le blog (MSDN) d’Aaron Stebner.