bug reporting

I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim

"Joakim Gyllstedt" wrote in message news:OEkuKfQPGHA.2300@TK2MSFTNGP15.phx.gbl

I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim

news://msnews,microsoft.com/microsoft.public.internetexplorer.general
-- Frank Saunders, MS-MVP OE "Anyone who prefers security over freedom deserves neither."

Seriously, do you really think that the Internet Explorer Public Newsgroup is the right place for Vista bug reporting?
What i want to know is if there is any bug tracking system? Of course I can spam every public Microsoft newsgroup/forum/blog with Vista in the title, but I don't think that it is the right way to do it.
/Joakim
"Frank Saunders, MS-MVP OE" wrote:

"Joakim Gyllstedt" wrote in message news:OEkuKfQPGHA.2300@TK2MSFTNGP15.phx.gbl I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim
news://msnews,microsoft.com/microsoft.public.internetexplorer.general
-- Frank Saunders, MS-MVP OE "Anyone who prefers security over freedom deserves neither."

"Joakim Gyllstedt" wrote in message news:34AC8C68-5CA0-4E5A-AA8B-CE182F9BDD59@microsoft.com

Seriously, do you really think that the Internet Explorer Public Newsgroup is the right place for Vista bug reporting?
What i want to know is if there is any bug tracking system? Of course I can spam every public Microsoft newsgroup/forum/blog with Vista in the title, but I don't think that it is the right way to do it.
/Joakim
"Frank Saunders, MS-MVP OE" wrote:
"Joakim Gyllstedt" wrote in message news:OEkuKfQPGHA.2300@TK2MSFTNGP15.phx.gbl I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim
news://msnews,microsoft.com/microsoft.public.internetexplorer.general
-- Frank Saunders, MS-MVP OE "Anyone who prefers security over freedom deserves neither."

Oops, I got confused. That is the proper place for IE7 bugs. Post Vista bugs here.
-- Frank Saunders, MS-MVP OE Please respond in Newsgroup. Do not send email http://www.fjsmjs.com Protect your PC http://www.microsoft.com/security/protect/

You should have an MSDN section of your site which enables you to leave feedback and bug reports. I can't remember the URL but I've seen it around before :o)
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!
--- Original message follows --- "Joakim Gyllstedt" wrote in message

Seriously, do you really think that the Internet Explorer Public Newsgroup is the right place for Vista bug reporting?
What i want to know is if there is any bug tracking system? Of course I can spam every public Microsoft newsgroup/forum/blog with Vista in the title, but I don't think that it is the right way to do it.
/Joakim
"Frank Saunders, MS-MVP OE" wrote:
"Joakim Gyllstedt" wrote in message news:OEkuKfQPGHA.2300@TK2MSFTNGP15.phx.gbl I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim
news://msnews,microsoft.com/microsoft.public.internetexplorer.general
-- Frank Saunders, MS-MVP OE "Anyone who prefers security over freedom deserves neither."

I finally found the download link to the "Microsoft Beta Client" right on the desktop in the "How to Share Feedback" document... Maybe I should have had a look at it before running all around the internet! :)
Sending bugreports like a maniac now... :)
/Joakim
"Zack Whittaker (R2 Mentor)" wrote:

You should have an MSDN section of your site which enables you to leave feedback and bug reports. I can't remember the URL but I've seen it around before :o)
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!
--- Original message follows --- "Joakim Gyllstedt" wrote in message Seriously, do you really think that the Internet Explorer Public Newsgroup is the right place for Vista bug reporting?
What i want to know is if there is any bug tracking system? Of course I can spam every public Microsoft newsgroup/forum/blog with Vista in the title, but I don't think that it is the right way to do it.
/Joakim
"Frank Saunders, MS-MVP OE" wrote:
"Joakim Gyllstedt" wrote in message news:OEkuKfQPGHA.2300@TK2MSFTNGP15.phx.gbl I've got access to Windows Vista through our Gold Partner Program / MSDN- Subscriptions, but I cant find any information about where to report bugs!
I've got a lot of bug's that I'd like to report, but where?
/Joakim
news://msnews,microsoft.com/microsoft.public.internetexplorer.general
-- Frank Saunders, MS-MVP OE "Anyone who prefers security over freedom deserves neither."

Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

You're both twerps :)
Neither of you provided attribution for the language of the text you supplied -- not Andre in his post or Zack on his site. (It's ripped direct from Microsoft.)
"Andre Da Costa [Extended64]" wrote in message

The signature is enough. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message Plug them more often then.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message I am Admin at Windows Connected and Extended64. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message That's the idea of the website - helps direct users to the content. Why don't you set your own site up?
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

The signature is enough. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message

Plug them more often then.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message I am Admin at Windows Connected and Extended64. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message That's the idea of the website - helps direct users to the content. Why don't you set your own site up?
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

Plug them more often then.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message

I am Admin at Windows Connected and Extended64. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message That's the idea of the website - helps direct users to the content. Why don't you set your own site up?
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

I am Admin at Windows Connected and Extended64. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message

That's the idea of the website - helps direct users to the content. Why don't you set your own site up?
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

That's the idea of the website - helps direct users to the content. Why don't you set your own site up?
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Andre Da Costa [Extended64]" wrote in message

Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

Give a direct answer and stop plugging your website like the ng is a socket. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker" wrote in message

All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

All the options here: http://www.vistabase.co.uk/welcome.php?bugreport
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "gerryR" wrote in message

theres a bug in your "date and time"

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

theres a bug in your "date and time"

"Alan Simpson" wrote in message

Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

Check under All Programs, Error Reporting is the folder group, it also contains a shortcut to "Problem Reports and Solutions". -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"wyatt" wrote in message

I don't have that link anymore. Can I recreate it? Thanks.
"Frank Saunders, MS-MVP, OE/WM" wrote:
"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?
Did you try the Feedback button on your desktop?
-- Frank Saunders, MS-MVP, OE/WM Please reply in newsgroup.

I don't have that link anymore. Can I recreate it? Thanks.
"Frank Saunders, MS-MVP, OE/WM" wrote:

"Alan Simpson" wrote in message Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?
Did you try the Feedback button on your desktop?
-- Frank Saunders, MS-MVP, OE/WM Please reply in newsgroup.

Its located within the Feedback link on the Windows Vista desktop: For Feedback: http://go.microsoft.com/fwlink/?linkid=55160
Feedback reporting tool: http://go.microsoft.com/fwlink/?linkid=43655
Tips for how to file a problem report
Here are some things to consider when filing a problem report:
Please file your report as soon as possible after you find a problem. The sooner we hear from you, the sooner we can investigate and try to fix the problem.
Please provide a brief, descriptive title. The title is the first thing we see when we get the report, so a succinct, clear title will help us effectively identify and prioritize the problem.
Please provide enough detail in the description for us to understand the problem. The more detail you can provide, the better.
Please provide the steps we can follow to reproduce the problem. Any incorrect or missing steps can prevent us from being able to reproduce and address the problem. If you have any supplemental files, screen shots, etc., that will help us investigate the problem, please attach those to your report. Seeing a picture can sometimes help us identify the problem more quickly. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Alan Simpson" wrote in message

Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

"Alan Simpson" wrote in message

Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

Did you try the Feedback button on your desktop?
-- Frank Saunders, MS-MVP, OE/WM Please reply in newsgroup.

"Alan Simpson" wrote in message

Can't seem to find the link for reporting bugs in Beta 2. Anyone know that offhand?

For some reason the bug reporter aint working! will not install. Any suggestions?
thanx

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?

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

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?

I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message

I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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" wrote:

I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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.
"Rob" wrote in message

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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

"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" wrote:

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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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).
"Rob" wrote in message

"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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message

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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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" wrote:

In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message 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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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
"Rob" wrote in message

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" wrote:
In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message 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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

patch = path
"Colin Barnhorst" wrote in message

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
"Rob" wrote in message 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" wrote:
In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message 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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

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" wrote:

patch = path
"Colin Barnhorst" wrote in message 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
"Rob" wrote in message 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" wrote:
In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message 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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?

I don't find netdtect.dll either.
"Rob" wrote in message

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" wrote:
patch = path
"Colin Barnhorst" wrote in message 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
"Rob" wrote in message 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" wrote:
In my first post I meant to say "you can run sfc with params." Sorry.
"Colin Barnhorst" wrote in message 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).
"Rob" wrote in message "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" wrote:
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.
"Rob" wrote in message 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" wrote:
I think uninstalling the old one completely and then running the new download might have worked better.
"Rob" wrote in message I forgot to mention that trying to run dxdiag also results in the same error message.
"Rob" wrote:
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?