Feature Update to Windows 10, Version 1803 - Error 0x800f0900

This was the command that you had ran in the earlier post:
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\sources\install.wim:1 /limitaccess

There are two types of iso and the type from the microsoft website is often esd and not wim.
It was a surprise that it was wim

Maybe it was from TechBench.
I know I sometimes use ESD Decrypter.

I've had too many sleeps to remember.

So, how can I get an ESD v1709?

OK.
I'm gonna compare this direct Microsoft link using Microsoft Windows And Office ISO Download Tool.

It's the same.

When the iso is posted on the Microsoft website it is in the esd format.
When the iso no longer available other websites offer the iso in wim format.
It should not matter the format except for the command.
The command worked as wim so that is fine.

When ready you can start windows driver verifier.

If there are no bsod using the customized settings in the prior link then change the customized settings for the simultaneous tests in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community




When using Windows driver verifier the computer may become sluggish. And the boots can become very slow.
The Windows driver verifier tool should be used for 48 hours. After the last bsod it will be used for an additional 36 hours of typical computer use.
If there are no more bsod then that will complete the use of this tool.

So, is the idea of Driver Verifier is to give me a BSOD, then I have to go looking for a crash log? Is that right?
And where do I find this log?

There were bsod in the logs but no dump files.
When there are dump files they can be debugged.
The tool windows driver verifier should create bsod crashes that produce dump files.
After each crash you will use the windows advanced troubleshooting menu to turn off the tool and return to the desktop.
On the desktop you will then uninstall misbehaving drivers.
New drivers can be reinstalled immediately or after all misbehaving drivers have been uninstalled.
The tool will then be restarted to find the next misbehaving driver.

The beta log collector will collect the mini dump files.
You will use everything to find the memory dump files. (c:\windows\memory.dmp)
If the memory dump files are < 1.5 GB then zip and post a share link into the thread (one drive, drop box, or google drive)

zbook said:

On the desktop you will then uninstall misbehaving drivers.
New drivers can be reinstalled immediately or after all misbehaving drivers have been uninstalled.
The tool will then be restarted to find the next misbehaving driver.

Will it tell me which are the misbehaving ones? How will I know?


BTW. Many thanks for your time, patience and help. I'm determined to fix it. Hopefully.
I have much older computers and laptops that updated without any problem at all.

The computer I am on at present is one I built 8 years ago.

GIGABYTE GA-X58A-UD7 LGA1366 Motherboard
Intel Core i7 950 Processor LGA1366 3.06GHz 8MB Cache CPU
24 GB RAM

It's still running like a dream. So, is the one that I am trying to upgrade to 1803. But it is being stubborn.
The stubborn one was built in 2012. Building and repairing them is usually easy, but when you get odd problems like this, that's when I need help. Damn Windows.