KB x64 (KB3194496)

I guess this update is problematic : it took a long time being referenced in the update catalog, but now it is non longer available.
Wondering about MS staff competence.

 

installed the cab on post #2 using w10ui automated script with no issues.

 

And so did I (successfully). Only problem, the amount of data to download.

 

LOL. Business as usual for Microsoft. We're all hamsters running on the hamster wheel as far as they're concerned.

 

as hamsters and guinea pigs i still prefer this model of faster updates and upgrades than win 8.1 and previous so will take the good with the bad as long as their are others out there to be the insiders while i lurk and decide whether to update/upgrade or not based on their pain points

 

I am having this issue on the normal build of windows 10 not the insider build. How do I fix this? I dont understand how.

 

You need to login to view this posts content.

 

I had SoftwareDistribution cleared down to install the previous Cumulative Update (KB3189866) and when it came to this one it downloaded and installed on the first attempt, although it did spend about 30 minutes accessing my C: drive at 100% before the dust settled. It looks like a previous update (before mid-September) is to blame for the patchy success of the Cumulative updates ever since.

Guinea pigs and hamsters? More like crash test dummies!

 

Obviously the WRONG team developed the update and now the CORRECT team is trying to develop a fix for it.

 

typical ms, get a brick layer to do brain surgery

 

˄˄
Microsoft are aware of the problem and are working on a fix. Instead of trying fixes yourself, wasting time and taking risks, it’s better to wait a little and then the update will go thru normally.

This is what I did last time there was the same problem.

 

I hade to use wushowhide.diagcab to hide the update till a fix is put out. Tired of the failing loop. I wish this update was never released when it was clearly having problems for insiders and now the gereral publice (non insiders). THey really nedd to do a lot more internal testing before releasing something like this from now on. Even the .221 build for mobile users has issues too.

 

What is not acceptable, is that for not skilled home users the installation of buggy updates is automatic and mandatory.

 

I agree that it is an unacceptable situation that a self-respecting company shouldn’t allow. You might have also expected that they’d have learned their lesson by now. And there was no hurry to rush out a half-baked update.

Nevertheless, the update though annoying, does no real damage to home user systems. It just sticks, and as I said above, you needn’t do anything, just wait for the fix.

Thus, without reducing Microsoft’s irresponsibility in any way, I also find almost equally incomprehensible the hysteria on the part of some users rushing to apply potentially dodgy fixes, thus risking to damage their systems themselves.

 

Simply true!

Just also simply true is: This Insider OS is still (early) Beta and should be handled from so called skilled users only. In reality, even any fully released OS (and Apps) are still containing bugs and more, there's nothing to be 100% correct! That's even more on any Test-Software.

That Updates are mandatory in Beta Testing, I would say, is still acceptable, just don't like that. And there should be a way to bypass that! The fact is, the developer of that Test-Software need to know the outcome of any new or changed modules etc., and that's one (of many) reason for the developer to give Pre-Release's free to test to a varity of user. There's nothing wrong with that. And, that's the price the Test-User has to pay for to get that Software for free use!

 

Having the same problem...settings says I've run through the loop *8* times. The first time I used the update hider it tried to install anyway, and it has ignored my "office hours" settings completely. It has tried to install whenever it wants to so far. I system-restored to 14393.187, used the Hide-Update program, un-hid it, then re-hid it, then rebooted, so we'll see if *that* helps any. So far, so good.

I've dropped back to the slow ring since 14393.0 and have remained on 14393.xxx, the commercial, non-Insider release of the OS. I don't understand why this .222 update was ever released to the Insider program when it was...because it was initially a beta update for 14393.187, which is *not* a beta version of the software and therefore not subject to Insider releases...then shortly after releasing it to the Insiders on the slow ring and after learning of the problems, it was released into the non-Insider channels...! The weird thing is, though, that 14396 has already been released to the Insiders channel, and the .222 update isn't needed and won't work.

Now, my wife's desktop, which is similar to my own, and not on the Insider's channel, got the .222 update and it installed fine for her, first attempt! Go figure...Sounds like someone at Microsoft pushed out this update early and on the wrong channels--because if it was really meant initially as an Insider update then a two-day testing period was not long enough--obviously.

Edit: Fixed it, finally! Downloaded the latest MediaCreationTool from Microsoft and told it to upgrade my Win10 installation to the latest...it did it all automatically, and when I was done I have .222.

 

Start installation from within Windows with an ISO standard AnniversaryUpdate and having Internet connectivity. At the beginning of the installation see if update packages are available, it will download the last 222 or whatever and use that to install the update package.

In conclusion we are in the 222 with everything we had at the end ...

(Occams razor)

 

I wasn't talking about the Insider OS which of course is beta software, but the regular commercial Windows 10 (which is still beta, lol).