Windows ver.2004 Update Failure

Windows Update Standalone Installer's response is - the update is not applicable to your computer. I have a CBS.log file related to this case but I cannot submit it for your further analysis because the size of it is about 91.3 KB and the limit of SUPERUSER's body size is 30,000 characters ( 29.3 KB ). Any idea how to proceed with that ?

**From wmicos.txt**

1. BuildNumber=19041
2. Caption=Microsoft Windows 10 Pro
3. CreationClassName=Win32_OperatingSystem
4. Locale=0409
5. OSType=18
6. OperatingSystemSKU=48
7. ProductType=1
8. RegisteredUser=RW
9. Version=10.0.19041
10. WindowsDirectory=C:\WINDOWS
11. ServicePackMajorVersion=0
12. Manufacturer=Microsoft Corporation
13. CSName=DELL
14. OSArchitecture=32-bit
15. PAEEnabled=True
16. MaxProcessMemorySize=2097024
17. NumberOfProcesses=98
18. FreeVirtualMemory=2437836
19. FreePhysicalMemory=1122352
20. FreeSpacePagingFiles=1836852

I have been trying to update OS Build from 10.0.19041.329 to 10.0.19041.388 ( in this attached above example ) and etc. using next update patches between June and November, 2020. All my attempts fail with the same response - the update is not applicable to your computer. Running SFC and DISM did not reveal any system files corruption. Also, I tried to do the upgrade using Windows ISO file disabling 3rd party antivirus app (Norton 360 ). The installation failed as well. Only I avoided off a clean installation of Windows which requires to re-install all my apps on this machine. How to fix this culprit ?

Reviewing the CBS.log ( some of conclusions) :

1. Failed to find a matching version for servicing stack.
2. Failed to find servicing stack directory in online store [Hresult=0x80070490-Error_Not_Found ]
3. Appl:Evaluating package applicability for Package_for_RollupFix_~.....~~19041.388.1.7, applicable state:Absent.

I used following commands: sfc /scannow - result clean, dism /online /cleanup-image /ScanHealth and dism /online /cleanup-image /RestoreHealth - result clean. Regarding @Ramhound's suspicion that WinSxS folder files might be corrupted with my mishap to update, I used another command as well as dism /online /cleanup-image /RestoreHealth /Source:I:\sources\install.wim, where I: drive is where I mounted my ISO.

Link where you will find CBS1.LOG file https://we.tl/t-QJm9vMuBZR

Starting September,2020 MS bundles LCU and SSU together. I downloaded KB4577266 patch and tried to install it, the process failed. Please see the uploaded CBS.log https://we.tl/t-syDzeLjayj

Also, before LCU and CCU install I tried to run sfc /scannow in Windows safe mode. No corruptions were detected.

https://we.tl/t-Y1NLAvdTrM I uploaded a copy of C:\windows\system32\config\components in components.txt file which is very gibberish to view those hives. I guess, they are as well as somewhere in registry under HKLM.

In addition, I reviewed CBS.log file:

• CBS failed to find a matching version for servicing stack C:\windows\winSxS\X86_MS_Windows-serrvicing stack........10.0.19041.329....... [Hresult=0x80070490 ]

I looked at the folder and found this file ( so it exists ! ), date modified 6/19/2020 when my Windows 10 ver.1909 got upgraded to ver.2004 (19041.329 ).

• Loaded servicing stack v10.0.19041.329 with core ..........\cbscore.dll

  I found that file with date modified 6/3/2020.

• Evaluating package applicability for package KB4577266, applicable state:Absent No parent found, go absent. My "nonprofessional" conclusion - if the SSU from 6/3/20 is corrupted, based on the marked error code, however, it was marked clearly as error not found why the system did not accept the new SSU (KB4577266 ) 2020-09 as a replacement for the corrupted ?

https://we.tl/t-chJ9nqKGH3 ComponentBasedServicing and Export(ServicingStackVersions) I am puzzled, why under HKLM\ hive I do not see in my registry key Components with other subkeys? Only when I create a new key "Components" and click "Load hive" I get that what is hidden in C:\windows\system32\config\components. Also when I reboot the machine the created hive under HKLM\ disappears.

I downloaded FRST app and created Fixlist.txt. For @ Tekkie_Boy's attention: Fixlist cannot be downloaded from the same site, I found there is a batch file on another site, the batch file should be pasted in a NotePad window and renamed as Fixlist.txt and later the FRST app renames it in FixLog.txt. https://we.tl/t-y62Vvqrdy0 So the FixLog file is created for your review.

https://we.tl/t-fUHAegI7uJ

FRST app after launching, it creates own folder FRST where are subfolders. Among them is a folder LOG where FixLog.txt file is laying.

After using the FRST app to scan and fix Components packages of Windows ver.2004 I got back "Windows Optional Features" and could install SSU patch KB4577266 without any issue. However, all sequential cumulative updates fail to be installed with error code 0x800f0831.

Yes, DISM ended in a failure with error code 0x800f081f-the source files could not be found. I continued as well as with sfc /scannow and uploaded for you another CBS.LOG file.https://we.tl/t-5V9ARniltQ Yesterday, I did an extra work - decided to see whether WINISO ( 19041.572 ) can be installed successfully upgrading my current OS. The process at end failed: "The system registry contains invalid file paths. Installation cannot proceed. The system image was applied without guaranteeing that driver-letter assignments would match across computers. Undoing changes made to your computer. 0xC1900101-0x30018 The installation failed in the First_Boot phase with an error during Sysprep-Specialize operation." So it restored my machine to 19041.329 back.

I appreciate very much @ Tekkie_Boy who spend with me a lot of time. I can report today after trying again to use Microsoft Media Creation Tool my Windows OS got finally successfully upgraded from 19041.329 to 19042.685 ( ver. 20H2 ). Everything functions correctly. I hope it stays this way. Regards, @Aventure