286
A while back I had network issues, ran the troubleshooter and apparently the IP address was incorrect. Went into Control Panel, changed it and it worked again. Not sure why the troubleshooter couldn't do that but whatever.
this post was submitted on 13 Nov 2023
286 points (95.8% liked)
Asklemmy
43755 readers
2200 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
I was missing printer drivers it found the drivers (iirc)
Folks, Windows's own system image couldn't be restored from Windows. I had to go download some program called Macrium Reflect and use the underlying VHD files.
What broke? Oh, you don't know? It was a bad Windows update that had a broken driver or something causing driver verification to fail.
I would usually have issues with my wi-fi, where the connection after a reboot won't work and the wi-fi GUI would reset itself everytime i tried. Network troubleshooter would fix it 100% every time and quite quickly, so there was no reason to actually figure out what was at fault.
Many times.
I can't say I've ever had a problem solved by any of the troubleshooters, yet I always go to them just in case one day they do.
Usually they either direct you to the most generic solutions possible (that you've already likely done by the time you're resorting to the troubleshooter), reset your networking (thanks Windows, I felt like having to reconnect to all my networks again) or come back saying they couldn't find a problem...
Which clearly isn't the case Microsoft, because if there wasn't a problem, why the fuck would I be using the troubleshooter? For the shits and giggles?
I had it work once for a wifi issue that was caused by an update, during either Vista or Win7 era. Outside of that, it fixed an audio problem for Win10 on a single app.
It broke itselt, it broke Win2Usb and it broke grub. Thats it hahaa
I had a problem once when my laptop display was just black after booting. Triend everything, nothing worked. Return to OEM authorized support. They had my laptop for 4 weeks, so solution. Then just refunded the full price & retuned back the laptop.
Ubuntu LTS since then & no sick or weird issues since.
No. Tried it like 3-4 times in my life for really f-ed up not booting machines and it never worked for me. Haven't tried it since the ealy Win10 times, though.
only once for startup repair, twice for system restore. all client systems, not mine, since the introduction of those features. one of those ended up needing a full backup and reinstall soon after anyway.
plus the one time shadow copies from automatic system restore points saved a client's cad, docs, images, pdfs, and other files from a poorly-executed ransomware attack (that failed to clear out those vss copies). a nirsoft utility was able to save everything.
the 'fixit' troubleshooters are nearly worthless.
I think it pointed out the right direction at least once, back when i was doing tech support (xp and pre-xp). Back when the toolkit includes whole stacks of cd's containing every driver known to exist. I don't even remember what it is, but it was something Realtek.
both fixed things many times
It will sometimes wipe your static IP configuration and switch it to DHCP which could theoretically fix something, but I've only ever seen this break things instead.
Not that I've ever seen. It usually means it's time to reinstall.
It's weird to me that we accept 'reinstall the whole operating system' as a fix, it's so absurd. I've literally never had to do that with any other operating system.
It isn't accepted as a fix, because it doesn't fix the issue.
Reinstalling is done for speed. Because it is quicker to nuke something and build it back up, than to go around and fill all the cracks with concrete.
In business, it is more important the system is back up and running than to have found the fix to the issue.
This is true for every OS.
Overall ya, but I've done my fair share of reimage or reinstall. Either because it would be faster(biz setting, Becky in accounting gotta get payroll done ASAP) or I just don't want the headache of it at that moment.
I moved my business off MS to Linux a few years ago, and unplanned maintenance just... stopped being a thing. It was surreal. I expected something to not work or require lots of expert configuration, but nope. Most people here already use cloud applications for work anyway.
Never thought I'd see the day! I did make a whole bunch of HD images just in case though :D
Nah more features and flexibility the better
This would only be possible if it installed Linux.
If the problem can be solved by a restart of that thing's service (audio, network, etc.) then it has fixed things for me in the past.
Pretty much no other solution (especially the running old games one) has ever worked in the troubleshooter without me having to tinker with it further.
Oh, man, I may have to eat crow on this one! This reminds me how, at my previous job, the lousy HP printer driver would freeze up and stop printing. I could get it printing again by going into Services and re-starting the printer service. It was more convenient, and easier to train my staff, to just run the printing troubleshooter. It never reported a problem, but it did re-start the printer service, which fixed the immediate issue.
Moral of the story: Only an HP deals in absolutes.
It used to fix WiFi issues for me back on Windows Vista (bleh). Vista would always have issues when I woke my laptop from sleep mode, and my WiFi would be disconnected and unable to reconnect/properly turn off. Running the troubleshooter would restart my wireless card. Other than that I haven't encountered anything it's helped, but I don't use windows too often these days.
I think it helped with a internet issue once, but I probably just needed to reset something.
I'm pretty sure it just does the absolute basic troubleshooting.
Troubleshooting has never been useful, and I think that was new-ish in XP. Startup repair (and chkdsk) have genuinely been useful.
The HP help and troubleshooting software did better than the Microsoft one.