Microsoft needs to refocus on Windows 10 fundamentals - Mary Jo Foley
-
I suspect Roy111 may be right in post 5.
Not fine and not the preferred outcome, but an acceptable risk after deliberation considering that perfection is unattainable.
We just don't know the reasons they thought the risk was acceptable. And likely will never get a candid answer.
I don't detect a major furor. I don't watch "the news" on TV. Has it been mentioned on mainstream non-techy outlets?
Total revenue continues to climb significantly despite Windows declining percentage of that total. That may be part of the reason for their seeming indifference.
Would it be an acceptable Risk if this build was sent to Industries and the same result happened. No it would not and it was not and never will be acceptable to release a Flawed OS To anyone especially when they were informed of this Problem 3 months ago and did nothing -nothing to fix it.
-
-
A weird-ish thought hit me, what are the chances some of the hardware in use is just plain "too good" for some of the features in Windows. I base that on the fact that my newest Desktop out of 4 is only 3 years old and all of my Notebooks are older than that and I don't see very many of the problems that show up on Forums. And having an abundance of storage devices keeps me from needing OneDrive and its 'features'.
-
A weird-ish thought hit me, what are the chances some of the hardware in use is just plain "too good" for some of the features in Windows. I base that on the fact that my newest Desktop out of 4 is only 3 years old and all of my Notebooks are older than that and I don't see very many of the problems that show up on Forums. And having an abundance of storage devices keeps me from needing OneDrive and its 'features'.
You may have a point, my PC is old and I did not have any issues.
-
It seems, to me anyway, that its now an accepted fact that some users will be "inconvenienced" when Windows is updated and or upgraded? But hay, we'll be right on that "after the fact". 
-
-
I suspect Roy111 may be right in post 5.
Not fine and not the preferred outcome, but an acceptable risk after deliberation considering that perfection is unattainable.
We just don't know the reasons they thought the risk was acceptable. And likely will never get a candid answer.
I don't detect a major furor. I don't watch "the news" on TV. Has it been mentioned on mainstream non-techy outlets?
Total revenue continues to climb significantly despite Windows declining percentage of that total. That may be part of the reason for their seeming indifference.
If a calculated risk with this outcome is an acceptable risk, MS needs some more WD-40 on their abacus.
-
I suspect Roy111 may be right in post 5.
Not fine and not the preferred outcome, but an acceptable risk after deliberation considering that perfection is unattainable.
We just don't know the reasons they thought the risk was acceptable. And likely will never get a candid answer.
I don't detect a major furor. I don't watch "the news" on TV. Has it been mentioned on mainstream non-techy outlets?
Total revenue continues to climb significantly despite Windows declining percentage of that total. That may be part of the reason for their seeming indifference.
Not sure if you can view the main BBC News site in the USA but it made headlines here....
https://www.bbc.co.uk/news/technology-45784482
-
Would it be an acceptable Risk if this build was sent to Industries and the same result happened. No it would not and it was not and never will be acceptable to release a Flawed OS To anyone especially when they were informed of this Problem 3 months ago and did nothing -nothing to fix it.
The risk has to be acceptable to Microsoft. Apparently it was.
I'm assuming they thought about it and didn't just flip a coin.
Doesn't have to be acceptable to me.
If I don't like it, I can go buy a Mac or go with Linux.
That's not how I'd prefer the world to work, but I'm not at the controls.
-
It seems, to me anyway, that its now an accepted fact that some users will be "inconvenienced" when Windows is updated and or upgraded? But hay, we'll be right on that "after the fact".
MS can continue with their two builds a year thing, but as for me, it will be one build. I will not update till next fall.
-
i guess I would like to know what percentage of the user base experienced this problem. I remember years ago when a service pack was blue screening computers and people were up in arms that MS didn't test enough. Turned out that the ones who were bluescreening, all had a rootkit installed unknown to them. Once this was discovered, MS fixed things up, but obviously they aren't testing how their software installs onto computers in various degrees of brokenness.
-
-
Would it be an acceptable Risk if this build was sent to Industries and the same result happened. No it would not and it was not and never will be acceptable to release a Flawed OS To anyone especially when they were informed of this Problem 3 months ago and did nothing -nothing to fix it.
Windows 10 Enterprise LTSB 2019 "was" up on My Visual Studio, along with Windows 10 Business 1809 and Consumer 1809. So apparently it was acceptable to release it to Industry? If only briefly. They were all pulled when things went south for "some" consumers.
Quote