DxDiag shows missing files after .Net 2.0, Oct and Dec 2005 SDK.

After installing the .Net Framework 2.0 and the Oct and/or Dec 2005 SDK, the DxDiag utility shows that some files are "missing".

DxDiag notes on the DirectX Files tab:

"Several files (system.dll, Microsoft.DirectX.dll, Microsoft.DirectX.dll) are missing!"

These files are present in the GAC and they coincide with the files from the .NET Framework 2.0 and the October and December 2005 versions of the .Net 2.0 beta versions of Managed DX.

system.dll - .Net Framework 2.0 (2.0.0.0)
Microsoft.DirectX.dll - October SDK - (2.0.900.0)
Microsoft.DirectX.dll - December SDK - (2.0.0.0)

Is it a known problem with DxDiag - that it doesn't recognize these files even though they are present

Thank you,

Jason P.

Answer this question

DxDiag shows missing files after .Net 2.0, Oct and Dec 2005 SDK.

thembi

Does your system have the regkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\ManagedDirectXVersion This key is created by dx9.0/dx9a/dx9b ManagedDX. i removed it on my system and problem goes away. The key ManagedDirectXVersion key is not needed for dx9c mdx.

Moses
Jon Jung

The existense of that regkey indicates that at one time you must have installed DXSDK Summer 2003. It shipped with mdx versioned 4.09.00.1126. The series of dxsdk 2005 updates setup doesn't create that regkey.
Alexey Orlov

sweeper wrote:

Same here, just did the .Net 2.0, The Dec SDK and dxdiag says "the file System.dll is missing" although there are two system.dll's available

.net 1.xxx and .net 2.xxx

We'll take a look and see if we can repro.

Thanks
Paul.Brown

I have not been able to reproduce this problem on a XP x86 machine with the final .NET 2.0 install, and the December 2005 SDK.

Are you sure you're using a non-beta .Net 2.0 install (i.e. from Microsoft Update or Windows Update) If you had a beta of .NET 2.0 (and/or a beta version of Visual Studio 2005), then you might want to try running http://hgao888.members.winisp.net/vs_uninst.exe and re-installing .NET 2.0.
lx1973
Thank you Moses. I deleted the reg. item and no more dxdiag missing file errors. I find it interesting that it only happened on 2 of my PC's. All are running similiar configs 2 did not have the error and 2 did. Crazy. Thanks again.

DeltaQ

Moses Mwangi wrote:

Does your system have the regkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\ManagedDirectXVersion This key is created by dx9.0/dx9a/dx9b ManagedDX. i removed it on my system and problem goes away. The key ManagedDirectXVersion key is not needed for dx9c mdx.

Moses

To follow-up on Moses suggestion, we're looking into why this is happening. We believe a change in the .NET 2.0 runtime has caused a problem with existing versions of DxDiag. The messages you see in DxDiag are in fact harmless so we're just trying to narrow down possible workarounds.

Thanks,

Paul

Rod1953
Deleted it too and now no more missing files message My thanks as well.

I just think it's strange that .net 1.1 was not making dxdiag read that key and .net 2.0 is
Shivax32
I haven't installed any betas of .NET 2.0 or Visual Studio 2005 ever. Only finals on this production machine.

My current environment:

Software:
Windows XP SP 2
Visual Studio Team Edition for Developers 2005 (RTM) (includes .NET 2.0 SDK)

Hardware:
P4 3.0 GHz with HT, 1 gig memory
ATI 9800 pro (with 5.13 Catalyst drivers)

I uninstalled the DirectX SDK (Dec 2005) and now the only file that shows as missing is the System.dll from the .Net Framework 2.0.

The System.dll file IS in the GAC and works when creating and compiling .NET 2.0 programs (command line or with VS 2005). Only DxDiag is unaware of the new stuff.

I will try to install just the December DirectX Redist and see what happens.

Jason P.
Inquirer
So i can delete that reg and its ok

jagotaas

Paul Bleisch wrote:

Moses Mwangi wrote:

Does your system have the regkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\ManagedDirectXVersion This key is created by dx9.0/dx9a/dx9b ManagedDX. i removed it on my system and problem goes away. The key ManagedDirectXVersion key is not needed for dx9c mdx.

Moses

To follow-up on Moses suggestion, we're looking into why this is happening. We believe a change in the .NET 2.0 runtime has caused a problem with existing versions of DxDiag. The messages you see in DxDiag are in fact harmless so we're just trying to narrow down possible workarounds.

Thanks,

Paul

Yes Paul and Moses,

The regkey

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\ManagedDirectXVersion

has the value: 4.09.00.1126

This is clearly not correct. Is it OK to remove this regkey or should I wait for future SDK

Thank you,

Jason P.

mr hamed
it appears that this is happening to a few people.

Here is a thread on the forums:

http://forums.microsoft.com/msdn/showpost.aspx postid=180398&SiteID=1

Entering "System.dll missing dxdiag" into google shows many hits.

Jason P.
tawm
bump

Can anyone verify this
wilyCoyote
Same here, just did the .Net 2.0, The Dec SDK and dxdiag says "the file System.dll is missing" although there are two system.dll's available

.net 1.xxx and .net 2.xxx
Josh Bernard
g'day. Deleting that registry key works. no more problems

thanks

Bob
DxDiag shows missing files after .Net 2.0, Oct and Dec 2005 SDK.

Answer this question