Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fokke Nauta Newsgroups: alt.comp.os.windows-11 Subject: Re: Can't connect to laptop Date: Mon, 28 Apr 2025 15:31:39 +0200 Lines: 69 Message-ID: References: <19dpvj20hqpzx$.dlg@v.nguard.lh> <3q9r7zon7e6x.dlg@v.nguard.lh> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net XI02aEzjaH21sHkuUxSoPghshfZ7GKhz1POPx1nCpYqeHagjMF Cancel-Lock: sha1:R+wJh7nHDHSJmBYV7y0IRJY6j4c= sha256:EUy1TjqWzmJiABOUg8b5f5NzP7PgCUY28q0oXx/Unpw= User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: nl In-Reply-To: Xref: csiph.com alt.comp.os.windows-11:18763 On 28/04/2025 14:58, VanguardLH wrote: > Fokke Nauta wrote: > >> VanguardLH wrote: >> >>> Fokke Nauta wrote: >>> >>>> From my pc: Troubleshoother couldn't identify the problem. >>>> From my wife's laptop: Troubleshooters are being moved and this utility >>>> is being retired. >>>> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are >>>> being deprecated. >>> >>> msdt.exe gave some error, and refused to load? >> >> It did load but I need a key that I got from a support assistance. Thais >> is bullshit, ofcourse. >> It also said "Troubleshooters have been moved and this utility will be >> deprecated." > > Yeah, that is when invoked with no command-line parameters. I got that, > too, on Windows 10. Invoke it with the command line that includes the > "/id NetworkDiagnosticsFileShare" argument that Paul mentioned. > > For Windows 10, I can get at the troubleshooter using the Start menu for > navigation. When I loaded it that way, and saw msdt.exe show up in Task > Manager, I used SysInternals' Process Explorer to see if there were > arguments in the command line, but it didn't show any. > > In the MS article I mentioned before in a reply to Paul, and for Windows > 11, you use the Get Help app to dig out the troubleshooter. If you > didn't disable Copilot, maybe that can start the troubleshooter. > > https://support.microsoft.com/en-us/topic/getting-started-with-copilot-on-windows-1159c61f-86c3-4755-bf83-7fbff7e0982d > > Not sure what you'd ask it, but maybe "network troubleshoot" would work. I'll have a look at copilot. It's new for me. > Your reply to Paul looked like you did run the troubleshooter, not that > it refused to load or start. Yet what you said made it appear your > computer had a different version of Windows than your wife. Yes. My pc has W10 Pro, my wife's laptop has W11 Pro. On your > computer, the troubleshooter ran, but didn't find a problem. On your > wife's, a message appeared about deprecation, but that was unclear if it > just showed the message, and refused to run. > > In any case, sometimes the troubleshooters find a problem, but more > often they don't. They're not very intelligent, and they don't check > much, plus they aren't trying to connect to anywhere to actually testing > networking. > > From another reply from you, there are more than just your computer and > your wife's on your intranet. "All other pc's I can open" which > probably meant you have other computers to which yours can connect. Correct. How > about the "other pc's": can they connect to your wife's computer? No, they can't either. Fokke