Announcing Windows 10 Insider Preview Build 16188 PC and 15210 Mobile Insider
-
I'm looking forward to a
seamless flight. I hope my '
One click tweaks em all' files work!
Attachment 133493
By seamless flight I mean successful updated installation.....bug hunting and feedback commences after that.
-
-
If they dedicated 100% of time and effort fixing things, we'd never get anything new.
I agree, but first take care of bugs/problems we all have worked to identify then add the goodies.
-
My first download failed, and the second has been stuck at 96% for some time now.
-
Looking at the timing of these things it is probably too soon to get any fixes in the next build. These things take time. They probably will appear two or three builds down the line.
-
-
I have to agree wholeheartedly--we need to address some issues since that is what our feedback is about, IMHO. New items are fine but fixes are first and foremost.
I agree bug fixing should be a priority, but the problem is introducing new functions can interfere with past bug fixes, and so the problems mount ad infinitum....best to do as M$ appear to have planned, slowly feeding in new concepts.
-
... seems all Edge and integrating existing PDF stuff... I would have thought the "Changes, improvements, and fixes for PC" takes precedence over the "What’ New in Build 16188 For PC"...
Just a thought regarding where their priorities lie... Insiders that report problems are the ones that should be primarily addressed .. IMHO (as always)
You are absolutely right in what you say and I agree 100% with you! Is DISM working in this build? What about those DCOM errors in the Event Viewer? I'll install this build tomorrow morning (after 8 -10 hours).
-
You are absolutely right in what you say and I agree 100% with you! Is DISM working in this build? What about those DCOM errors in the Event Viewer? I'll install this build tomorrow morning (after 8 -10 hours).
I've personally got the odd DCOM error showing up in every build of Windows 10. They can easily be fixed but as they don't seem to cause any problems I just ignore them until a new build comes out and they get replaced by a different DCOM error :)
-
Because correction of bugs needs to be tested before signed-off... that can only happen when the fix is properly tested. why wait 'till October to find out that the "fix" was incorrect?
There was a tweet from Jason saying that not all issues would be fixed in the next flight, no matter what the number. I'm pretty sure the Outlook 2016 thing won't be fixed. I don't have it, but I'd think it's rather important.
-
If they dedicated 100% of time and effort fixing things, we'd never get anything new.
Nope, but we'd have one fantabulous OS with no bugs.
Actually, I agree with both sides . . . we need both bug fixes and new features. I think Microsoft has enough engineers to see to both, maybe.
-
-
Looking at the timing of these things it is probably too soon to get any fixes in the next build. These things take time. They probably will appear two or three builds down the line.
Agreed, Keith, although I hadn't thought of that before you said it. :)
Quote
