This quote is from Lil Pun. Didn't you read it? It appears you offended him. "I really don't give a **** if you people talk about me or not. Thank you for your help before but you don't have to go spewing profanities like you're being inconvenienced, if it is troubling you helping me out then just don't do it."
A system restore does nothing as far as the driver's, you would have to manually roll back the drivers for the wireless card. And device manager will not say there is a problem as long as there is a driver loaded. Dont go throught the troubleshoot it is pointless. First thing you should always do when diagnosing the problem, once you have made figured you have a problem, is update all hardware with latest driver info.
I disagree. The first thing I do when I diagnose a problem when things have been working previous, is to determine what has changed. Why should I update an audio driver to the latest version if my network is having problems?
Excuse me, when I said all driver info, I failed to mention all driver info related to the issue ie. wireless not working, update wireless network drivers ie. Audio not working, download audio drivers and install You waste more time trying to figure out what has changed, when you could be resolving the issue. Plus that is a quick fix attempt. If that doesnt work then you think about what is the las thting changed since it worked
To each his own, but I am not going to change a driver unless there is a reason to. You may waste more time trying to determine what has changed, but others may not. Also, that "waste of time" always helps me further understand what's going on. To me, the problem with updating a driver may indeed be a "quick fix". In other words it may simply mask the underlying problem. If my wireless quits working for no apparent reason after it has been working properly for weeks or months, then I am fairly certain it is not the driver. Perhaps I installed something that does cause a problem/conflict with the driver. A driver update may be in order, but updating the driver could break something else. Personally, I want to know what was changed to cause the conflict to see if it is worth it to me to update the driver to fix the one thing that caused the conflict or to remove/undo what I did that introduced the problem.
No offense, but this is typical of a 1st tier call center troubleshooting mentality - get the caller off the line ASAP with a "quick fix" laden shot gun blast. I am not a fan of this approach. Determining the root cause of the issue is priority one.
agree, knowning the problem will solve more time in the future but if all fails, reconfigure the whole damn router
