Upgrade from 14271 to 14316 Fails with 0x80240031

I've tried many suggestions, including removing files, system cleanup, etc but it consistently fails with the 0x80240031 error code. Other Windows updates are successful, just the 14316.

Its not a system hardware problem as it is a triple boot system with Win7/Win10/Insider Win 10. Each are on separate drives. The Insider installation is on a separate 1GB hard drive and the only thing installed, other than the default Win 10 applications, is Malwarebytes.

I don't see a 14316 ISO yet so I can't just download that and reinstall.

The installer is having an issue with the other disc's in the system IMO.

My main rig has 4 1Tb drives, though 3 of them are differing storage drives, only one is the master and OS booting. I had to remove my others to perform the upgrade, and then would plug back in afterwards.

As long as no one feels pulling your other drives and doing the upgrade may not screw with the boot manager, I'd say try that.

I haven't had any problem with the preview updates before, with all 3 OS discs on line. Mine are not slaves like yours.

Fixed. The "Updates From More Than One Place was set to "on". Setting it to "OFF" fixed the problem.

The "on" setting must be default as I've never changed it (or even looked at it). I found the solution on a Microsoft forum.

My suspicion is that the other Win 10 installation was causing the problem (system is triple boot with Win 7/Win 10 Pro/Win 10 Preview). When I "Retried" the update it had to download the complete update. Before changing the "Choose how updates are delivered" option, it downloaded but the download was much faster suggesting some of it was being accessed from the other Win 10 installation.

Here is the setting panel (accessed from Advanced Options, then Choose How Updates are Delivered.

Ahh, that is interesting, but I'm wondering how it considered a non active partition or drive with your other install as a networked resource, or did I miss something here?

Yeah, that should always be off IMHO.

Glad you got it though, can you set to solved for us? Thanks.

It is set to "solved". I did that yesterday when I posted the fix.

The other drive is only a thought since it was a multiple boot system with another copy of Win 10 (each OS on a separate drive).

BTW, I'm originally from Mechanicsburg, Pa.