In reply to a post by TinyMongomery:

Surely that is the fault of Creative rather than Microsoft?

I found it difficult to see it that way. It was working perfectly and the update broke it.

When a bad driver prevents a device from working properly I blame those who provide the driver.

Driver updates for Windows 10 and many devices (such as network adapters, monitors, printers, and video cards) are automatically downloaded and installed through Windows Update.
Who do you blame if Windows does not detect device. This has happened to me and I had to install driver separately.

The device drivers, in general, are not written by Microsoft but by the manufacturer of the device, so an error in the driver is down to them. It would not be reasonable to expect the developers of an OS to write drivers for every possible device.

Yes but the drivers are supposed to be tested by WHQL lab.

I don't use generic drivers if there is a specific one available. Might as well get full functionality if you can. I was surprised that an OS update caused my sound system to suddenly be plunged into silence 8^).

In reply to a post by longedge:

In reply to a post by TinyMongomery:

Surely that is the fault of Creative rather than Microsoft?

I found it difficult to see it that way. It was working perfectly and the update broke it.

Me too, i had problems with my Asus sound card on windows 10, windows 10 kept trying to change the drivers as they was suppose to be better, but they was not, because the Windows 10- drivers would not work at all.

To stop it happening I had to stop updates on all hardware, because you can not just stop updates on certain hardware. Ms really did not think this out.

One reason why I went back to Windows 8.1, The problem is i am still getting a memory management error now and again, not as often as I did, but still annoying. I blame Ms, not doubt done something to make it happen on new gen CPUs.

As for having software auto update, I tend not to allow it happen apart from my antivirus.

In reply to a post by TinyMongomery:

The device drivers, in general, are not written by Microsoft but by the manufacturer of the device, so an error in the driver is down to them. It would not be reasonable to expect the developers of an OS to write drivers for every possible device.

Microsoft has consistently, for several years, replaced HP AIO printer drivers with its own without asking, when upgrading from one version of Windows to another.

The result has always been the loss of facilities such as network access from other machines via the router; ink level monitoring; and the scanning facility.

That's not true. Manufacturers can self-certify their drivers. This means that they will install without an error message but aren't allowed to display the "certified for Windows" logo.

WHQL tests are normally performed by the manufacturer and the logs submitted to Microsoft, though Microsoft do test some hardware.