Bug Reporting Problem

[Guest]

I've been using the Microsoft Beta Client Reporting Tool for a few days now
without any problems.

Today however, I tried running it but I get an error titled, "dxdiag.exe -
Unable to Locate Component" and the body of the error message says, "This
application has failed to start because netdtect.dll was not found.
Re-installing the application may fix this problem."

So redownloaded the Problem Reporting Tool and repair-installed it it but
the problem is still there.

The only thing I have done in the last day or is to disable Windows Search
service and also disabled Indexing service as well. I doubt these are
connected, but could they be?

Any ideas what's causing this?

 

[Guest]

I forgot to mention that trying to run dxdiag also results in the same error
message.

 

[Colin Barnhorst]

I think uninstalling the old one completely and then running the new
download might have worked better.

 

[Guest]

I'm beginning to wonder if this has anything to do with the reporting tool.

I uninstalled it comepletely and restarted the computer and then tried to
just run dxdiag and I still get that error.

Can my dxdiag be corrupt, and if so what can be done to restore it? Does
Vista beta support running the command sfc /scannow?

 

[Colin Barnhorst]

To run right click on the cmd icon (run) and choose 'run as administrator'.
When you get the command window you can run scannow with params. Set a
system restore point first because I have seen one or two posts indicating
some issues.

 

[Guest]

"run scannow with params"? What does "params" mean? Sorry I'm a little slow
today. Do you mean just running the "sfc /scannow" command?

Thanks. I'll report back once this is done.

 

[Colin Barnhorst]

The '/scannow' is the parameter you want to use with 'sfc'. To see a list
of parameters for a command type the command followed by a space and '/?'
(no quotes, of course).

 

[Colin Barnhorst]

In my first post I meant to say "you can run sfc with params." Sorry.

 

[Guest]

Just an update:

I ran the CMD with Admin privileges and it defaulted to c:\windows\system32
file, which is fine I guess. When I then typed "sfc /scannow" it said that
"System wide scan is not implemented for Beta 2. Please run sfc per file."

I have no idea where dxdiag is in windows to run sfc for that particular
file. I also, just for kicks, ran a system restore to before when the problem
started happening and the restore went smoothly however the problem was still
present.

I think I just hit a brick wall here. Any ideas short of a clean re-install
of Vista?

Thanks.

 

[Colin Barnhorst]

Type 'dxdiag' in the start search box but do not hit Enter. In the list
above you should see its icon. Right click on the icon and choose Open File
Location. Check the patch in the WE address bar. I got
D:\Windows\System32\dxdiag
so the path would be
%systemroot%\Windows\System32\dxdiag

 

[Colin Barnhorst]

patch = path

Type 'dxdiag' in the start search box but do not hit Enter. In the list
above you should see its icon. Right click on the icon and choose Open
File Location. Check the patch in the WE address bar. I got
D:\Windows\System32\dxdiag
so the path would be
%systemroot%\Windows\System32\dxdiag

 

[Guest]

Hey Colin,

In case you're still checking on this issue, or anyone else reading who
might be able to help, here's an update.

dxdiag is the same path for me (mine is c:\ however).

Running the sfc "verify file" parameter on dxdiag.exe resulted in the
message that says it did not find any integrity violations. System wide
'Scannow' parameter does not seem to be supported in Beta 2.

Also, running the sfc "verifyonly" paramter on the system starts the scan
normally but half way through it says it could not perform the requested
operation and just stops.

There is really only one more thing I'd like to check and that is if on your
system the file "netdtect.dll" is present. I ran a search for it on my system
and could not find it. This file, as previously mentioned, is the one missing
when running dxdiag and also seems to be the culprit behind my Bug Reporting
Tool issue. I'm not really sure if the search I did was also scanning hidden
windows files (I'm not sure how to enable "Search hidden system files" in
Vista).

So, could you advise me if you have that file and if so, where it is?

Thanks.

 

[Colin Barnhorst]

I don't find netdtect.dll either.

Hey Colin,

In case you're still checking on this issue, or anyone else reading who
might be able to help, here's an update.

dxdiag is the same path for me (mine is c:\ however).

Running the sfc "verify file" parameter on dxdiag.exe resulted in the
message that says it did not find any integrity violations. System wide
'Scannow' parameter does not seem to be supported in Beta 2.

Also, running the sfc "verifyonly" paramter on the system starts the scan
normally but half way through it says it could not perform the requested
operation and just stops.

There is really only one more thing I'd like to check and that is if on
your
system the file "netdtect.dll" is present. I ran a search for it on my
system
and could not find it. This file, as previously mentioned, is the one
missing
when running dxdiag and also seems to be the culprit behind my Bug
Reporting
Tool issue. I'm not really sure if the search I did was also scanning
hidden
windows files (I'm not sure how to enable "Search hidden system files" in
Vista).

So, could you advise me if you have that file and if so, where it is?

Thanks.