Survey - Windows Network Diagnostics....
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I'd amend your title to "Windows Troubleshooters" in general. And also throw in
sfcanddism. They're the go-to answer for everything in the MS support forums. But I've never seem them fix a problem. :sigh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I'd amend your title to "Windows Troubleshooters" in general. And also throw in
sfcanddism. They're the go-to answer for everything in the MS support forums. But I've never seem them fix a problem. :sigh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
No.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
The name says it all. Diagnostics not repair. Now, do the thing actually diagnose anything?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Useful when customer is watching. Gives one time to figure out the real problem. :)
>64 It’s weird being the same age as old people. Live every day like it is your last; one day, it will be.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I'd amend your title to "Windows Troubleshooters" in general. And also throw in
sfcanddism. They're the go-to answer for everything in the MS support forums. But I've never seem them fix a problem. :sigh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I wouldn't lump dism into this category. This has always been my go-to solution whenever I needed to install .NET 2.0/3.5 on OSes that don't include it by default, and the installer fails (which I'm not sure ever worked for me). But this always succeeds: dism /online /enable-feature /featurename:NetFx3 /All /Source:E:\sources\sxs /LimitAccess (replace E: with the appropriate ISO mount drive, D: turned into a smiley...)
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
No Windows diagnostic has ever identified anything for me. On top of that, in Events Viewer, each error code has a link to click for more information. Not once has that ever returned any explanation.
Will Rogers never met me.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I've never had any Windows troubleshooter fix anything, except for the most extremely simple problems that are quicker to manually fix anyway. Same with System Restore. I had it successfully recover a relative's botched update - once - where Vista (to give you an idea of the timeframe) was stuck in a reboot loop. Rolled it back, reinstalled the update, and everything was fine. But I always have it disabled on my own systems, as I've never had a single use for it.
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
When I've seen it work is when it disables and reenables the adapter, which is pretty much the equivalent of turning it off and on again. So, yes, it has "fixed" things in my experience, though it hasn't done anything particularly "special" to make it happen.
Fool me once, shame on you; Fool me twice, prepare to die. --Klingon proverb
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
On one of my machines which is unfortunate to be equipped with an Intel NIC it can help. Unlike the startup repairing, which never ever solved any problem. SFC and DISM have also helped but the most case involved these unfortunately had a bad filesystem on a failing drive as root cause. Also fast startup + dual boot ...
-
I've never had any Windows troubleshooter fix anything, except for the most extremely simple problems that are quicker to manually fix anyway. Same with System Restore. I had it successfully recover a relative's botched update - once - where Vista (to give you an idea of the timeframe) was stuck in a reboot loop. Rolled it back, reinstalled the update, and everything was fine. But I always have it disabled on my own systems, as I've never had a single use for it.
System restore saved me many times with arcane drivers on unsupported OSes and also with a too well executed kiosk type lockdown with the [FrontFace Lockdown Tool - Windows Kiosk Mode (Freeware)](https://www.mirabyte.com/en/frontface/lockdown-tool/)
-
System restore saved me many times with arcane drivers on unsupported OSes and also with a too well executed kiosk type lockdown with the [FrontFace Lockdown Tool - Windows Kiosk Mode (Freeware)](https://www.mirabyte.com/en/frontface/lockdown-tool/)
I can certainly see the case where, in theory, the cleanest way to roll back a bad driver would be with System Restore. Fortunately I never got myself into that sort of situation where I couldn't get things back the way they were. I turn it off on my own systems. But I wouldn't necessarily encourage the less technically-inclined to do the same (because then I know I'd be the one they'd turn to). OTOH I've also sees systems with a crap-ton of restore points that had been diligently created...but turned out to all be reported back by the OS as "unusable". That did nothing to restore confidence...
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I have had the same experience with Maple (all versions since 2006). The codes and links don't even diagnose anything. For the uninitiated, Maple is a native math code system (mostly). It is also used by many college math programs to teach advanced mathematics. Sometimes using their online forum works, and someone will tell you wtf is going on, or at least how to avoid it. To err is human. To brp takes an LLM. Please stop. Who told you to add LLM tech to a science research paper writing system? Why ever would you DO that? Who told you to add LLM to a math model system like Maple? You do know that if I use AI in any way in research, I have to declare it to the journals? And I have to be able to tell them what it did for me? How the $#$#@! can I know exactly? Please stop. Quit spying on me!
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
For me, no, it never really fixed anything. And any error message you get from Windows about a networking issue is more likely than not just a red herring, which will lead you nowhere... I am always glad in such situation that I can look back at 40 years of networking experience, which allows me to quickly check on some of the basics, which in most cases are revealing the problem at hand. The only thing I get stuck once in a while is the whole security/permission mess that comes with Windows, something where I really wish I could work with good old Novell Netware again, there everything was logical and made sense...
-
Has it EVER fixed anything? Every time I've been prompted due to some network issue to run windows network diagnostics, it has NEVER, EVER found a problem or fixed anything. This morning, it just errored out with some random code.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Nope, but I have totally had the audio diagnostics wizard (stands out because recent 1st timer there) figure something out and make things start working again. It did not tell me what it found/did. I suspect a flag is randomly flipped to break audio so that it can take the credit for fixing it when it simply flips the flag back.
