Jump to content

Users Start Reporting Installation Issues with Windows 10 Update KB3194496


Batu69

Recommended Posts

KB3194496 causing problems on Windows 10 PCs

users-start-reporting-installation-issue

   Another update, another installation problem

 

KB3194496 was officially released to retail users earlier today even after insiders complained of installation issues, so it’s no surprise that many more PCs are hit with the same problems.

Users who rushed to install this cumulative update are now reporting the same bugs as with the previous releases, explaining that on some PCs, it fails to install successfully with an error saying just “Undoing changes.”

“Fails to install for me, tried 3 times. Every time I get an 'undoing changes...' screen during the reboot. I'll just wait if there'll be another update to fix that,” one user explains on Reddit.

“I keep getting Undoing changes, couldn't install updates. I have tried troubleshooting windows update. I get the following error is event viewer: 0x800F0922 and a few AppReadiness errors,” another one added.

No workaround available

For the moment, there is no workaround available, but what’s important to know is that the number of complaints coming from users who installed it is substantially smaller than for the previous cumulative updates.

Most likely, Microsoft is already looking into these reports and if a fix is necessary, it could be released in the coming weeks. A new cumulative update should land on October 11 when Microsoft rolls out Patch Tuesday updates, but it remains to be seen if a different one could arrive in the meantime.

What’s also critical to know is that there were users who claimed that KB3194496 got stuck at 45 percent during the downloading process, a bug that was already experienced by some people with previous cumulative updates.

This time, however, patience is really a virtue, and if you wait long enough, the process should complete successfully and luckily, the update would install smoothly too. There are only a few reports pointing to this bug, so it’s probably just a minor issue that should be resolved in the next cumulative updates.

Article source

Link to comment
Share on other sites


  • Replies 12
  • Views 1.3k
  • Created
  • Last Reply

Here also this ;  " a few AppReadiness errors "  !

But these are errors in eventlog ( id=214 and id=10 ), they appear after every reboot .

The update is installed , only these annoying " AppReadiness-errors "  , dont know if its harmfull..............:(

Link to comment
Share on other sites


If I dont look in the eventlog ,then I dont have problems and errors also.............:rolleyes:

Your eventlog is clean and does not show any errors , I guess ?

Link to comment
Share on other sites


Are these AppReadiness-errors causing severe problems ? I dont use apps and dont have MS-account .

Dont know what to do with error id=214 and id=10..........:rolleyes:

Link to comment
Share on other sites


Airstream_Bill

I finally got it.  It took awhile how long I really do not know.  The update stalled at 45% then I rebooted and let it start over and it Stalled at 79%.  I just left it alone for a couple of hours and when I checked it again it had gotten it.  I told it to install and then rebooted.  Getting to be a pain if one just wants to download it and get it over with.  I think they are pulsing the updates to ones computer.  ???? 

Link to comment
Share on other sites


Old problems linger with new Windows 10 Anniversary Update, build 14393.222

The drive freezes, install failures, and network lockups continue, but many little bugs are finally gone

Last night Microsoft released KB 3194496, the latest cumulative update for Windows 10 Anniversary Update, version 1607. Those who are able to install it find that their build number (type winver in the Cortana search box) stands at 14393.222.

 

This is the seventh cumulative update for Win10 Anniversary Update in the past eight weeks. With all that patchin' goin' on, you might think Win10 AU would be pretty well plugged by now. Many folks would disagree.

 

If that KB number looks familiar, it's because the patch was released to the Insider Preview ring on Sept. 27. Earlier this week I talked about how the patch was misidentified in the mainstream patch. Now it appears the patch has been released to the world at large in spite of reports of significant problems with the Insider Preview release. For example, poster JVJerman on the Microsoft Answers forum said:

I have three machines, and this update has failed on each of them multiple times. It goes so far, then says "we cannot install update" and reverses itself. Am good at following directions, however cannot find any definitive advice on this one. Now what???

The problem report was repeated in a different thread on the Microsoft Answers forum, where poster CrazyKats said:

 

I'm also having an issue with this Update. I'm on build 14393.187. This update fails during install for me and pops an 0x800736cc error.

John Wink, the Microsoft avatar who tackles such issues, started asking for copies of installation log files on Sept. 28. Apparently they weren't deemed dire enough to prevent Microsoft from unleashing the cumulative update on the world on Sept. 29.

 

Predictably, there now have been reports all over the web that KB 3194496 refuses to install for normal people -- the ones who aren't in the Release Preview ring. For example, poster Maxdec94 on Reddit says:

Third time, no dice. This update really doesn't want to install for me. Event manager shows error code: 0x800F0922.

The Windows 10 update history page lists dozens and dozens of fixes in this patch.

 

One bit of advice: If it looks like the installer is freezing, wait a bit. That bug was supposed to be fixed in the last cumulative update, dated Sept. 13, and many people report that if they simply wait at 45 or 90 percent for 20 or 30 minutes, the patch installer will sort itself out.

 

Among those users who can get the update to install (it proceeded fine on my test machines), some old problems still haunt the fix.

 

One is the continuing problem with freezing and randomly disconnecting external hard drives, which I discussed on Aug. 4, again on Sept. 13, and again on Sept. 15. The problem is still there.

 

Another is the cumulative updates' infernal tendency to change settings and muck with taskbar icons. The updates aren't supposed to touch settings, but the track record shows otherwise.

 

A third big bug affects the creating and renaming of folders on a network share. I talked about that problem on Sept. 15 as well. The bug is a showstopper for many network admins.

 

Until Microsoft fixes those three big bugs, I continue to recommend that you actively block the Anniversary Update. Based on reports from readers on AskWoody.com, Microsoft has accelerated the rollout of the Anniversary Update; what was a trickle has become a flood.

 

Version 1607 isn't ready yet. If you want to use Windows 10, stick with the Fall Update, version 1511, until these big bugs get squashed. Perhaps the eighth time will be the charm.

 

Source: Old problems linger with new Windows 10 Anniversary Update, build 14393.222 (InfoWorld - Woody Leonhard)

 

Win10 Anniversary Update 14393.222 slays many small bugs, but three biggies remain (AskWoody.com)

 

InfoWorld - Woody on Windows

Link to comment
Share on other sites


  • Jordan featured and unfeatured this topic

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...