Heck... it took until Windows 8.1 Update (1) before USB 3.0 was finally relatively stable as compared to Windows 7; due to driver changes.
C'mon Jim... again, you full well know you need to check for drivers when upgrading your system. And please don't give me the "average person doesn't know this" routine, because like any piece of equipment you own, whether it be a car or a PC, it requires routine maintenance. In the case of PC's... Windows updates, and driver/software updates need to be performed on a regular basis. Again... you know this.
And again, it is NOT Microsoft's responsibility to manage other vendor's hardware/software updates. Including Renesas who owns a large share of the USB 3.0 controllers on motherboards.
Sheesh.
Do you even keep up with those types of issues.
For example, Intel provids drivers for their USB 3.0 chipsets that you'll find in most new motherboards now for Windows 7.
But, guess what? They do not provide them for Windows 8, 8.1 or 10.
Why? Microsoft insisted that the Microsoft drivers be used instead of Intel's drivers, and they've been extremely buggy.
Why do you think I pointed that out (that it took until Windows 8.1 Update (1) before USB 3.0 drivers were relatively stable): That was because Microsoft insisted on users going with their drivers, with Intel agreeing not to supply drivers for Windows 8.x or later.
Some of the other USB 3.0 chpset makers do supply drivers. But, if you're using an Intel chipset (as most computers built for years, starting with Ivy Bridge do), you are using Microsoft drivers with Win 8, 8.1 or 10 (since Intel does not provide drivers for USB 3.0 chipsets for newer Operating Systems).
Microsoft is doing is doing he same thing for some of the otherUSB 3.0 chipsets, providing native Microsoft drivers for them, n agreement with the chipset makers, since Mocrpspft wans you using their drivers with newer Windows releases.
If you dig around hard enough, you can find some articles on how to modify files to try and use vendor provided USB 3.0 drivers from Windows 7 instead of Microsoft's drivers users are forced to use by default in Win 8.x and now Win 10.
Many users wanted to do that with Intel Usb 3.0 host controllers, since Intel dos not provide drivers for Windows 8, 8.1 or 10 for them. But, Microsoft has slowly worked out the issues with their drivers, and now, they;re relatively stable after the last updates to them.
No offence, as I guess you might have good intentions, versus really wanting to spend your time criticizing others trying to help users, as some of the other forum members seem to do
That's a very common problem in the forums here -- users that seem to think that they're "experts", without a clue what they're talking about, looking for any opportunity to bash members that are trying to help
So, you're not alone.
Again, MS provides base functionality to basic hardware to get them started, after that, its up to you to install their specific drivers... not Microsoft.
Again, why don't you research how that kind of thing really works
For some chipsets, no vendor provided drivers are available for Window 8x or Windows 10. For example, as just pointed out, Intel does not provide drivers for their USB 3.0 chipsets for Win 8.x or later -- you must use Microsoft developed drivers instead.
Where wireless is concerned, Microsoft will usually include vendor provided chipset maker's drivers. But, the drivers they provide may or may not cause issues, as they will often over write the computer manufacturer’s "tested" drivers with drivers that do not work properly.
I've had issues on numerous occasions because of that kind of nonsense from Microsoft Windows update.
You don;t need to try very hard to find lots of news articles about how Microsoft windows updates were botched, overwriting good drivers with bad drivers (for wireless chipsets, video card chipsets and more). Heck right after Win 10 was introduced, we saw a major fiasco because of the way Microsoft rolled out Nvidia drivers that caused conflicts. You'll find *many* news articles about that screw up
I've even seen them screw up drivers for sound cards (replacing working drivers with bad drivers, where I had to "jump through hoops" to undo all of the damager caused to registry entries and more.
Sure... they try to help out with driver updates. But, I'd suggest you be very careful about what you let MS Windows Update install.
So, the changes to the way Windows Update in Windows 10 works for typical home users does concern me. Sure, you can find a utility that lets you "hide" problem driver updates now so that they won't try to reinstall after they're removed. But, the basic malfunction is that you can't hide them ahead of time like you could with previous versions of Windows You have to hide them after they're installed (and potentially screw up your windows installation) instead.
The new forced updates mechanism for Windows 10 Home Users is just an accident waiting to happen. You can say that the new Windows Insider Program with it's "fast ring", and "slow ring testers should allow more robust testing before those updates are rolled out to more users.
But, we're seeing how well that works so far. For example Mircosoft not rolling out the latest updates to Adobe Flash Player and Edge Browser to the "fast ring" so that the updates will be tested more, and instead only rolling them out to users of the final releases and "slow ring", totally bypassing the testing by the fast ring users they've been promoting as helping to insure all updates are better tested before sending them to more users.
I hate to think about how widespread update related problems will be in the future if they continue down that path (rolling out forced updates to Windows 10 users without better testing first). Microsoft's reputation for botching updates is well known, and with the new forced updates for Windows 10 Home Users (with no way for them to
pt out like they could using Windows XP, 7, 8 or 81), we're bound to see some very serious update related issues going forward.
Now, in fairness to Microsoft, there is a way to stop them from sending driver updates to Windows 10 users. Here's one article about it:
http://winsupersite.com/windows-10/stop-automatic-driver-updates-windows-10
But, like the defaults for the user account, privacy settings and more, a typical Windows 10 Home User is not going to know how to perform those tasks.
Non driver related updates are still going to be forced with no way to opt of them, too. If you want Microsoft doing anything it wants to with your OS, by all means, use windows 10 home.
"Windows 10 is not the monster you and many others try to make it out to be. And outside of the "privacy uproar", which I find laughable, especially since most of these same people use Google and smartphones, many of the issues or complaints are no different from any other operating system that was newly released. Some of these same arguments go back to DOS to 3.1 and forward. Nothing new.
Sorry but some of your logic is faulty, especially coming from someone with the experience you claim."
I don't recall saying hat Windows 10 is a monster. But, if the shoe fits wear it.
Outside of the privacy uproar, huh? so, I guess you don't care about that. Again, "complacency" It's amazing how many people defend their actions, and what Microsoft is able to get away with without the DOJ pressing charges under existing anti-trust laws.
Ethics seemed to have been thrown out the Window since Microsoft started trying to force users to upgrade to Windows 10, using every "trick in the book". including sending Window 10 installers to users of Windows that did not want to upgrade to it, and even "accidentally, by mistake" enabled the supposedly "optional" Windows 10 installation by default, causing the problems the OP of this thread ran into earlier, where he could not receive any other updates for a Win 7 installation without running the window s10 installer. That's happened to many users.
One reason I pointed out the updates the OP may want to make sure are hidden again, is because he ran into issues with forced updates for Windows 10 installation before, where he started a thread about it here:
http://www.dpreview.com/forums/post/56303751
Isolated case, right? Nope. See the articles linked to in this more recent rhead:
http://www.dpreview.com/forums/post/56633308
Sure, go ahead and defend those practices. You're not the only one here doing it.
But, you may want to read up on what is really happening first, versus assuming things like you've been doing so far.
Too many users are wearing blinders, and ignoring that Microsoft is doing everything they can get away with to turn Windows into an advert delivery platform, with money being made from Bing Search results by default (even for desktop searches unless you change the default settings), new style applications with embedded adverts and more
Fine.. if they want to do that and users are willing to put up with it, let them. But, when they start forcing Windows updates down users throats that do not want to upgrade, and start pushing out updates to previous versions of windows that gather the same types of data on user's computer usage,then IMO, they're stepping "over the line"
I do not like it at all, and sure, I'm going to suggest that users stick with Windows 7 for a variety of reasons, including it's more familiar User Interface, and how it gives users more control over updates (versus the forced updates Window 10 home users put up with, with no way to opt out).
If they were only forcing Critical Security related updates, that would be one thing. But, the forced updates also include any feature and application updates they may want to roll out, including notifications in your system tray to "upgrade to Office 365, get more space with OneDrive" etc.
Yea, there are some settings that can get rid of some of that Spam (what I'd consider it to be) But, again, a typical user is not going to know how to get into those settings, and end up with a Windows OS that is being used for an Advert Delivery platform. Free Upgrade, huh?
But I was not pointing out those deficiencies in this thread until pushed by you, with your inaccurate info about how things like USB 3.0 drivers work in newer versions of Windows..
Instead, I was sticking to issues that I felt the OP would like more information about, as I'm getting really tired of responding to flame bait style posts that serve no purpose other than to criticizer my posts (with criticism that is often full of flawed information that is blindly ignoring pertinent issues impacting users).
--
JimC
------
