Windows 10 Update 2004 / 20H2 - Error 0xc1900101

Anonymous
2020-07-21T19:15:15+00:00

Windows specifications

Edition Windows 10 Education
Version 1909
Installed on 2019-06-25
OS build 18363.959
Arch. Type x86_64
Insider program No

Device specifications

Processor AMD Ryzen 5 1600X 6c/12t 3.6GHz
BIOS Mode UEFI
Motherboard Asrock AB350 Pro4
RAM 16 GB

Issue

I downloaded the Feature Update 2004 and tried to installed it 3 times. Each time all went good without error, then it ask for restart, so I click the "Restart and Update", then it reboot (1st time) but before accessing the authentication page it reboot again (2nd time) then again before accessing the authentication page it reboot again (3rd time) this time it's really longer (as if the update was finally applying), it goes to teh authentication page. I log in, then I check and the I'm still at update 1909.

In the Windows update history I can see an error code: 0xc1900101. Nowhere else I can see an error.

The two first times I tried to update and it fails when I went in Windows Update and clicked "Check for updates" I saw the 2004 update available and was able to download and install it again. But since last try it now tells me I'm up to date yet I'm still at update 1909 and 2004 failed to apply.

PS: I have Core Protection disabled.

PS2: Windows Update troubleshooter says all is fine.

Additional information

From systeminfo:

Hotfix(s):                 23 Hotfix(s) Installed.
                           [01]: KB4565633
                           [02]: KB4497165
                           [03]: KB4498523
                           [04]: KB4503308
                           [05]: KB4506933
                           [06]: KB4508433
                           [07]: KB4509096
                           [08]: KB4515383
                           [09]: KB4516115
                           [10]: KB4517245
                           [11]: KB4520390
                           [12]: KB4521863
                           [13]: KB4524569
                           [14]: KB4525419
                           [15]: KB4528759
                           [16]: KB4537759
                           [17]: KB4538674
                           [18]: KB4541338
                           [19]: KB4552152
                           [20]: KB4560959
                           [21]: KB4561600
                           [22]: KB4565554
                           [23]: KB4565483

Windows for home | Windows 10 | Windows update

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
Answer accepted by question author
Anonymous
2021-04-17T12:05:03+00:00

If you experience this issue on ASRock motherboard make sure that you've updated to the latest available BIOS.

Then Enter the BIOS (F2) and Turn off (Compatibility Support Module) 

After you changed the BIOS setting run Windows10Upgrade9252.exe available for download on microsoft website url: http://go.microsoft.com/fwlink/?LinkID=799445

Problem solved.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

69 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-20T06:46:58+00:00

    Hi sonny_mv

    Thanks for this answer.

    Unfortunately it doesn’t seem to be the solution for me as I could find no BCD error per your instructions.  My result is shown here:

    (Can't Paste the Screen Shot so have extracted the text, shown below)

    I guess that is one less possibility though!

    Extracted Text of the Screen Shot:

    Visual BCD Editor - System store

    Store "New Repair Help Object Elements

    B- Bed Store

    {fwbootmgr}

    {bootmgr}

    B Loaders

    • Windows Boot Manager

    • DebugTool

    •CD/DVD Drive

    • Hard Drive

    BBI

    Windows Recovery Environme

    Windows Boot Manager

    S Hibernate resumers

    É) Settings

    S Device options

    {memdiag}

    RCIick to Create new Boot Entries

    Type Name

    0x11000001 Application Device

    0x12000002 Application Path

    0x12000004 Description

    0x12000005 Preferred Locale

    0x14000006 InheritedObjects

    0x14000008 Recovery Sequence

    0x15000066 library _custom : Ox15000066

    0x16000009 Auto Recovery Enabled

    0x1600000b Allow Bad Memory Access

    0x16000060 library _custom : Ox16000060

    0x17000077 library _custom :Qx17000077

    0x21000001 OS Device

    0x22000002 System Root

    0x23000003 Associated ResumeObject

    0x25000020 Nx Policy

    0x250000c2 loader_custom :0x250000c2

    0x250000f0 HypervisorLaunchType

    Delete Ed* New

    □

    X

    Value

    \Device\HarddiskVo!ume9<C:) \Windows\system32\winload .efi Windows 10 en-US

    {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} <bb2ddb4a-1d44-11ea-984a-84b 3b625a 135} 7

    True

    True

    True

    0x15000075

    \Device\Harddisk Volume 9(C :)

    \Windows

    <bb2ddb48-1d44-11ea-984a-84b 3b625a 135}

    NxPolicyOptln

    1

    HypervisorLaunchOff

    Edit Boot-Menu

    Hint: DbICIick to Edit

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-17T08:50:32+00:00

    Okay, sorry for that, I try to explain it easier:

    I solved the 0xc1900101 error with deleting some partition entries in the BCD (Boot Configuration Data) of the hard drive. The entries directed to already deleted partitions.

    The BCD is the Bootloader of Windows 10 (since Win Vista).

    You can read the BCD entries with the tool Visual BCD (https://download.cnet.com/Visual-BCD/3000-2094\_4-75742559.html):

    1. Start the tool Visual BCD, open the section "Loaders" in the left.
    2. Double-click the entries named "Windows 10" and look in the right section for the line "ApplicationDevice".

    3)The wrong entries have some questionmarks in the "value"-column like "?volume?\Harddisk...". Now right-click the entry in the left section and select "delete selected object". Repeat that procedure with the other "Windows 10" entries left. There should be only one left with the name "Windows 10". That one has no question-marks.. Ignore the other entries. 

    Be careful to not delete the right ones, otherwise your Windows will no longer Start!!!

    After that procedere, Windows Update was able to run the full update to Win 10 2004 :)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-17T07:09:16+00:00

    Same Problem here with ASUS N56VZ Notebook (2012)...

    After many attempts to solve the 0xc1900101 error, I figured out that there were too many entries in the BCD (Boot Configuration Data) orphaned and had redirections to partitions that are no more available..

    To show the BCD entries:

    start command prompt "cmd" with admin-rights (start--> type "cmd" and hit enter by pressing shift+ctrl)

    the type in "bcdedit /enum all" and there should be some entries, but only one named "Windows Boot Manager" and two "Windows Boot Loader" entries.

    On my N56VZ Notebook there were 5 entries of Windows Boot Loader.

    I cleared out the 3 ones. To find out, which are wrong, find the string after "resumeobject" in the list of the "Windows Boot Manager". The entries of the "Windows Boot Loader" beginning with that number and the other with "{current}" are the right ones. So I deleted the other (normally under "device" there are some "?"-Symbols when orphaned) with the tool "Visual BCD", simply search for it.

    After that procedere, Windows Update was able to run the full update to Win 10 2004 :)

    Could you try explaining that again but with better English? I understand some of what you are saying but it is very difficult to follow. It reads like you pasted from Google Translate or something like that.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-31T05:47:49+00:00

    Thank you WG. I had all the problems in this thread including the disappearing update after two tries. I found your post and uninstalled .NET 2.0. Updated to 2004 again from Microsoft's web site and it went smoothly for me.

    Was this answer helpful?

    0 comments