"Up to date" even though I am running version 1507 (RTM build of Windows 10); how to get 1803 (Redstone 4)?

Anonymous

Well without any real help from anyone, I managed to get a legitimately genuine version of Windows 10 installed on my computer... but it is from a DVD so I am running the first released version of the operating system, and I am trying to update to the latest release. When I run Windows Update, I used to see "Feature Update to 1803" as an available update, but now I don't see it at all and I know for a fact that I am still running Threshold instead of Redstone.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

62 answers

Anonymous

2018-09-05T18:14:42+00:00

... this is starting to become incredibly irritating... I've just hit a mood swing before I see my comupter restoring from 1703 again and that isn't helping either... as soon as I get error codes, I will post them here...

First error code is the same. C1900101 - 4000D...

The diagnostics tool is taking too long as always so I am just going to send the entire log of errors which happened during the upgrade...

<start log>

2018-09-05 12:43:43, E rror SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade*[gle=0x00000005]***

2018-09-05 12:44:39, Error CSI 00000001 (F)80220008 [Error,Facility=FACILIT Y_STATE_MANAGEMENT,Code=8] #171885# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })

[gle=0x80004005]

2018-09-05 12:45:23, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)

2018-09-05 12:47:03, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get preferred homegroup withhr=0x80070490

2018-09-05 12:47:18, Error CSetupAutomation::Resurrect: File not found: C:$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]

2018-09-05 12:47:18, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation:0x80070002[gle=0x00000002]

2018-09-05 13:03:10, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)

2018-09-05 13:05:04, Error MIG COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error:0x80070422[gle=0x000003f0]

2018-09-05 13:06:30, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2

2018-09-05 13:06:30, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error

2018-09-05 13:06:30, Error [0x0808fe] MIG Plugin {6CF7C0FC-91DD-4D47-9B6F-0769F8AE68D2}: [TpmScr] - check completion signature failed, skip this folder. file=C:$WINDOWS.~BT\Work\MachineSpecific\Working\srcworking\agentmgr\CCSIAgent\005A9238\completed.txt

2018-09-05 13:06:31, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed0x139f, bridge present = 0

2018-09-05 13:06:32, Error [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: DISPLAY\ACI22FD\1&8713bca&0&UID0 -> Migrated [0000000000000000], configured [monitor.inf] and not present.

2018-09-05 13:06:32, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment}. Error: 0x80070002

2018-09-05 13:06:32, Error SP Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2*[gle=0x000000cb]***

2018-09-05 13:08:49, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{52776FBF-403C-49cc-b7cb-dd557f36096A} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)

2018-09-05 13:09:47, Error MIG COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error:0x80070422[gle=0x000003f0]

<end log>
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-05T21:10:45+00:00

Welp, as it turns out, I did actually update three or four drivers for various devices so that could have been the issue as well.
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-05T22:09:23+00:00

So it restored again but a few things are different.

This time, I intentionally skipped a disk-checking process which happens at the second (OOBE) reboot, and the upgrade now reports 40017, which according to the errors page means that the throwback happened at "BOOT" (the upgrade stalled at 75% after the skipped disk check and never went back to the blue update screen).

SetupDiag was unable to match to any known failure signatures.

Does it mean I have to restart the upgrade again/perform an upgrade disk check?
Was this answer helpful?

0 comments No comments

Anonymous

1A	SP_EXECUTION_OP_BEGIN_FIRST_BOOT

17	SP_EXECUTION_OP_BOOT

Earlier you had 1A, now you've got 17, neither one is telling me much. Too, too bad SetupDiag just doesn't say something in real English. That app is meant to read all the logs & state the error. But who does it think it's talking to?

So, I get this far only...

https://docs.microsoft.com/en-us/windows/deployment/upgrade/troubleshoot-upgrade-errors

Troubleshooting upgrade errors

It is in Phase 4, you get so close to a success...

"Second boot phase: In this phase, the system is running under the target OS with new drivers. Boot failures are most commonly due to anti-virus software or filter drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, temporarily uninstall anti-virus software, then retry the upgrade."

It sounds to me you did everything, including disabling suspect devices...

https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures

Resolution Procedures

	Code	<br>	---	<br>	0xC1900101 - 0x40017	<br><br> <br><br><br>	Cause	<br>	---	<br>	Windows 10 upgrade failed after the second reboot. <br><br>This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.			Mitigation	<br>	---	<br>	Clean boot into Windows, and then attempt the upgrade to Windows 10. <br><br>For more information, see How to perform a clean boot in Windows. <br><br> <br><br>Ensure you select the option to "Download and install updates (recommended)."

And this I posted earlier...

	Code	<br>	---	<br>	0xC1900101 - 0x4000D	<br><br> <br><br><br>	Cause	<br>	---	<br>	A rollback occurred due to a driver configuration issue.<br> <br><br>Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.<br> <br><br>This can occur due to incompatible drivers.			Mitigation	<br>	---	<br>	Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.<br> <br><br>Review the rollback log and determine the stop code. <br><br>The rollback log is located in the C:$Windows.~BT\Sources\Panther folder. An example analysis is shown below. This example is not representative of all cases:<br> <br><br>Info SP Crash 0x0000007E detected <br><br>Info SP Module name : <br><br>Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005 <br><br>Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A <br><br>Info SP Bugcheck parameter 3 : 0xFFFFD000E5D23728 <br><br>Info SP Bugcheck parameter 4 : 0xFFFFD000E5D22F40 <br><br>Info SP Cannot recover the system. <br><br>Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.<br> <br><br>Typically, there is a dump file for the crash to analyze.<br><br><br><br><br><br>If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:<br><br><br><br><br><br>1. Make sure you have enough disk space. <br><br>2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. <br><br>3. Try changing video adapters. <br><br>4. Check with your hardware vendor for any BIOS updates. <br><br>5. Disable BIOS memory options such as caching or shadowing.

I'm not sure where to go from here. I wish there were a log that would state the precise driver that is at fault. Did you look for a rollback log this time?

0 comments

Anonymous

2018-09-05T23:52:04+00:00

It does not matter now... it is not like a complete reformat and reinstallation straight to 1803 is impossible. All of the files I have kept from Windows 8.1 are still nicely archived and I did not grab anything new that I want to keep since that point. I am just going all the way back and performing a fresh installation of 1803.
Was this answer helpful?

0 comments No comments