System error: missing MSVCP90D.dll

433 views
Skip to first unread message

Munjal Doshi

unread,
May 15, 2012, 6:13:34 PM5/15/12
to Chromium-dev
After doing a sync and rebuild of chrome (all of which succeeded), when I run chrome.exe (debug build) from within VS or outside VS, I get the following system error dialog:

---------------------------
chrome.exe - System Error
---------------------------
The program can't start because MSVCP90D.dll is missing from your computer. Try reinstalling the program to fix this problem. 
---------------------------
OK   
---------------------------

Does anyone know what the problem could be?

Daniel Cheng

unread,
May 15, 2012, 6:22:42 PM5/15/12
to mun...@chromium.org, Chromium-dev
You could try (re)installing the VS2008 redistributable. I'm not really sure why it'd randomly stop working though if you have VS installed.

Daniel

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Alex Pakhunov

unread,
May 15, 2012, 6:26:29 PM5/15/12
to dch...@chromium.org, mun...@chromium.org, Chromium-dev
Shouldn't that be fixed if chrome was linked to the static CRT? Are there any specific reasons why the dynamic CRT is used?

Alex.

Munjal Doshi

unread,
May 15, 2012, 6:31:31 PM5/15/12
to Alex Pakhunov, dch...@chromium.org, Chromium-dev
Some time ago I followed some steps on chromium blog somewhere to setup the build env on windows to speed up the build. I wonder if one of them was to use dynamic CRT. Checking...

Munjal Doshi

unread,
May 15, 2012, 6:49:21 PM5/15/12
to Eugene Girard, Alex Pakhunov, dch...@chromium.org, Chromium-dev
I have no such folder as C:\WinDDK on my machine (Win 7 Enterprise).

On Tue, May 15, 2012 at 3:44 PM, Eugene Girard <gir...@google.com> wrote:
I "fixed" this by copying "C:\WinDDK\7600.16385.1\bin\x86\ia64\msvcp90.dll" into C:\Windows\WOW64.

(For debug builds, you will want msvcp90d.dll)

Eugene Girard

unread,
May 15, 2012, 7:01:45 PM5/15/12
to Chromium-dev, Munjal Doshi, Eugene Girard, Alex Pakhunov, dch...@chromium.org
The setup page (http://www.chromium.org/developers/how-tos/build-
instructions-windows) asks you to install the WDK if you are using
VS2010 Express. It's at http://msdn.microsoft.com/en-us/windows/hardware/gg487463.aspx

You might already have the DLL on your machine though.

HTH,
Gene

On May 15, 6:49 pm, Munjal Doshi <mun...@chromium.org> wrote:
> I have no such folder as C:\WinDDK on my machine (Win 7 Enterprise).
>
>
>
>
>
>
>
> On Tue, May 15, 2012 at 3:44 PM, Eugene Girard <gir...@google.com> wrote:
> > I "fixed" this by copying
> > "C:\WinDDK\7600.16385.1\bin\x86\ia64\msvcp90.dll" into C:\Windows\WOW64.
>
> > (For debug builds, you will want msvcp90d.dll)
>
> > On Tue, May 15, 2012 at 6:31 PM, Munjal Doshi <mun...@chromium.org> wrote:
>
> >> Some time ago I followed some steps on chromium blog somewhere to setup
> >> the build env on windows to speed up the build. I wonder if one of them was
> >> to use dynamic CRT. Checking...
>
> >> On Tue, May 15, 2012 at 3:26 PM, Alex Pakhunov <alex...@google.com>wrote:
>
> >>> Shouldn't that be fixed if chrome was linked to the static CRT? Are
> >>> there any specific reasons why the dynamic CRT is used?
>
> >>> Alex.
>
> >>> On Tue, May 15, 2012 at 3:22 PM, Daniel Cheng <dch...@chromium.org>wrote:
>
> >>>> You could try (re)installing the VS2008 redistributable<http://www.microsoft.com/en-us/download/details.aspx?id=29>.

Scott Graham

unread,
May 15, 2012, 7:04:47 PM5/15/12
to mun...@chromium.org, Eugene Girard, Alex Pakhunov, dch...@chromium.org, Chromium-dev
That dll should be in a subdirectory of \Windows\winsxs\.

If it's there, it smells like a manifest problem. You might have more
luck not using component=shared_library if you are using it.

(I'm surprised copying an ia64 dll did anything helpful?)

Gabriel Charette

unread,
May 15, 2012, 7:09:46 PM5/15/12
to mun...@chromium.org, Chromium-dev
This might be related to my recent change:

Which OS / build system (VS 200?) are you using.

I have a change upcoming to make this change more flexible (i.e. its currently supposed to work on your machine, but not when copying the bits over somewhere else) https://chromiumcodereview.appspot.com/10387140/ ... let me know if this helps you.

Cheers,
Gab

--

Alex Pakhunov

unread,
May 15, 2012, 7:11:10 PM5/15/12
to Scott Graham, mun...@chromium.org, Eugene Girard, dch...@chromium.org, Chromium-dev
(I'm surprised copying an ia64 dll did anything helpful?)

It probably wasn't actually an Itanium DLL:

"C:\WinDDK\7600.16385.1\bin\x86\ia64\msvcp90.dll"

Not that I think it copying anything to syswow64 directory is a good idea. :-) 

Alex. 

Munjal Doshi

unread,
May 15, 2012, 7:12:03 PM5/15/12
to Eugene Girard, Chromium-dev, Eugene Girard, Alex Pakhunov, dch...@chromium.org
I am still using VS 2008. And I do see the DLL in a ton of places under C:\Windows\winsxs.

Gabriel Charette

unread,
May 15, 2012, 7:14:06 PM5/15/12
to mun...@chromium.org, Eugene Girard, Chromium-dev, Eugene Girard, Alex Pakhunov, dch...@chromium.org
Ok this fix won't help you yet then, let me make it non-VS-version specific.

Gabriel Charette

unread,
May 15, 2012, 7:59:58 PM5/15/12
to Gabriel Charette, mun...@chromium.org, Eugene Girard, Chromium-dev, Eugene Girard, Alex Pakhunov, dch...@chromium.org
FYI, this change is being reverted as we speak, I'll write a new patch that does this correctly so that you shouldn't see it come through when it does ;)!


Cheers,
Gab

Munjal Doshi

unread,
May 16, 2012, 4:26:12 PM5/16/12
to Gabriel Charette, Eugene Girard, Chromium-dev, Eugene Girard, Alex Pakhunov, dch...@chromium.org
Thanks Gabriel.
Reply all
Reply to author
Forward
0 new messages