New Windows 10 Insider Preview Fast+Skip Build 18941 (20H1) - July 18 Insider
-
Perhaps...just perhaps...MS would like to find how, what, when, and where - via A/B testing - that the installation routines fail. That "could" be the reason that some of the Insider builds have issues installing for some users and not for others. That various configurations of hardware and software will result in various installation failures AND report back via that villainous telemetry WHAT happened to a particular hardware/software configuration.
That's certainly a valid point. But since MS lists this at #1 in Known Issues, I'm thinking some of their in-house testers may have encountered the problem. Also, the same thing happened to some Insiders (including me) with the previous build. They may have already had enough info to devise a fix, in which case they should have done before releasing 18941. Even so, I won't be surprised if the same bug exists in the next build and maybe even more after that.
-
-
You see, that is the point, it is kind of going in circles and that takes us back to square One. How can you test those Insiders builds if you cannot install them.
LOL...True, it "IS" a Catch 22. And, there is no way to know at what point the installation issues are resolved unless they are tested against (or until) failure. This isn't something that can be resolved without using Insiders (or, very undesirably, real world "Users") to actually test drive the installation and subsequent "fixes".
-
![]()
That's certainly a valid point. But since MS lists this at #1 in Known Issues, I'm thinking some of their in-house testers may have encountered the problem. Also, the same thing happened to some Insiders (including me) with the previous build. They may have already had enough info to devise a fix, in which case they should have done before releasing 18941. Even so, I won't be surprised if the same bug exists in the next build and maybe even more after that.
Undoubtedly they have encountered many issues in house. But, their in house testing cannot possibly duplicate the innumerable hardware/software configurations that exist in the wild. Hence, they most probably have tested/fixed/tested/fixed...etc...in house. At some point the beast must released into the broadest mix of configurations as possible...hence...us! And, that beast will just as undoubtedly find new victims...again...us!
Ahhhh, the circle of life...so to speak.
I rather suspect that through this process, what MS wants to know is - what still is causing installation failures and thus, remains to be fixed.
-
Forget unlimited software configurations being the issue here. Usually if Windows fails to install or upgrade is because of Windows itself.
-
-
LOL...True, it "IS" a Catch 22. And, there is no way to know at what point the installation issues are resolved unless they are tested against (or until) failure. This isn't something that can be resolved without using Insiders (or, very undesirably, real world "Users") to actually test drive the installation and subsequent "fixes".
That means we are also being "guinea pigs" for installation issues as well. I consider it to be going beyond the pale, if that is true on Microsoft's end. I find it very hard to swallow, because the way I understand it we are beta (or alpha) testers and in order to help MS in that regard the first prerequisite is to be able to install these Insiders builds without any issue. LOL! 
-
That means we are also being "guinea pigs" for installation issues as well. I consider it to be going beyond the pale, if that is true on Microsoft's end. I find it very hard to swallow, because the way I understand it we are beta (or alpha) testers and in order to help MS in that regard the first prerequisite is to be able to install these Insiders builds without any issue. LOL!
I agree, unless it's explicitly stated that the build is a test for new upgrade system. Then it's acceptable if something during upgrade is broken.
-
I agree, unless it's explicitly stated that the build is a test for new upgrade system. Then it's acceptable if something during upgrade is broken.
I agree in as much as it is well stipulated in the "Known issues" section the fact that one might not be able to install this upgrade because of some configuration issues hardware or otherwise (drivers etc..) related. Some sort of forthright warning...
-
I agree in as much as it is well stipulated in the "Known issues" section the fact that one might not be able to install this upgrade because of some configuration issues hardware or otherwise (drivers etc..) related. Some sort of forthright warning...
Yep, but since MS knows what hardware we are running, they should put blocks on those devices until they have resolved the issue... but then again, failed installs/upgrades helps solve the issue too.
-
Yep, but since MS knows what hardware we are running, they should put blocks on those devices until they have resolved the issue... but then again, failed installs/upgrades helps solve the issue too.
You are totally right again. Maybe this is asking MS too much or it is done purposefully, as you put it "but then again, failed installs/upgrades helps solve the issue too". LOL
-
-
They know about the problem and decided not to fix it before they released a new build. How can one go forward if the darn thing won't even install?
Obviously they know about the problem, but did they decide not to fix it or are they still trying to fix it? From my perspective, if 18936 refused to install, and given the Known Issue reported with both 18936 and 18941 I wouldn't bother to go forward. Logic tells me it wouldn't work. And ... I'm one of those who will try anyway, but not this time. Too much evidence to ignore.
You probably shouldn't try to go forward, because there's adequate evidence that it won't work. In the end, the decision is yours to make.
Quote