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: Oldest
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-10-02T14:31:11+00:00

    To confirm that we are dealing with the same problem, first You have to study logs in the C:$Windows.~BT\Sources\Rollback directory :

    1. setupact.log
    2. setuperr.log

    To put it simply, there will be two kinds of errors - minor, that setup ignores, and major that causes a setup to stop and rollback to the previous version. For me it was the problem with NET Framework 2.0 itself, not with particular KB update. After disabling feature in the control panel :

    Press the Windows key   on your keyboard, type "Windows Features", and press Enter.

    The Turn Windows features on or off dialog box appears.

    Unselect the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box, select OK, and reboot your computer if prompted.

    Everything went smoothly :)

    WG.

    Thank you. Problem solved

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-20T10:36:59+00:00

    Hello to all.

    I had the problem  doing the update from 1803 to higher version,  Direct update or thru downloaded WINDOWS.ISO file

    So after some searching I found a posting and did this o my machine   and now W O R K I NG .

    So here is what I did :

    UPDATE  18,11,2020:

    the upgrade to windows 20H2 now worked. Found some postings on the Internet.

    So here is what I have done:

    First of all I did a FULLBACKUP of my system using easeus Backup.

    This problem seems to be with some error in the IIS-Services  : InternetInformationServices

    To find this :

    1. Enter OPTIONALFEATURES.EXE in the window-search area and excute it
    2. Find IIS- in the list and see if anything is checked.
    3. try to uncheck every occurance in there, and check OK
    4. Probably you get an error that the change cannot complete.
    5. so,  using explorer : go to :  c:\windows}system32\inetsrv

    6 there is a folder CONFIG

    1. make a new folder CONFIG_old and copy CONFIG ==> CONFIG_old  You may get an error that you need special permission

        so continue.

    1. go inside folder CONFIG  and delete everthing that is in there.  Folder SCHEMA will remain becasue it is in use.

    9 REBOOT windows !!!

    1. after reboot do point 1, 2 and 3 again
    2. changes now will be accepted.
    3. REBOOT windows !!!

    13.  Download the WINDOWS.ISO file from  https://www.microsoft.com/en-us/software-download/windows10

    14 use ISO  NOT USB !!!

    1. when download is finished, open WINDOWS.ISO with explorer and run SETUP.EXE
    2. klick on "how windows...etc and select  "NO UPDATES",these will be done later

    17 let the update run  It will reboot a few times.

    On my system it worked perfectly after trying to update from 1803 many many times!!

    After the update go to Systemsetting and check for updates

    Hope this was of help for some of you !!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-01-11T03:29:00+00:00

    Update fails to install on a device with two hard drives. System files are on one (C drive). All data, including media on the other (D drive).

    The update did not fail on single hard drive devices of which I have two.

    Has anyone else found this to be true?

    Was this answer helpful?

    0 comments