Last edited by snolat; 19 Aug 2016 at 13:38. Reason: No reason
Everyone is seeing that.
It is a known issue in 14905, as you would have known if you had read the Microsoft blog post about this new build before upgrading: Insider Announcing Windows 10 Insider Preview Build 14905 for PC and Mobile - Windows 10 Forums
Just blindly upgrading without first finding out about any known issues is not very clever. Screenshot from the announcement of build 14905:
The MS model is automatic update
- the fact that Release notes exist is non-sequitor for non-commercial users
Updates do not ask you to review the Release notes before updating - they just update your machine.
We are not talking about Windows Updates here. Were are talking about Windows Insider build upgrades. They are not automatic and can never be compared to automatic updates; each user can turn Insider upgrades off or switch to slow or release ring after a successful build upgrade thus not receiving next build automatically, then read the release notes when a new build is released and only then decide if he / she wants that build or not.
User's choice, not automatic. Even if in Fast Ring, a downloaded upgrade does not have to be installed.
The sentence from my first post in this thread which you
Windows as a service makes updates and upgrades indistinguishable - let's not argue semantics.
Windows 10 November Update
Windows 10 Anniversary Update
but Settings is defer Upgrades
No criticism and not worth more time - even the thread starter dropped out of this thread .
Yes, I agree, we both know you will never admit being wrong which makes this useless.
Updates and Upgrades are not same. Windows Updates are automatic whereas build upgrades can be unselected, even downloaded upgrades don't have to be installed. A wise user never upgrades without checking the release notes first.
For your information, you started this with a totally irrelevant post:
This thread was done after OP's post and my reply in post #2 from which BTW the OP gave me rep.
Your effort to be clever started then this unnecessary conversation in post #3.