Bork Tuesday, Any Problems Yet?

Patchday issues with updates & WSUS (September 11, 2018)
https://borncity.com/win/2018/09/12/patchday-issues-with-updates-wsus-september-11-2018/

 

So should one try to avoid Win 10 KB4457128 somehow? How?

Or is update with Check for Updates OK?

 

Why? You do want to have the fully patched machine, don't you?

Yes, if you find the update in the list of installed updates, run Check again and it will install properly this time with rebooting. You're done.

 

Just that people seem to be having issues.

 

As far as I'm aware, the problems are limited to a two-time needed installation not with the update itself.

 

OK, thanks.

Hasn't been offered automatically here yet, on two machines. Will wait and maybe 'Check for updates' later, after imaging, just in case.

 

Make a backup with macrium reflect, make sure you have macrium recovery boot option (even better if it's on a usb, if the Windows 10 PE files are on internal drives then if something bad happens with the drive(s) you won't be able to boot into the macrium recovery)

For me, taskbar > start button > settings > update & security > windows updates > check for updates button does not show new version updates, you have to go here https://support.microsoft.com/en-us/help/4018124/windows-10-update-history, find the update you want, and then go to the bottom and click Microsoft Update Catalog link, from there you want Cumulative Update ... Windows 10 version 1803 ... x64 , so that would lead you to here: https://www.catalog.update.microsof...updateid=eab1a4bc-7207-4730-9370-a5869908cd56 (there's no download button, it's on the previous page) And if something goes wrong, you plug in the usb, boot into the macrium recovery environment and restore from your boot drive image that you made before installing the update, usually takes less than 10 mins if you have Rapid Delta Restore enabled (not on free version)

 

Exactly what happened in my case.

I would state at this point if anyone received the 1803 cumulative update without a reboot request after download installation completed, the update was never fully installed.

 

Another theory in regards to this double KB4457128 updating business on Win 10 1803 is the VBS/HVCI element. This update did include security updates to Hyper-V. Did everyone where this activity occurred have VBS/HVCI enabled?

I have wondered about the advisability of having VBS/HVCI enabled during Win update activity.

 

I updated my Asus 32-bit tablet last night. The Cumulative update only happened once and it took a long time to install. No reboot was requested. I clicked Check for updates several times but there was no second Cumulative update. Maybe 32-bit Win10 is different.

 

Yes, I think I read that the Servicing Stack Update was a prerequisite for the Cumulative Update.

 

@Reality,
I edited my yesterday's reply regarding Microsoft Office 2010.
It is very well possible that the 32-bit version of Microsoft Office 2010 is installed on that 64-bit Windows 7 system.
The 32-bit version is the default when Microsoft Office 2010 is installed.
If the 32-bit version of Microsoft Office 2010 is installed on that 64-bit Windows 7 system, you would need to download the 32-bit version of the update from Microsoft Download Center.
See the full edited post for all details.

 

WOODY ON WINDOWS
Error 0x8000FFFF in Win7? Phantom patch for Win10 1803? There’s a solution.
September 12, 2018
https://www.computerworld.com/artic...m-patch-for-win10-1803-theres-a-solution.html

 

Yes, on one machine I had an auto install of the Cumulative Update KB4457128 yesterday, followed by KB4456655. Then today a 'Check for Updates' led to a reinstall KB4457128.

On the other machine, WU updated today as expected and uneventfully, though I don't see Servicing Stack Update KB4456655 in the history ...

 

Check installed updates via Control Panel.

What is weird about this latest of the never ending Win updates fiascos is that in prior Win 10 versions, the service stack updates never used to show in Windows Updates if accessed via System Settings option. You could only see them if Win updates was accessed via Control Panel. However, this Stack Update KB4456655 does show if Win updates is accessed via System Settings.

At least we now have an explanation for the dual cumulative update activity.

 

@itman You are right, there it is under 'View installed updates' > Microsoft Windows, in Control Panel.

 

Having trouble with KB4457128. MS tried to install it several times via WU, but it never could be installed. I tried to install it manually, which didn't work either. I'm really tired of being forced to reboot my computer again and again, just to be told that this update could not be installed. Is there a way to stop MS from trying to install KB4457128? My computer would probably not be fully patched without it, but I really coulndn't care less. I just want stop MS from trying to install a patch that probably cannot be installed here (Windows 10 Home Premium 32bit). Thanks for your help in advance.

 

https://support.microsoft.com/en-us/help/4026726/windows-hide-windows-updates-or-driver-updates

 

Have you seen if KB4456655 is installed?
For Windows 10 version 1803, KB4457128 requires KB4456655.
See this article:
Error 0x8000FFFF in Win7? Phantom patch for Win10 1803? There’s a solution.

 

Check if KB4456655 is installed. If is doesn't show when accessed via System Settings, then check via Control Panel option.

If KB4456655 is not installed, that most likely is the reason the KB4457128 update is failing. Download KB4456655 from the Win Update Catalog web site and install it. Then try to reinstall KB4457128.

Another possibility is a borked KB4457128 got installed because of the above. Again per above, check if it is installed. If it is installed, uninstall it. Then try to reinstall it after KB4456655 is installed.

 

@Stupendous Man and @itman My bad. I should have mentioned that KB4456655 was installed before the installation attempt of KB4457128. So a missing KB is not the reason why KB44566128 cannot be installed here. I even tried system restore but that didn't work either. Hm...

@pegas This tool works! MS has stopped trying to install KB44566128.

Thank you all for your help.

 

Great! I used this tool when I was having some troubles with updates before the annual update. You can retain this tool on your drive in case of any other updates issues. Usually the main Win 10 upgrades will overcome all problems with monthly patches.

 

There are just too many MS update issues, so I will definitely keep this tool.