Windows cannot continue the update...

P

pmikep

Active Member
I don't know if this is a problem with NTLite or with later updates from Microsoft. But I just now tried to do a live integration of the August Quality Rollup into Win8.1. (This is on a working Win8.1 Pro 64 that had some removals via NTLite.)

When I shut down the computer, the gas gauge goes to 33% in the "Do not turn off" warning and then the computer reboots.

When it starts up again, it picks up at 34% and continues to 99%.

Then at the last minute, I get a screen that the Update cannot continue and Windows will roll back. (Or some phrase like that.)

My uneducated guess is that it's a logging problem - that Windows can't write to a certain og file?

I suspect that I would get the same message if I just double clicked on the KB itself and installed it outside of NTLite. (I'll try that after I post this.)

I had the same problem last month when I tried installing KB's using WSUS Offline Updater.

Integrating KB's after removals used to work. So the only two variables that changed (that I can think of) are new versions of the NTLite Removal Engine or newer updates from Microsoft.

I know I'm not being very exact in my description. I'll try to take a screen shot with my camera the next time it happens.

Anyone else getting this?
 
My moneys on the update itself. WSUS OU log file will show the install order and the bogey will be the last in the list.
 
I logged in as Administrator, disabled Comodo's HIPS, and manually installed the msi for just the latest Quality Rollup. (KB4512488)

Fail at the 99% point after reboot.

I can't get to logs easily because after the Fail point, Windows tries to roll back and then gets stuck in a loop. (I might be able to boot Linux from a CD and grab any log file that might have been written to if that will help troubleshoot.)

So it's either a (new) problem with Removals via NTLite, Comodo, or the update itself.

If nuhi wants to test, here's the Preset of my Live Removals.
 
There are issues with that KB. and Here Where possible try to have a spare partition/or space availible and manually install updates one by one, you will easily spot a bad'un. If they install ok and give no problems they can be added to your main system.
 
Last edited:
By my tests the safest way to keep windows compatible with updates is to do the removals before installing a cumulative update.

That is, on Windows 10 do the removals in a clean install.wim without any updates and then integrate the updates later. On Windows 7/8.1 integrate all updates except the latest Monthly Rollup and the latest .NET Rollups, make the removals and then integrate the rollups. Cumulative update will detect the components present and only update them.

Otherwise on a newer update it may be necessary to change some removals for it to be installed properly. Because of this the NTLite removal engine needs to fix and update constantly and it is always necessary to use the latest version of NTLite and rebuild the ISO or reinstall the image with the fixes constantly.

PS: On Win7/8.1 if telemetry is removed it is reinstalled with the latest Monthly Rollup. It's better to disable telemetry rather than remove it to keep it quiet if you want to keep installing updates every month.
 
Last edited:
I had forgotten that Rollups will install things that were not wanted. That's why I was using WSUS Offline Updaters curated Security Only updates.
 
"On Windows 7/8.1 integrate all updates except the latest Monthly Rollup and the latest .NET Rollups..."

Hmm ... I almost did it that way. But I integrated the .NET's first. Next time I'll try it your way.
 
The .NET's do not make much difference integrating before or after but as they are updated almost every month it is more coherent to leave to install them later (you can make a base ISO with updates and removals and then only integrate the latest updates each month). But I think there is no problem integrating .NET updates before removals.
 
You must log in or register to reply here.
Back
Top