Most insiders got that build, then several updates to it along the way. Consumer's got it all in the one image, with I think one small update on release day. It seems to me that something went wrong with the creation of that master final image? One that was never really tested on very many, if any insiders? That's my best guess anyway.
I still very much like Windows 10, and will recommend it to others, I just think they dropped the ball this time around.
Please don't blame OEM's for a Microsoft poor decision policy (forced updates).
Microsoft let's us use the drivers, at a risk... and the OEMs are at fault in this case.
This is all they really had to do:
To update a code signing certificate
Step 1: Renew your code signing certificate
- Determine which type of code signing certificate you need (for more information, see Get a code signing certificate). UEFI and LSA certification now require extended validation code signing certificates.
- Get a new certificate or reuse an existing certificate.
- Once you receive your verified certificate from the certificate authority, you can sign and upload the Winqual.exe file following the instructions below.
Note When you register a new company on the dashboard, you must have a digital ID.
Step 2: Sign and upload your Winqual.exe file
- From the Hardware Dev Center dashboard, sign in as an administrator with your Microsoft account.
- Download the Winqual.exe file from the Hardware Dev Center dashboard, and sign it with the new digital certificate for your company using the SignTool.
- On the Administration page, in the Digital certificates tile, click Upload code for digital certification.
- On the Digital certificates page, click Browse to locate and select the Winqual.exe file that has been signed with the correct digital certificate for your company.
If you bought a OEM PC with Windows 7 on for example you'd never expect to get Windows 8 or 10 drivers a few years down the line. Why should they bother? There is nothing in it for them except perhaps goodwill. Perhaps it isn't much work but it is work and they only said it would work with 7. Better for them you buy a new one.
What is good news is the rumored enforcement of secure boot never came about. That would have been irritating to those of us who like to use old hardware.
Windows is designed to work on multiple types of equipment, with different types of drivers, it isn't a OS specific design as for MAC's with OS X.
The problem still exists, that the user "you know the one who usually owns and uses the computer", still has no control. Microsoft knows OEM's don't keep up, they have been doing business long enough to know this. So why make a policy that can forcibly cause a crash?
Forced updates for this OS is a bad policy... Plain and Simple.
Or perhaps OEMs should stop developing machines for Windows, they kind of have done this with apps, no one really wants to play that game either.
Testing takes almost 75% of the hole Costs on Software products!
Further, Windows is growing and growing , what makes it more difficult to test, and the Time for testing increases so that to have a fully tested release will take many months.
After all there is the question around the strategic of offering new Builds as "free", so we may have to accept some "flaws" .