Microsoft Confirms Windows 10 Cumulative Update KB3194496 Installation Issues

[Batu69]

A fix is being developed, a company official says

   Microsoft being Captain Obvious once again

 

Microsoft rolled out a new Windows 10 cumulative update for PCs running version 1607 (Anniversary Update) and just as we reported yesterday, there were plenty of users who experienced installation issues.

In a post on the firm’s Community forums, Microsoft engineers confirm the installation problems and explain that the team is already investigating and developing a fix.

“Investigating”

There are no details as to when exactly this new cumulative update fix could be released, but it’s worth noting that Microsoft itself says that there’s no point in trying to install this cumulative update because it’ll keep failing anyway.

“Teams have dug into this issue and do believe the cause has been identified. The correct team is developing a fix/workaround and once we have the full details, we'll be posting that information. For your affected machines, there's no need to keep attempting the install. It'll keep failing. In the mean time, hold tight! We're all over this and will keep sharing information along the way,” Microsoft says.

Several company engineers have already joined the discussion thread on the Community forums, asking for more details on the problem, so it’s very clear that the firm is actively investigating the problem.

What’s more frustrating, however, is that this cumulative update actually experienced the exact same issues when being tested as part of the Windows Insider program, but Microsoft shipped it anyway. This is a bit odd given the fact that the previous cumulative updates also had problems installing on a number of computers, so Microsoft should pay more focus to testing these updates before rolling them out to all PCs worldwide.

In addition to this new cumulative update fix that should land in the next few days, Microsoft is also expected to release a new one on October 11, when the company is also shipping Patch Tuesday fixes for all Windows computers. CUs for the original Windows 10 version and for November Update should also go live.

Article source

[Pete 12]

I hope they will fix these annoying errors of AppReadiness id=214 and id=10 also !

Never had these errors before ,until latest update...............

 

We dont use much apps and all with local account , but you always want to have your eventlog as clean as possible .

[voman]

Installed smoothly on both my desktop and notebook.

[pc71520]

Why M$ does Not adequately Test these Updates

Before causing such a MESS?

[Pete 12]

I think they do , only after each update a lot of severe problems for many people , so they test, appearently, not deep enough............

[mikie]

sOne of the problems with insiders is many have tired of reporting problems as no fixes come their efforts.  Only gives Microsoft a messed up % of ultimately how many users might be affected by a particular problem.. Microsoft is allowing for some acceptable % of problems to rush things out.  Even a small percentage can affect a  'whole bunch'  of computers.

[Karlston]

In 2014 Microsoft sacked their QA people, a group of experienced testers who kept updates (relatively) problem free.

 

For Windows 10 they introduced the Windows Insider programme, shifting the testing, bug finding and bug reporting onto those enrolled in the programme. But this idea has a number of problems, proven by a horrible history of buggy Windows 10 updates and fixes. This article is good...

 

6 things wrong with the Windows Insider program

 

And then there's the inherent problem with bundling updates into one, increasing the chances that a cumulative update will contain at least one major bug.

[SPECTRUM]

no issues here.

[Pete 12]

" no issues here. " ...........sweet dreams

[jenyco2]

hello

 

Si la mise à jour ne passe pas avec comme message d'erreur au redémarrage: Impossible de terminer les mises à jour. Annulation ...
et donc qu'à chaque redémarrage son téléchargement recommence et recommence encore, encombrant particulièrement le réseau local, voici ce qu'il faut faire ( mise à jour offline ) :
---
Solution qui fonctionne "à tous les coups" pour la mise à jour du KB3194496 :
---
1 - Il faut utiliser une clé USB d'installation de Windows 10.
2 - Y copier le KB3194496.cab (renommer ainsi car le nom du fichier téléchargé est très long).
3 - Démarrer sur la clé et passer en mode Dépannage puis Invite de commande

Lancez la commande suivante (modifier les lettres disques selon votre machine):
DISM /Image:C:\ /Add-Package /PackagePath:F:\KB3194496.cab /scratchdir:C:\TEMP

Remarque :
1 - Le disque C: est le disque ou se trouve Windows.
Si vous avez plusieurs disques en ligne il est bien possible que ce ne soit pas cette lettre donc faire un dir sur les disques présents pour trouver le bon disque
2 - Le disque E: correspond à la lettre de la clé USB.
Si ce n'est pas cela faire comme précédemment pour "découvrir" la lettre de la clé d'installation ou d' ailleurs se trouve le KB3194496.
3 - Si vous avez une erreur à cause du manque de place créer un répertoire TEMP qui sera utilisé par scratchdir

Une fois la commande DISM démarrée cela durera environ 3 à 4 minutes ... C'est un peu long quand on attend !!!
A la fin si tout s'est bien passé redémarrer la machine.
Exécuter CMD ( en mode administrateur ) puis Winver.
La version devrait être 14383.222 et Windows Update ne devrait plus vous redemander sans cesse la mise à jour.

 

in English via Google:

 

If the update does not happen with such error message reboot: Unable to complete the updates. Cancellation ...
and so that each reboot download it again and again again, particularly bulky local network, here's what to do (offline update):
---
Solution that works "every time" for the update KB3194496:
---
1 - You must use a USB drive to install Windows 10.
2 - Y copy KB3194496.cab (rename as well as the name of the downloaded file is very long).
3 - Start the key and enter Troubleshooting mode and Command Prompt

Run the following command (change the letters disks depending on your machine):
DISM / Image: C: \ / Add-Package /PackagePath:F:\KB3194496.cab / scratchdir: C: \ TEMP

Note :
1 - The C: drive is the drive or Windows is.
If you have multiple line drives it is quite possible that this is not the letter so do a dir on these discs to find the right disk
2 - The disk E: is the drive letter of the USB drive.
If it does not do this as above to "discover" the letter of the installation key or elsewhere is the KB3194496.
3 - If you have an error due to lack of space create a TEMP directory to be used by scratchdir

Once the DISM command started it will take about 3 to 4 minutes ... It's a bit long when waiting !!!
At the end if everything went smoothly restart the machine.
CMD Run (in administrator mode) then Winver.
The version should be 14383.222 and Windows Update will not ask you again constantly update.

 

@+

[dac]

_{Installed on both desktop and laptop, no issues}

[wacm1979]

Well I admit that this update installed okay on my units but I believe should do some thorough testing before sending these updates out like that. Especially as things are going cumulative on updates across Win 7, 8/ 8.1.