Microsoft has just re-released a cumulative update that dropped two days ago with an additional fix that mends a problem with download sizes. According to Senior Program Manager Brandon LeBlanc, those who installed the cumulative update when it was originally released will not get this fix.
The new update is KB3176934, which is different from the Cumulative Update that was released the other day KB3176932. Both updates bring the user to 14393.82, however the newest update includes an additional fix not found in the originally released update.
@GoodThings2Life @vitorgrs @zacbowden @TheRichWoods Ok, if you got KB3176932 on Tues, you will not be offered KB3176934.
— Brandon LeBlanc (@brandonleblanc) August 19, 2016
Those of you who installed the original update and want the new fix will likely have to wait for a newer Cumulative Update to roll around, as it appears this update will not be applied to those already running 14393.82. This newest update is now available in the Release Preview and Slow Ring on PC, and the changelog will show up in the Feedback Hub soon.
Reader comments
Microsoft re-releases Windows 10 build 14393.82 for PC Insiders with additional fix
I think what we have to accept is this, Windows 10 will always be beta, always. A quote from forbes, (the highly respected world news) in an interview with a former employee of MS, " Ms has some very talented programmers, not common but they do exist, the problem is the entire company is totally focused on developing an absurd number of new features and products, giving them, (the programmer) completely unrealistic deadlines and them ship software on those deadlines no matter how half assed or buggy it is. This has perpetuated into a duct-tape culture that refuses to fix problems and instead rewards teams that find ways to work around them. The talented coders are stuck working on code that, at best, had to deal with multiple badly designed frameworks from other teams, or at worst work on code that had been scrapped. New features are prioritized over all the most system critical bugs, and teams are never given time to actually focus on improving their code. The only improvements that can happen must be snuck in while implimentating new features.
As far as Ms is concerned, all code is rubbish and the only thing that matters is if it works well enough to be shown at a demo and shipped. Needless to say I don't work there anymore, I couldn't bear the culture."
So there we have it. We have the free trial as in 10 on pc and mobile which will probably always be a bit of a mess. We have no control over our devices which is rather sad , other than move on which personally I've almost reached that point. Such a pity but I simply can't see this ever being a top notch system which it richly deserves to be.
Hmm....
Disgruntled former employee giving up life in modern society for life in a log cabin in the woods, perhaps?
Or...
A glimpse into the MS Shop of Horrors?
Hmmm...
If only there was some place, a forum maybe, where people could discuss things that are completely unrelated to this article.
Im sorry for the off topic, but I have a completely unrelated question. I am Dutch but have my PC language set to "English US", which allows me to use Cortana whilst my region is still set to "The Netherlands". When, however, I do this on my mobile phone, Cortana is not available. Is this because this really isn't available for mobile yet, or am I doing something wrong? Please note that I do NOT want to set my region to anything else but "The Netherlands".
Thanks in advance for any reply concerning this problem.
I'd be interested to know if the people with Settings/Power button problems have low amounts of RAM, SD cards or slow processors in their affected machines. I have an original Surface Pro that runs 14905 without the power and setting problems, but an 18-month old HP Stream 8 crashes back to the start screen from most Settings options and must be turned off with a long push of the hardware button and a slide-down movement. It may be a little more forgiving in Tablet Mode than in Desktop, but it's still not working as one would expect.
One big thing broken in the newest build is that the power/shutdown button from start menu is not working.
That was stated by Microsoft for you to read before you download the update. They also listed a work around for it.
So much of XBOX.....
Hey Microsoft re-release Windows 8.1! Everything worked!!!
I like Windows 10 but it still feels sluggish to me but Windows 8.1 flew fast oddly enough. I miss the old Windows of yesteryears lol.
Posted via the Windows Central App for Android (LG V10 or Nexus 5x)
Everything? It also had less features...
It had more features like usability as a tablet.
@JohnStrk
Update 2
How about re-releasing mobile 0.67 AU with some fixes such as sim2 bug, panorama, black & white picture glance screen, microSD card bug and battery drainage....?
This!
Thumbs up to u for this comment
The restart/shutdown and Cortana issues were known and documented. Expect even more instability for a while. This is part of the path for early beta access.
Beta test you mean on builds that's already public? Some issue still left unfixed like Cortana which is a user visible feature.
I've had no issues with Cortana, well, no worse than she's always been, sometimes great other times non-responsive, depends a lot on your net connection. Most of the folks in this thread, clearly seem to be talking about the latest RS2 builds, it's documented that there'll be issues with Cortana on those builds.
It amazes me how many so easily mix up or don't understand the differences between the build branches, & the branches for Mobile Vs PC, there really is quite a lot of dumb people (not speaking of you), it's been explained so many times, yet some still mix-it-up or don't understand.
My experience with Cortina is based on currently RS1 which is quite buggy where crashes tends to happen especially when using voice. Because of this, it renders Cortana to be almost useless when it comes to voice commands. For now she's only good for reminders and other stuff.
About the build branches, I always noticed of people indeed getting mixed up for whatever reason. The Insider Program has been running for more than a year already and there is still a confusion about it.
This is why I highly don't recommend and encourage people to be on Insider unless they really, really want to beta test and ask sensible suggestions or report every bugs no matter how trivially small it is. Insider Program isn't for just getting the latest and the greatest, thats not a point. I virtually never ask somebody to get Insider builds, even to my fellow geek friends unless they do want to really contribute. It is not for everybody, not even for most enthusiast.
That sometimes gets me thinking that we shouldn't make people encourage to get Insider builds or even stay unless for reasons above. We can still send feedbacks even with production/RTM builds on Feedback Hub. On the other hand Microsoft needs to really do something and make feedbacks really discoverable like live feeds of feedbacks and trends every day, week and month. There are tons of good feedbacks that are left undiscovered, thus low to no votes, while for whatever reason some vague feedbacks or some that are not too sensible manage to gets trending. Most are good feedbacks but many awesome ones too are buried on big wall of text.
Posted from alternate universe
+1
With regards to Cortana, can't say I have issues that are as bad, but agreed with everything else.
Cheers.
I wish my Cortana works properly as yours. This what's frustrates me most since the issues are not too consistent regardless of devices. This makes bug tracking really hard and even cause accusations in fellow community like here. All we left to do is to post the issue on Feedback Hub and cross-fingers multiple times.
[Deleted because of duplicated caused by WC app]
Every single build is public and official
Yeah, sorry what I mean is it a production/RTM/non-Insider/non-beta build or Insider builds.
He is taking about the new RS2 build
Can't access power options with this build. No restart. Have to shut down using power button. Terrible.
This is listed in the known issues. Right-click the "Start" button or Win+X for now.
Slightly (un)related, but this latest build for mobile has a few bugs. Won't mind if it gets re-released too. Any body else notice Cortana not speaking (responding) on this build & a very buggy outlook calendar? Lumia 950. N.B. And yes, I've recorded these bugs in the appropriate feedback forums.
My Cortana kept crashing too especially when launched using voice. This is been an issue even several builds before. Still same buggy one, idk why certain issues kept getting broken while other gets fixed, regardless of same device.
Keep complaining about things that are known issues in a Fast Ring Insider Redstone 2 build????
Eh, I didn't mean RS2 at all. To clarify I'm not even on Slow Ring, I have no plans going to Fast Ring yet anytime soon, especially this early. I'm talking about RS1, the same build number mentioned in this article.
Thanks for letting me know that this actually an issue on Fast Ring too, thoug mh not surprising because it's a fast ring, which is why I'm not on that branch. Sorry for not being clear.
I second that; hope they're quick with the next release to fix the major bluetooth issues...
I'm assuming you speak of the fast ring... Cortana was listed as having an issue with her voice, do no singing, jokes or reading texts. There are a few other issues but Cortana was on it as well. It was expected
Cortana problem is a known issue.
Why would Leblanc re-release the same build while having dinner and confuse users. If you already installed this build on your phone, you wont get this build again. but this build has a fix for an issue.. Very confusing Microsoft. Why can't you release .83 or something?
This update is for pc not mobile
You can uninstall the older update, reboot the machine check for updates and get the newer update.
Posted via the Windows Central App for Android
How does that build or those builds compare to 14905 which is waiting to be installed on my PC?
14905 is a fast update preview of Redstone 2 which is as rough as Redstone 1 was in the early days of the build.
Posted via the Windows Central App for Android
That's not true stop putting out lies
Fails to load on my PC which in itself is all you need to know, no issues with previous builds even towards the end when they popped out almost daily so maybe its not a complete untruth probably for the Mobile and PC versions. It certainly broken things that previously worked on my phone is definately reminiscent of the early redstone 1 updates but that is to be expected its a new development cycle.
Most Certainly not...!
Run dude run
Bit silly to still be in Fast Ring now that RS1 has been in Production for almost 3wks;
It was inevitable that Fast would switch from a stable branch (14393), to the latest bleeding edge unstable branch.
By all accounts, the early builds of RS2 aren't as bad as RS1 was, but that doesn't mean it'll be all smooth sailing.
Time will tell how bad...
If your "PC" must be reliable at all times (i.e. your primary workstation), then you'll need to go back to 14393.xxx.
Woops!
To the the author -
Note that you don't DROP software release. You release a build to production/public.
********
Just for your info (from dev pro):
Each build takes enormous team effort across many teams: dev teams, qa teams, various business units and holders. Usually all teams work under very tight deadlines to meet the release schedule.
Each build goes through many phases during the lifecycle prior release.
In addition any new changes have be be sync across many different dev branches.
*******
In this light -
Please stop using inappropriate words. We need to pay more respect and appreciate bit more what MS is trying to achieve.
********
Advise -
Next time why don't you DROP your pen and think about bit more what you are going to write.
It's slang.
Gratis on the most obnoxious post I've read in this forum ever.
Try Inappropriate, not unappropriate. Now drop your phone cause you suck.
The author forgot to mention the buttons, too. Each developer had to press buttons... many buttons pressed many times before this release could be gifted to us.
Seems ia_win pressed a few people's buttons here, also :D
You went full retard, man. Never go full retard.