Author Topic: Win 10 - cumulative updates seem to install, then roll back (Read 29473 times)

embeeusername · « **on:** September 30, 2016, 12:49:46 pm »

Three win 10 cumulative updates fail to install. Have done everything that seemed reasonably non-destructive to fix this without success. Do not want to refresh unless absolutely necessary. Current is Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194496), but the two previous cumulative updates had the same issue. Have tried uninstalling/hiding, but it keeps coming back and I've no idea how to ID which update(s) within the batch may be at fault. It reappears many times a day, appears to install, demands a restart, re-downloads (no issue with the downloading), goes through the entire updating process, then throws a can't finish error and rolls back. Completely stumped. Any awareness of how to deal with this? Specific logs to send? Computer otherwise appears to be working normally (though some MS apps install/update properly and some do not).

Thanks

Boggin · « **Reply #1 on:** September 30, 2016, 02:21:01 pm »

Open a Command Prompt (Admin) and enter -

dism /online /cleanup-image /startcomponentcleanup

This may take a while to run.

dism /online /cleanup-image /restorehealth

This one can appear to hang at 20% but will complete.

sfc /scannow

This one will tell you if there is still corruption.

embeeusername · « **Reply #2 on:** October 01, 2016, 04:11:11 pm »

Hi,

I had previously run all of the possibly relevant procedures in the most recent Windows Repair version. Chkdsk and sfc found no issues. I downloaded several hopeful batch files to no effect. I ran some MS diagnostic tools and the offline updates that I was able to find. Nothing. My update history for the last week or thereabouts shows the following failures to install: KB3194496 (5 times), KB3189866 (1 time), and KB3193494 (21 times).

I ran the procedures you sent and have quoted the results below. In short, nothing has changed. Any other Ideas?

[==========================100.0%==========================]

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

Boggin · « **Reply #3 on:** October 01, 2016, 04:21:33 pm »

You could use the Media Creation Tool to download the latest ISO and create bootable media and then do a repair install.

Use the Download tool now button in https://www.microsoft.com/en-gb/software-download/windows10

The latest ISO should incorporate those updates.

embeeusername · « **Reply #4 on:** October 02, 2016, 02:51:48 pm »

Still no luck. Media Creation Tool at https://www.microsoft.com/en-gb/software-download/windows10 tells me that the tool can't upgrade my PC because the language or edition are not supported by the tool. This is Win 10 Education V 1607 build 14393.105

Boggin · « **Reply #5 on:** October 02, 2016, 03:01:13 pm »

You'll probably have to contact MS about this error as I believe the Education build has been problematic.

embeeusername · « **Reply #6 on:** October 02, 2016, 03:23:44 pm »

Was afraid of something like that. Anyhow, the responses on this forum are spectacular. Thanks so much. Bet I don't get a relevant answer from MS - well - at anytime.

MB

Boggin · « **Reply #7 on:** October 03, 2016, 04:31:18 am »

Phone them up - problems with updates are free.

Xas1953NC · « **Reply #8 on:** October 08, 2016, 01:43:55 pm »

Hello, My wife's updated W7 to W10 computer successfully installed the cumulative update on the 29th of last month this being the initial update. Every day since then the history update file shows an attempt to automatically install it again with results indicated as failures. The update page indicates it is available for downloading even though it did so on the 29th. It appears to be looping even though the download is not required.
The same cumulative update was successfully downloaded and installed on the 29th on my W8.1 to W10 laptop and my W10 Desktop computer without further looping.

Boggin · « **Reply #9 on:** October 08, 2016, 02:40:06 pm »

Yours seems to be a different problem.

Usually Windows Updates repeat when they sense an incomplete install.

Go Start - type winver and press enter - if the updates are up to date then it should display as 14393.222

However, MS has issued a patch which may work but the hyperlink in this article refers to a download for Insiders.

Create a restore point then download from the link and then see if the problem continues.

I don't know if the patch is in lieu of the update or if it just facilitates a smoother install.

http://www.express.co.uk/life-style/science-technology/717778/Microsoft-Fix-Patch-Windows-10-Anniversary-Update-Install-Fail

This article was published on Oct 6th.

Xas1953NC · « **Reply #10 on:** October 09, 2016, 09:20:45 am »

Hello Boggin, Winver on my wife's computer is 14393.187 so it looks as if the KB 3194496 update did not take hold even though the update history for 29th of last month said it did. Her computer is not designated as an insider as she does not have a Microsoft account so the patch did not work.
It looks like we will just have to wait until MS sends an update to rectify the problem.

Xas1953NC · « **Reply #11 on:** October 09, 2016, 09:23:41 am »

Just one more thing, her computer each time shows download progress to 11% then stops.

Boggin · « **Reply #12 on:** October 09, 2016, 09:42:04 am »

If your wife is using a 3rd party antivirus program, try the updates with it fully disabled or uninstalled.

I use Norton Security and to manually install the Anniversary Update, I had to turn off both the antivirus and firewall aspects of it for the install to continue after the second reboot.

Xas1953NC · « **Reply #13 on:** October 09, 2016, 11:11:38 am »

Hello Boggin, I did think of turning off Avast Free prior to your suggestion but as I did not see the Avast icon rotating in the taskbar I thought it was not the cause of the problem. However, I have just followed your advice by temporarily turning off the Avast 3 shields and also exiting SuperAntiSpyware. This resulting in the downloading and installing of the windows update but during the restart Avast and SAS automatically kicked in again which resulted in the failure for the update to install. I have just thought of the idea that if I temporarily disable their activities by doing so in Autorun Organiser startup program perhaps the Windows update will succeed.

Boggin · « **Reply #14 on:** October 09, 2016, 12:38:25 pm »

Sometimes you have to uninstall them using their uninstallers.

When you turn Norton off, you can do it by degrees of time including permanent so there's no chance of it reinstating itself, but it sounded like you were making progress while they were turned off.

Xas1953NC · « **Reply #15 on:** October 09, 2016, 01:23:28 pm »

Hello Boggin, So far the update has now downloaded as it says installing update instead of downloading and the request to restart comes up. Disabling SAS and Avast Free prior to this by temporarily disabling their components in Autorun Organizer made hope they would not interfere. There was a 5% update then the computer did three auto partial restarts saying do not turn off computer.During the final restart I was told the update was rolling back as it could not be fully installed and upon completion both Avast and SAS were running automatically. I then decided to do an indepth disabling by using Autoruns 64 but was denied access to some of the Avast components. Avast does have a self protect process so perhaps that is why it it still active on a bootup. I think I will wait until MS come up with an antidote.

Boggin · « **Reply #16 on:** October 09, 2016, 01:41:02 pm »

I don't think the problem is with Windows but with Avast - or at least you will need to eliminate that as the cause by uninstalling it using its uninstaller.

Is SAS the Pro version - if it is then you may have to uninstall that as well.

Xas1953NC · « **Reply #17 on:** October 09, 2016, 02:03:57 pm »

Yes, SAS is the Pro version. What else is happening is that restarting causes all the taskbar icons to disappear into the box on the taskbar that looks like an inverted V. I have to either drag them back or in the settings select and switch ON the icons so something is switching them to OFF. Powering down and then rebooting up retains the icons on the taskbar. This has been happening before the current attempt to resolve the update issue.

Boggin · « **Reply #18 on:** October 09, 2016, 02:13:16 pm »

See if you can get the update problem resolved first and then perhaps the Repair Icon fix in WR may sort that out.

Xas1953NC · « **Reply #19 on:** October 09, 2016, 02:21:03 pm »

OK. The inverted V box is called the Overflow. something else I just learned late in life!

Boggin · « **Reply #20 on:** October 09, 2016, 02:26:03 pm »

Well that makes two of who have just learned something - I've always called it the icon arrow

Brama · « **Reply #21 on:** October 11, 2016, 08:37:15 am »

Three.

Boggin · « **Reply #22 on:** October 11, 2016, 08:44:35 am »

The thing is that if I tell someone to click on the Overflow they may end up looking for it in the bathroom

Boggin · « **Reply #23 on:** October 11, 2016, 04:03:18 pm »

@ as1953 - I'd inadvertently removed your post but thought "sinkronisation" was a good one

Xas1953NC · « **Reply #24 on:** October 11, 2016, 04:24:52 pm »

Ta, I thought perhaps others would tap into the conversation....As it happens I have just downloaded the latest updates into my wife's computer and three went in but the latest cumulative one failed so that makes two of them.