locked
TsmBootstrap.exe: msvcp120.dll is missing from your computer RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    When windows7 starts for the first time (Phase = stateRestore), TSmBootstrap.exe gives the error: msvcp120.dll is missing from your computer. Actually, I do have "msvcp120.dll" in %deployroot%\Tools\x86\. But it does not copy to C:\MININT\Tools\X86. The same happens with x64 version OS.

    After I press "ok" in this error, deployment wizard finishes with error "Welcome wizard failed or was cancelled".

    Bdd.log says:

    SMS Task Sequencer found at F:\Deploy\Tools\X86, copying to C:\MININT\Tools\X86	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\CcmCore.dll to C:\MININT\Tools\X86\CcmCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\CcmUtilLib.dll to C:\MININT\Tools\X86\CcmUtilLib.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\Smsboot.exe to C:\MININT\Tools\X86\Smsboot.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\SmsCore.dll to C:\MININT\Tools\X86\SmsCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsCore.dll to C:\MININT\Tools\X86\TsCore.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TSEnv.exe to C:\MININT\Tools\X86\TSEnv.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsManager.exe to C:\MININT\Tools\X86\TsManager.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsmBootstrap.exe to C:\MININT\Tools\X86\TsmBootstrap.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsMessaging.dll to C:\MININT\Tools\X86\TsMessaging.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TsProgressUI.exe to C:\MININT\Tools\X86\TsProgressUI.exe	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\TSResNlc.dll to C:\MININT\Tools\X86\TSResNlc.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\xprslib.dll to C:\MININT\Tools\X86\xprslib.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Tools\X86\00000409\tsres.dll to C:\MININT\Tools\X86\00000409\tsres.dll	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying F:\Deploy\Control\2\TS.XML to C:\MININT\Tools\X86	LiteTouch	10/6/2015 3:01:06 PM	0 (0x0000)
Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X86\VARIABLES.DAT	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
RUN: regsvr32.exe /s "F:\Deploy\Tools\x86\Microsoft.BDD.Utility.dll"	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
RUN: regsvr32.exe /s "F:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
TargetOS is the current SystemDrive	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAContinue	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
Property LTIDirty is now = TRUE	LiteTouch	10/6/2015 3:01:07 PM	0 (0x0000)
Command completed, return code = -1073741515	LiteTouch	10/6/2015 3:29:36 PM	0 (0x0000)
Litetouch deployment failed, Return Code = -1073741515  0xC0000135	LiteTouch	10/6/2015 3:29:36 PM	0 (0x0000)

    Why it doesn't copy proper tools from %deployroot%\Tools\x86\?
    What can I do?

    Tuesday, October 6, 2015 9:39 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    You're running MDT 2013 Update 1, correct?

    This line from LiteTouch.wsf copies the files (which includes the files that you mention):

        For each sFile in Array("CcmCore.dll","CcmUtilLib.dll","Smsboot.exe","SmsCore.dll","TsCore.dll","TSEnv.exe","TsManager.exe","TsmBootstrap.exe","TsMessaging.dll","TsProgressUI.exe","TSResNlc.dll","msvcp120.dll","msvcr120.dll","CommonUtils.dll","ccmgencert.dll","00000409\tsres.dll")

    You can see the files in question there.  Have you updated your boot media (CD, PXE, USB) since upgrading?

    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    • Marked as answer by Ty Glander Wednesday, October 7, 2015 1:56 AM
    Tuesday, October 6, 2015 1:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Michael, you made everything clear.

    Yes, I am running MDT 2013 Update 1 (6.3.8298.1000)

    It worked recently after upgrading.

    The problem was that I messed up with default scripts. and I copied some scripts (including litetouch.wsf) from old deploymentshare with lower version.

    To get default scripts back, I created new deploymentShare with new name. All the scripts were generated in new DeploymentShare. Then I copied these scripts to my DeploymentShare.

    • Marked as answer by Ty Glander Wednesday, October 7, 2015 1:56 AM
    Wednesday, October 7, 2015 1:38 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    You're running MDT 2013 Update 1, correct?

    This line from LiteTouch.wsf copies the files (which includes the files that you mention):

        For each sFile in Array("CcmCore.dll","CcmUtilLib.dll","Smsboot.exe","SmsCore.dll","TsCore.dll","TSEnv.exe","TsManager.exe","TsmBootstrap.exe","TsMessaging.dll","TsProgressUI.exe","TSResNlc.dll","msvcp120.dll","msvcr120.dll","CommonUtils.dll","ccmgencert.dll","00000409\tsres.dll")

    You can see the files in question there.  Have you updated your boot media (CD, PXE, USB) since upgrading?

    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    • Marked as answer by Ty Glander Wednesday, October 7, 2015 1:56 AM
    Tuesday, October 6, 2015 1:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Michael, you made everything clear.

    Yes, I am running MDT 2013 Update 1 (6.3.8298.1000)

    It worked recently after upgrading.

    The problem was that I messed up with default scripts. and I copied some scripts (including litetouch.wsf) from old deploymentshare with lower version.

    To get default scripts back, I created new deploymentShare with new name. All the scripts were generated in new DeploymentShare. Then I copied these scripts to my DeploymentShare.

    • Marked as answer by Ty Glander Wednesday, October 7, 2015 1:56 AM
    Wednesday, October 7, 2015 1:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same problem but don't understand what I need to do?  Can you help?

    Thank you,

    Mike

    Monday, October 12, 2020 1:30 AM