Windows 10: Cumulative Update KB3194496 for Windows 10 PC Build 14393.222

I wonder how many responses could be given and processed in those two days the update was given to the insider rings...

 

I agree Scottyboy, It seems like the right hand doesn't know what the left hand is doing at MS at the moment.
I've been on the Insider Slow Ring for the past few months and this latest CU was publicised as being for Insiders on the Slow and Release Preview rings. I kept manually running check for updates and recived nothing, I lowered my Insider level to Release Preview Ring and received this CU almost immediately. Now it's obvious that everyone is receiving it which is fine but why even have a Release Preview Ring if MS aren't using it as originally intended, ie so it could be tested for around a week or two before it was finally released.

 

It was offered to me, downloaded, installed but did not take - system was rolled back.

I'm no longer in the Insider Program - Fast, Slow or Release Preview.

I checked via Windows Update MiniTool - showed cumulative update available, hide it then tried Windows Update via Settings - didn't appear - said my system was up-to-date.

Weird!

 

Nobody? New error 10/214 in event log

 

What does that error refer to?

 

Yeah, its out for everybody now. Not much time for release preview insiders to find any bugs.

 

and both my surface 3 and my HP Envy failed to install it and roll back, first time it happens. By the way both not under Insider program.

 

Just got it on my non-insider boxes and laptop. Maybe there's something in it Microsoft decided couldn't wait until Patch Tuesday.

 

Insiders got it Tues. 27th , now on 29th everyone is getting it..........

some here are having issues on the Surface .....I have not tried mine yet

Microsoft Community

 

Yes I have this problem on release preview. I and several others posted about the problem on the insider hub so why the hell was this released to the public.

 

I edited my earlier post, but my 14393.187 upgrade to 14393.222 failed at 99%...*Wink Heh--amazing...*Wink It simply failed and rebooted back into 14393.187 without a problem. BTW, I've noticed that when an update like this fails that Win10 will *not* try to force a repeat of the failed upgrade *unless* the user actively clicks the "Check for Updates" button on the Updates Tab in settings--at which time the automatic nix on the failed update will be overridden and the same update will try again to install--and the same thing will happen, most likely. So if you don't want the failed update to automatically reinstall, simply do not click on the "Check for Updates" button and it won't--but to repeat, this will only happen when the system has automatically restored the previous build of Windows when the installation fails. If the system BSOD's or in some other way crashes and does not restore the previous version then it might very well continue to try and install the failed update again automatically. In that case only a system restore can get you out neatly.

Note: apologies...I just found out the hard way that this cumulative update does not work like every other flight upgrade I did during the two years when I was actively involved with the Insiders program (still am, but now on the slow ring to take an extended break.) I had to reboot to check something else out--and wham! The update had already loaded and I went through the same thing *again* despite the system having automatically restored to 14393.187--and I am now going back to change my "office hours so the consume most of the day...*Wink Sheeesh...not sure what is going on @ Microsoft these days!

This whole thing with respect to this build is goofy in the extreme--as 14393.187 is *not* an Insider build in the first place--it is an official release build! So *no* Insider updates should be coming down the pike for 14393.187 at all, imo. Only release_level updates should be applied to 14393.187! I think Microsoft has become a bit confused with its build numbers! Too many builds are in the wild at the same time--so many, in fact, that even Microsoft is becoming confused as to what a release_build is and what an insider_build is! Good grief, for release builds like 1607, no beta software should be released at all for that build!

They have already released Insider build 14396...which is where Insider cumulative beta-software updates should apply!

 

This is the third in the row when after succesfully updating shutting down computer led to BSOD with "irql less then equal" message.

 

Microsoft Community

On the 3rd page of that post , they say they identified the issue yesterday and the appropriate Team was working on the fix.... so I guess they think it is fixed ? One computer here had a black screen for about 5 mins after the reboot but I just waited patiently and it eventually came up as normal.


KB

 

Hi Guys,....


I am not an insider here, but did receive the Cumulative update on two home computers with in the past hour.

Installed with no problems on both computers, but I was a little nervous, when the update hung at 90 %, for what seemed like a long period.

Currently at 14393.222

And I understand this has probably been posted, but this is what it fixes:

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Improved reliability of the Windows Update Agent, shared drives, virtual private network (VPN), clustering, HTTP downloads, Internet Explorer 11, Hyper-V platform, multimedia playback, and Microsoft Edge.
• Improved performance of push and local notifications, Hyper-V platform, and some social media websites using Microsoft Edge.
• Addressed issue where mapping a drive from an elevated command prompt doesn’t work with administrator credentials.
• Addressed issue causing movies that were ripped using the transport stream (.ts) format to play without sound in Windows Media Player and the Xbox One Media Player app.
• Addressed issue causing the Movies & TV app on the Xbox to stop working when attempting to play content that was just purchased from the Store.
• Addressed issue where ActiveX can't be installed using the ActiveX Installer Service (AXIS) in Internet Explorer 11.
• Addressed issue causing “Print all linked documents” to not work in Internet Explorer 11.
• Improved reliability of downloading and updating games.
• Addressed issue preventing some users from changing the default download location in Windows 10 Mobile.
• Addressed issue causing unnecessary notifications about fixing Microsoft account in Windows 10 Mobile.
• Addressed additional issues with multimedia, Windows kernel, Windows shell, enterprise security, storage file system, Remote Desktop, core platform, Hyper-V platform, Windows Update for Business, display kernel, near field communication (NFC), input and composition, Bluetooth, Microsoft Lync 2010 compatibility, Windows Storage API, app registration, Trusted Platform Module, Group Policy, Internet Explorer 11, virtual private network (VPN), BitLocker, wireless networking, datacenter networking, Cortana, PowerShell, Active Directory, connection manager and data usage, Access Point Name (APN) database, Microsoft Edge, Windows Recovery Environment, file clustering, Universal Windows Platform (UWP) apps, audio playback settings, DShow Bridge, app compatibility, licensing, cloud infrastructure, domain name system (DNS) server, network controller, USB barcode reader, and Adobe Flash Player.

For more information about the complete list of affected files, see KB3194496.

 

I posted earlier that the reason for the "insider" rather than general focus of this update may be to gather telemetry - a head count on insiders running 14393 - if they are eligible to receive this update then they are presumably "happily" running slow or Insider preview ring versions.

If they are Insiders on 14393, and ineligible for the update, then there is a likelihood that they have remained Insiders, but have opted out of fast ring build updates for a time, and presumably have reverted to the official 1607, while the recent fast ring builds are being rejected as unstable, or unusable, with the deadline for the builds to timeout being the 1st/2nd October.

This might have been the case for me and Berton as my thread in the Insider forum details, had we not found a workaround.