Cuando se instala el software en la parte de la instalación del paquete redistribuible de microsoft visual c++ 2005 da un error 


En principio parece que el problema viene por el servicio Trustedinstalling que no se ha iniciado, asi que vamos a services.msc y buscamos el servicio "Instalador de Modulos de Windows"

en las propiedades, (doble click) vemos que esta parado y si le damos a iniciar sale este error:

Vamos a seguir el procedimiento de reparación de este KB de microsoft :

Solución KB (adjunta en pdf)

  • Revisamos que la clave de registro del Kb existe y miramos el numero de versión en la carpeta Windows\Servicing\Version , despues buscamos en Windows\Winsxs paquetes con la cadena siguiente (si es x86, la correspondiente a x86) amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f
  • Copiamos el nombre de esta carpeta y lo usamos en la parte nueva de creación de la clave corrupta (siguiendo las instrucciones del KB) y ya podremos iniciar el servicio.
  • Observaremos que de repente las actualizaciones de windows ya funcionan, así que actualizaremos el windows a topel primero.
  • Reiniciamos para que se apliquen todas las actualizaciones bien.
  • Volvemos a realizar la instalación del software de Carestream (el VC++ redist. 2005 ya lo pasa como instalado)


Se abre el software, se comprueba que todo funciona, se introduce el código de licencia y listo.


Fin de la solución.


KB usado de microsoft


Error message when you start the Windows Modules Installer service (TrustedInstaller): "System Error 126: The specific module could not be found"

Source: Microsoft Support


RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.


Symptoms


When you start the Windows Modules Installer service, you receive the following error message:



You also receive an error message at the command prompt:




Cause


This issue occurs if the following registry subkey was changed:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version 


Resolution


To resolve this issue, you have to re-create the expandable string value of the registry subkey that is mentioned in the "Cause" section.

First, you have to check whether the registry subkey exists. To do this, start Registry Editor, and then browse to the subkey that is mentioned in the "Cause" section. If the subkey does not exist, you must create it. To do this, follow these steps: 
  1. Locate the C:\Windows\Servicing\Version directory, and note the name of the subfolder in this directory. It will be named something like "6.1.7600.16385." This is your TrustedInstaller ID. 
  2. Copy the subfolder name to the clipboard, and then paste it into Notepad for safekeeping.



    Note In this example, the TrustedInstaller ID is 6.1.7601.17592.
  3. In the C:\Windows\WinSxS directory, find a subfolder whose name begins with one of the following strings. (In the following subfolder names, the placeholderTrustedInstaller ID represents your TrustedInstaller ID.)

    For 32-bit Windows

    x86_microsoft-windows-servicingstack_31bf3856ad364e35_TrustedInstaller ID_none

    For 64-bit Windows

    amd64_microsoft-windows-servicingstack_31bf3856ad364e35_TrustedInstaller ID_none

  4. Copy the subfolder name to the clipboard, and then paste it into Notepad for safekeeping.



  5. Create the following registry subkey:

    HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version 

    Note To create this key, you have to be an owner of the "Component Based Servicing" key. Then, you have to then give yourself full access permissions.
  6. On the Version key that you created in step 5, create an expandable string value (or edit it if it already exists). To do this, use the TrustedInstaller ID as your name, and use the full path of the folder that you identified in step 3 as the value.

    Note In the full path, you must use %SystemRoot%\WinSxS\folder_name instead of C:\Windows\WinSxS\ folder_name.


  7. Click OK, and then exit Registry Editor.
You can now start the Windows Modules Installer (TrustedInstaller) service as usual.


DISCLAIMER


MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.


Properties


Article ID: 959077 - Last Review: Jul 18, 2014 - Revision: 1

Applies to

Windows 7 Enterprise, Windows 7 Home Basic, Windows 7 Home Premium, Windows 7 Professional, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 for Windows Essential Server Solutions, Windows Server 2008 for Windows Essential Server Solutions without Hyper-V, Windows Server 2008 Foundation, Windows Server 2008 Service Pack 2, Windows Server 2008 Standard, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Datacenter without Hyper-V, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 for Embedded Systems, Windows Server 2008 R2 for Itanium-Based Systems, Windows Server 2008 R2 Foundation, Windows Server 2008 R2 Service Pack 1, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Standard without Hyper-V


-------------------------------------------------FIN DEL ARTICULO----------------------------------------------------------------------------------------------