Windows 10: KB3193494 meant to replace KB3189866 FAILS too!

Howdy,

A few days ago I posted a thread telling the problems I was having trying to install the Cumulative Win 10, Version 1607 Update (KB3189866) both through the Windows Update program and manually from the Windows Catalog Center Can't install KB318966 (Cumulative Update, Win 10, Version 1607)

Today I noticed that Windows Update attempted twice to update another Cumulative Update (KB3193494) meant to replace KB3189866. These attempts failed so I went to the Windows Catalog and tried installing it manually but that failed too.

Just curious if anyone else is experiencing the same problem again? *cry

Thanks and regards,


:)

 

KB3189866, KB3193494 and KB3194496 cause problem with Chrome and Firefox with authenticated proxy (SQUID)

Hi

I'm having problem with Chrome and Firefox accessing proxy authentication after KB3189866, KB3193494 and KB3194496 updates.

The first time I had the problem was with KB3189866: after installation and restart Chrome (Forefox too) was not able to connect to any website with error ERR_INVALID_AUTH_CREDENTIALS, but the problem is that the popup asking for credentials is not prompted.

I tried uninstalling KB3189866 and it worked.

During the following days I had to uninstall KB3189866 because it kept installing with every windows update check.

All this until last thursday (21/9) when KB3189866 disappeared from windows update and was apparently replaced by KB3193494.

When I wen back to my client with Authenticated Proxy, I found the same exact problem.

Uninstalled KB3193494 and all worked.

The last try was to activate Windows Insider Program-Release Preview and install KB3194496.

Now I have Windows 10 version 14393.222, KB3193494 IS NOT installed, KB3189866 IS NOT INSTALLED but I have the same problem: I cannot use Chrome and Firefox.

I already wrote on Google forums, but the issue is not only for Chrome, also for Firefox, and happened with all three KB listed before.

I have WIndows 10 x64 and the authenticated proxy of my client is Squid (dunno the version).

Thank you for your help

Best Regards

Paolo

 

Windows 10 Anniversary Update freezes at lock screen when waking from sleep

Here's my concern: KB3193494 replaced KB3189866 on 20 September 2016. If all were well with your initial upgrade to Win10, we'd expect to see KB3193494 already installed or offered to your computer today.

<QP>

We encountered a network transmission issue that affected update 3189866, published on September 13, 2016. The quickest way to address this issue was to reissue the update to all Content Delivery Networks. This new update package, KB3193494, includes the same
set of fixes as KB3189866...If you have installed previous updates [e.g., KB3189866], only the new fixes that are contained in this package will be downloaded and installed to your computer...This update replaces the previously released update KB3189866.

</QP>

Source:
https://support.microsoft.com/en-us/kb/3193494

That being said, good luck with the next cumulative update for Win10 1607!

 

On your other thread I said:

Well, now they have said something (a first?)

https://support.microsoft.com/en-us/kb/3193494

The two CUs are identical as far as fixes go. I (eventually) got KB3189866 installed and it looks like Windows Update is intelligent enough not to offer me KB3193494 when I check for updates. So no - I'm experiencing no problems at all. *Biggrin

@Brink has a 'News' thread for KB3193494, that's the one to watch for problem reports (the old thread for
KB3189866 has 28 pages of them!).
Cumulative Update KB3193494 Windows 10 build 14393.187 and 14393.189

 

Hi Bree,

I just saw your response so I did go to Brink's post and put a response on it.

Thanks and regards,

 

I'm of the opinion to file an injunction in federal court. Microsoft's claim to fame was making all hardware (that they certify) compatible under one operating system. Now they have failed. The injunction should bar them from releasing an update until it has been tested on all the machines that they certify. For instance, HP has every model they have ever made. For those models that passed, the upgrade should be tested by the manufacturer, then report back to Microsoft whether it succeeded or not.