none
Need to install Visual C++ 2010 in MDT before performance testing. RRS feed

  • Question

  • Hi all,

    I'm in a situation in which I'm deploying a laptop over MDT, and the display driver is captured by MDT fine. However, upon initial boot after installing the OS, I come across this error when running WINSAT.exe; "The program can't start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix the problem." This isn't the first report I've seen of ATI drivers triggering this, but I'm stuck with it regardless.

    This is attributed to a component of Visual C++ 2010 not being installed. (It's not preinstalled in our capture, and I'm trying to avoid having to do that again.)

    Being that we're a 0-touch organization when imaging, I need a way to remedy this. I'm currently trying to run the install, 'vcredist_x86.exe /q:a'   from "run a command line" (sourced on the server's C:\ drive) before the performance tests, but I can't find a proper place to put this command at in the task sequence. Is this even a viable method? Is there a method to skip WINSAT.exe pre-boot? My initial tests with this aren't working.

    Any advice or pointers appreciated! 


    • Edited by jdoiwpcs Tuesday, January 21, 2014 5:27 PM
    Tuesday, January 21, 2014 5:16 PM

Answers

  • Thanks for the msi switches, but I was trying to avoid doing a recapture at all, as I think it would be faster to find a workaround for this specific type of ATI driver that doesn't include that .dll

    To any techs searching this topic, what I've found to work (short of using different drivers or recapturing the image with Visual C++ 2010 installed) is creating a task sequence step that copies 'MSVCR100.dll' into the machine's C:\Windows\System32 folder before WINSAT testing, and the process continues on fine. Not sure what kind of impact this has on Visual C++ 2010 being installed later or getting your WEI score, so use at your own risk. 

    • Marked as answer by jdoiwpcs Thursday, January 23, 2014 1:49 PM
    Wednesday, January 22, 2014 7:15 PM

All replies

  • Hi,

    Normally I think WinSAT is only relevant when deploying the image to your targeted computers (hardware). So why not integrate Visual C++ components into your reference image?

    At the customer I'm currently working for we also put all our Visual C++ installations in the so called Build image.

    I have provided a list with the install commands for the various programs.

    Visual C++ 2005 SP1 ATL Security Update x64 msiexec /i "vcredist.msi" /qb
    Visual C++ 2005 SP1 ATL Security Update x86 msiexec /i "vcredist.msi" /qb
    Visual C++ 2005 SP1 MFC Security Update x64 msiexec /i "vcredist.msi" /qb
    Visual C++ 2005 SP1 MFC Security Update x86 msiexec /i "vcredist.msi" /qb
    Visual C++ 2008 SP1 ATL Security Update x64 install.exe /q
    Visual C++ 2008 SP1 ATL Security Update x86 install.exe /q
    Visual C++ 2008 SP1 MFC Security Update x64 install.exe /q
    Visual C++ 2008 SP1 MFC Security Update x86 install.exe /q
    Visual_C_2005_SP1_x64_8_0_56336_EN_M1 msiexec /i "vcredist.msi" /qb
    Visual_C_2005_SP1_x64_8_0_59192_EN_M1 msiexec /i "vcredist.msi" /qb
    Visual_C_2005_SP1_x86_8_0_50727_42_EN_M1 msiexec /i "vcredist.msi" /qb
    Visual_C_2005_SP1_x86_8_0_59193_EN_M1 msiexec /i "vcredist.msi" /qb
    Visual_C_2008_SP1_x64_9_0_30729_17_EN_M1 msiexec /i "vc_red.msi" /qb
    Visual_C_2008_SP1_x64_9_0_30729_4148_EN_M1 msiexec /i "vc_red.msi" /qb
    Visual_C_2008_SP1_x86_9_0_210022_EN_M1 install.exe /q
    Visual_C_2008_SP1_x86_9_0_30729_17_EN_M1 msiexec /i "vc_red.msi" /qb
    Visual_C_2008_SP1_x86_9_0_30729_4148_EN_M1 msiexec /i "vc_red.msi" /qb
    Visual_C_2010_x64_10_0_40219_EN_M1 msiexec.exe /i "vc_red.msi" /qb
    Visual_C_2010_x86_10_0_40219_EN_M1 msiexec.exe /i "vc_red.msi" /qb

    Trying to install Visual C++ and than run WinSAT post OS installation will not work.


    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Wednesday, January 22, 2014 12:54 PM
  • Thanks for the msi switches, but I was trying to avoid doing a recapture at all, as I think it would be faster to find a workaround for this specific type of ATI driver that doesn't include that .dll

    To any techs searching this topic, what I've found to work (short of using different drivers or recapturing the image with Visual C++ 2010 installed) is creating a task sequence step that copies 'MSVCR100.dll' into the machine's C:\Windows\System32 folder before WINSAT testing, and the process continues on fine. Not sure what kind of impact this has on Visual C++ 2010 being installed later or getting your WEI score, so use at your own risk. 

    • Marked as answer by jdoiwpcs Thursday, January 23, 2014 1:49 PM
    Wednesday, January 22, 2014 7:15 PM
  • How do you know for sure that WinSAT is the one that is complaining about the missing MSVCR100.dll? I doubt that WinSAT would have that kind of dependency problem. Although if there is some kind of driver causing it then you have other problems.

    It could be a 3rd party task bar applet that is blocked.  Try to break into the app with some SysInternals tools just to be sure.


    Keith Garner - keithga.wordpress.com

    Thursday, January 23, 2014 6:43 AM
    Moderator
  • Keith, I'm quite sure it was as the error prompt was titled WinSAT.exe - unless it's disguised as something else. Either way this has been solved via the workaround of manually placing that .dll there in a task sequence step before this. 

    Thanks,

    Thursday, January 23, 2014 1:49 PM
  • Can you provide the step in the task that you created to solve this I'm having a similar issue myself.
    Tuesday, December 2, 2014 1:40 PM
  • iamLu,

    It's been awhile and we've recaptured our images and re-done task sequences since this and it's no longer an issue on our end. (we're now on MDT2013 as well)  If I remember correctly, I found and copied that .dll from a known good computer with Visual C++ 2010 installed and put it to a network location.

    Then, I made a task sequence that just copies that .dll into the needed location on the imaging client's machine and it skipped over that error completely. 

    Tuesday, December 2, 2014 1:52 PM
  • All,

    Also, check out this post.  I found it extremely helpful when pulling down all of these C++ Redistributables.  The guy who wrote this is a genius!

    http://deploymentbunny.com/2014/08/05/powershell-is-king-download-all-vc-runtimes-using-a-script/

    (And no, it wasn't me who wrote this..)

    /Brian G


    -BrianG (http://supportishere.com)

    Tuesday, December 2, 2014 6:00 PM