Update 1709 to 1803

dalchina · 02 Mar 2019

MS can't be responsible for all conflicting 3rd party issues in all cases. However, there should be much better support for failing upgrades, which can lead to the upgrade repeatedly downloading and reattempting.

The OS is complex and vulnerable, and because it's very open to influence and modification because of its architecture where user drivers and registry keys e.g. are mixed with those of the OS, and much more, complex problems are inevitable.

Sadly we're not likely to see a major reorganisation to separate the user and the OS.

*** Have a look at your BIOS and see if you have this option:

Update 1709 to 1803-snap-2019-03-02-14.52.32.png

It's about support for virtualisation so won't affect normal use.

haku · 02 Mar 2019

Hi again,

The Microsoft attitude.You are quite right in one respect, that of MS not required to be all the time everywhere. However, if one particular item (in this case one of their own dll's) occasions such havoc all over the place and so often, it's looking as if it's their responsibility.

Meanwhile, I've read the very interesting exchanges you gave me a link to + the possible "disabling VT-D in the BIOS" solution.This reeks of a very good possibility.Come Monday, with my physical hands back on my desktop machine, I'm going to try this before the next upgrade attempt. Indeed, I certainly don't need VT-D: never a game, no 3D and what have you.

However, my suspicion also goes to some motherboard elements that are no longer compatible with the latest Win10 reiterations (which, in my opinion will go down in computer history as even worse than the Vista adventures). Why oh why couldn't they leave Win 7 alone, patch it up when necessary, and proceed. Someone in that linked conversation put it very well: the actual mess with the upgrades is the worst they have seen.

But, again, we'll come to the bottom of this...

Best,

H

dalchina · 02 Mar 2019

Here's another solution (which may or may not be relevant): found with similar content to some of your error log, albeit the failure was at a different stage of the upgrade procedure.

For now, hold on to this and do nothing with it- you've plenty to do.

It may also be necessary to try to get SFC /SCANNOW run.

Not been able to update since 17025 : windowsinsiders

The 'fix' is to the end:

It worked ! Renamed both the folder and the reg key (after disabling inherited permissions removing any that were inherited, and giving full access to my account), and installed the upgrade immediately.

A default provisioning folder and reg key set are created during the install.

- but doing that is described earlier- it's not as simple as pressing 'delete'!

Found by searching for
onecoreuap\shell\propsys\schemacachehelpers.cpp