Can't get up to date from 1709 build 16299.492

Per subj, nothing works. I rarely consult support as I usually manage to resolve issues myself, but I'm about to give up on this one.

The history is as follows. A gaming PC, installed Windows in 2017. Prohibited updates right away, so I don't have to deal with updates BS bouncing my PC in the middle of a an online gaming run or unexpectedly changed behavior, etc.

Fast forward to 2021, when I upgraded my PC with a new MB, migrated the RAID from soft to hard and upgraded the CPU. All worked fine, except the CPU change from Ryzen 7 1700 to Ryzen 7 5800x, as that broke hibernation and sleep functionality for reasons unknown. Of course, I tried to install and reinstall all MB and AMD drivers with that, no success, but I don't have any question marked unknown devices in the Device Manager.

So I decided that it's time to update as this may fix the problem. I reenabled the Windows updates in group policies, but it says "Last failed install attempt on ‎10/‎6/‎2021 - 0x80240034". I tried to manually download from the catalog the KB it thinks my PC needs, which is KB4493441. Downloads fine, when installing it fails with (in the setup event log) "Windows update could not be installed because of error 2149842967", which, according to MS, means that this update isn't applicable, which is weird as I didn't come up with this KB number myself.

I also tried to use the "windows 10 update assistant". It fails to properly boot and reverts the changes. The setuperr.log contains a load of errors, a bunch of last ones:

2021-10-06 13:20:11, Error CONX Windows::Compat::Shared::UtcLogger::SetServiceState (820): Error starting service: [1058].[gle=0x80070422]
2021-10-06 13:20:11, Error CONX Windows::Compat::Shared::UtcLogger::End (281): Error starting service: [0x80070422].[gle=0x80070422]
2021-10-06 13:52:15, Error MIG OC Exception: OC::COCDismAdapter::GetFoundationPackageName: Couldn't find the Foundation package
2021-10-06 13:52:15, Error SP Could not save OC status. Error: 0x8007001F
2021-10-06 13:52:15, Error SP Operation failed: Gather Optional Component status. Error: 0x8007001F[gle=0x000000b7]
2021-10-06 13:52:15, Error SP COperationQueue::Sort: Could not find an execution phase for 50
2021-10-06 13:52:15, Error SP Operations can no longer be sorted following an attempt to retry a failed operation.
2021-10-06 13:52:15, Error SP Operation execution failed: 6. hr = 0x8007001F
2021-10-06 13:52:15, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007001F
2021-10-06 13:52:15, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007001F

Searching online doesn't bring any meaningful results.

Any ideas how do I fix this as I really don't want to abandon the system. The hibernate and sleep are my only issues at this point and I tried to fix them multiple times using various suggestions on forums with no success, so I decided to upgrade.

dalchina said:

Advise outcome.

1709 build 16299.492

C:\Windows\system32>chkdsk c: /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
713728 file records processed.
File verification completed.
13870 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
21930 reparse records processed.
862858 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
21930 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
74566 data files processed.
CHKDSK is verifying Usn Journal...
35043920 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

475371519 KB total disk space.
302349312 KB in 513748 files.
303440 KB in 74567 indexes.
0 KB in bad sectors.
836279 KB in use by the system.
65536 KB occupied by the log file.
171882488 KB available on disk.

4096 bytes in each allocation unit.
118842879 total allocation units on disk.
42970622 allocation units available on disk.

setupdiag.exe:


SetupDiag was unable to match to any known failure signatures.
SetupDiag version: 1.6.2107.27002
System Information:
Machine Name = DESKTOP-6H2UO7D
Manufacturer = System manufacturer
Model = System Product Name
HostOSArchitecture = 1033
FirmwareType = PCAT
BiosReleaseDate = 20210810000000.000000+000
BiosVendor = BIOS Date: 08/10/21 06:11:29 Ver: 05.00011
BiosVersion = 5861
HostOSVersion = 10.0.16299
HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
TargetOSBuildString = 10.0.19041.900 (vb_release_svc_prod3.210311-1736)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Windows Defender
FilterDrivers =
UpgradeStartTime = 10/6/2021 3:07:10 PM
UpgradeEndTime = 10/6/2021 3:30:22 PM
UpgradeElapsedTime = 00:23:12
CV = SRn13fTdZUKro/lo
ReportId =


SetupDiag was unable to match to any known failure signatures.
SetupDiag version: 1.6.2107.27002
System Information:
Machine Name = DESKTOP-6H2UO7D
Manufacturer = System manufacturer
Model = System Product Name
HostOSArchitecture = x64
FirmwareType = PCAT
BiosReleaseDate = 20210810000000.000000+000
BiosVendor = BIOS Date: 08/10/21 06:11:29 Ver: 05.00011
BiosVersion = 5861
HostOSVersion = 10.0.16299
HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
TargetOSBuildString = 10.0.19041.900 (vb_release_svc_prod3.210311-1736)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Windows Defender
FilterDrivers =
UpgradeStartTime = 10/6/2021 3:07:10 PM
UpgradeEndTime = 10/6/2021 3:30:22 PM
UpgradeElapsedTime = 00:23:12
CV = SRn13fTdZUKro/lo
ReportId =

Currently at c: with 1709 in-place upgrade (the fresh windows 20Hwhatever fails).

Using the heidoc.net tool now, never heard of them before, but just learned that they were in a fight with Amazon:

HeiDoc.net vs. Amazon.com Part 1: The History of a Legal Dispute

So I'm gonna post this message to promote it, encourage others to do the same and wish that Amazon goes bankrupt as well as Jeff Bezos personally for all the harm they do to small business owners overall and to me personally.

- - - Updated - - -

It fails, doesn't even manage to prepare the temp folder in full, i.e. it doesn't reboot the PC. The last lines from the setuperr.log from the "Panther" folder:

property from 'SCSI\Disk&Ven_HPT&Prod_DISK_0_0&Rev_4.00\7&2399a73e&0&000000'. Error = 0x0000000D
2021-10-06 17:29:41, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2021-10-06 17:29:41, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2021-10-06 17:29:55, Error MOUPG Finalize: Error reading narrator reg key: [0x80070002]
2021-10-06 17:29:55, Error MIG OC Exception: OC::COCCbsAdapter::InitOnline: Failed to find the Foundation Package name
2021-10-06 17:29:55, Error SP Could not save OC status. Error: 0x8007001F
2021-10-06 17:29:55, Error SP Operation failed: Gather Optional Component status. Error: 0x8007001F[gle=0x000000b7]
2021-10-06 17:29:55, Error SP COperationQueue::Sort: Could not find an execution phase for 82
2021-10-06 17:29:55, Error SP Operations can no longer be sorted following an attempt to retry a failed operation.
2021-10-06 17:29:55, Error SP ExecuteOperations: Failed execution phase Finalize. Error: 0x8007001F
2021-10-06 17:29:55, Error MOUPG MoSetupPlatform: Finalize reported failure!
2021-10-06 17:29:55, Error MOUPG MoSetupPlatform: Using action error code: [0x8007001F]
2021-10-06 17:29:55, Error MOUPG CDlpActionFinalize::ExecuteSetupPlatformFinalize(896): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CDlpActionFinalize::ExecuteRoutine(393): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CDlpTask::ExecuteAction(3243): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CDlpTask::ExecuteActions(3397): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CDlpTask::Execute(1631): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CSetupManager::ExecuteTask(2169): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CSetupManager::ExecuteTask(2132): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CSetupManager::ExecuteInstallMode(809): Result = 0x8007001F
2021-10-06 17:29:55, Error MOUPG CSetupManager::ExecuteDownlevelMode(346): Result = 0x8007001F
2021-10-06 17:30:02, Error MOUPG CSetupManager::Execute(236): Result = 0x8007001F
2021-10-06 17:30:02, Error MOUPG CSetupHost::Execute(375): Result = 0x8007001F

Followed the in-place upgrade tutorial here, e.g. ensured there's no secure boot option in BIOS selected, ensured that the BitLocker is disabled, etc.

Any ideas?

PS I'm a bit concerned about the fatality of that error about the reading the narrator's reg key. If I recall right I used in the past some hardcore measure to disable the narrator as this stupid thing gets in the way of gaming and it's the next nightmare after the windows update to have a narrator pop up in the middle of a gaming run.

Please run:

Both V2 and DM log collectors:
BSOD - Posting Instructions

Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.


Upgrade_failure_info.bat - Click here to go to the BSOD batch repository to download and run this batch file.

I'm not doing the ghey collection stuff as it's pointless. Sorry, and I understand if you folks won't be willing to help without it. But there's just no point and it's pretty intrusive, e.g. collects the IPv6 address, MAC address, etc.

I will probably eventually give up, but wanted to leave a trail for someone who's willing to pursue this further.

Judging from what I've read and experimented with, MS is willingly turning this into a subscription service with a small rolling window, they have 0 interest in supporting people who wish to live off the grid even for a little while. I don't think it's stupidity that there's no way to "reset" the CBS, I think it's by design -- which is to ensure that up-to-date systems are healthy, but those who are behind are more and more likely to be stuck in order to encourage people to stay on the most recent system.

So they key here is the "foundation package". Here's how it looks like in the setupact.log:

2021-10-08 14:05:01, Error DISM DISM Package Manager: PID=11448 TID=14148 Failed to open the Windows Foundation Package as a fall back. - CPackageManagerCLIHandler::ProcessCmdLine_GetFeatures(hr:0x800f0805)
2021-10-08 14:05:01, Error DISM DISM Package Manager: PID=11448 TID=14148 Failed while processing command get-features. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0805)

This error shows that the so-called "component based servicing" is corrupt. Such Windows system can't be in-place upgraded or uplifted and even most updates won't install.

The foundation package is a collection of Windows features one can install. So your Windows knows about the features that can be potentially installed from the installation media or whatever it maintains some form of list or a database of these features.

When it fails you can't install or remove any Windows features or packages anymore using the tools such as "windows features" or dism.



"Get Features" is the basic thing that is supposed to work at all times which just gives a list of all the features the system can have, such as IIS, FTP client, etc.



MS suggests multiple ways (using dism tool) to "fix" the CBS, but in my case nothing works.

It's a yuuuge problem as by searching by this situation description or error codes of dism one can find a ton of questions, even on these forums, and all of them are dead ends. This breaks the updates and uplifts for people with no recourse, but to abandon their systems. I've found only 1 mention that a person was able to fix something by exporting/importing the registry keys (read further) that are related to CBS from a similar hardware system. I have no such a thing.

There's a weird, sort of "ephemeral" registry key called COMPONENTS.



It won't show, unless you've just run a dism command. It's pretty big, if exported, in my case it was about 130M. The structure of it is unclear, full of various GUIDs and hashes and needs research as apparently manually fiddling with it changes the dism behavior. I did my share of transposing the entries there, but it's hard to do it without understanding how it works, so all I got in the end is different errors but never got my CBS working as it should.

Another registry key of interest is "component based servicing".



It MAY be the one that potentially contains the names of KBs that your system may find "applicable":



Because as it turned out MS retires their older KBs quickly, literally none of these (except just 1) can be found in their update catalog as of now (although mentions can be found on forums, etc).

In the end my speculation is I got into this mess because either of the two:

1) Because all KBs that can potentially make my windows update compatible back again with the rest of MS were superseded or retired I'm stuck with an unsupported windows update that prevents my system from being uplifted.

2) It may also relate to the hardware change as I replaced my CPU, which may have made some of the active CBS components incompatible with the system I'm running.