Windows 10 Feature Update 2004 won't install; MEMORY_MANAGEMENT stopcode

David Schrag 376 Reputation points
2020-11-17T17:04:25.84+00:00

I have tried multiple methods for updating to Feature Update 2004, including Windows Update and the Windows 10 Update Assistant. The download completes fine and the updates begin to install. The first reboot seems to go OK as well. But then it reboots to a BSOD with Stop code: MEMORY_MANAGEMENT. After that, it rolls back the installation to 1909. The only error in the event log is "Installation Failure: Windows failed to install the following update with error 0xC1900101: Feature update to Windows 10, version 2004." I have run both pre-boot and post-boot memory diagnostics from both Microsoft and Dell. They find no errors. I have tried removing all peripherals from the computer during the update process. I have gone through the Windows Update troubleshooter. I have run sfc. I am stumped.

Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,942 questions
0 comments No comments
{count} votes

9 answers

Sort by: Most helpful
  1. Jenny Feng 14,131 Reputation points
    2020-11-18T02:13:33.217+00:00

    @David Schrag
    Hi,

    A result code of 0xC1900101 is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue.

    You could try to use the Device Manager updating drivers manually:
    Go to Start > type Device Manager > click the first result
    Expand the list of devices.
    The device causing error 0xC1900101 will likely appear with a yellow exclamation mark.
    Right-click the problematic driver > select Update Driver Software to install the latest updates.
    Click Uninstall to completely remove it.

    To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the Resolution procedures section later in this article.
    More information is then obtained for the troubleshooting.
    For your reference:
    https://learn.microsoft.com/en-us/windows/deployment/upgrade/upgrade-error-codes

    Hope above information can help you.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. David Schrag 376 Reputation points
    2020-11-18T15:14:41.187+00:00

    Thanks for the reply. There are no devices in Device Manager with a exclamation mark. I have already used the hardware vendor's tool to search for updated drivers for built-in components, and there are no updates to install.

    I downloaded and ran SetupDiag (https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag), and found the extend code: 0x30017. This indicates that the phase was SP_EXECUTION_FIRST_BOOT and the operation was SP_EXECUTION_OP_BOOT. This particular extend code is not covered in the resolution procedures (https://learn.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures).

    I ran sigverif (https://learn.microsoft.com/en-us/windows/deployment/upgrade/quick-fixes#repair-unsigned-drivers) and confirmed that I had no unsigned drivers.

    I ran DISM (https://learn.microsoft.com/en-us/troubleshoot/windows-server/deployment/fix-windows-update-errors). It created a 46 MB log file so it's hard to tell whether it fixed anything.

    My next step will be to try again after a clean boot. If that doesn't work, do you have any other suggestions?

    0 comments No comments

  3. David Schrag 376 Reputation points
    2020-11-18T16:45:14.193+00:00

    I tried the clean boot and used the Windows 10 Update Assistant. This time it attempted to install Feature Update 2009, not 2004. But I got the same MEMORY_MANAGEMENT stop code (BSOD), followed by a rollback. The SetupDiag log reported the same 0x30017 extend code. There are a bunch of other logs in the zip file generated by SetupDiag, but I don't know how to interpret the results.

    0 comments No comments

  4. Jenny Feng 14,131 Reputation points
    2020-11-19T07:11:18.683+00:00

    @David Schrag
    Hi,
    Thanks for your efforts you have put into this case.
    Since you have try many method to solve this issue, sometimes nothing other than a Windows 10 Reset will completely fix your problem. Windows 10 Reset replaces your system files with a completely fresh set of files and theoretically clears lingering issues relating to the Memory Management error while keeping the majority of your important files intact.
    I think you can perform a reset save files or clean install.

    Hope above information can help you.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  5. TekkieBoy 106 Reputation points
    2020-11-19T16:56:32.977+00:00

    Hello David,

    Can you run the following command in the command prompt as an administrator?

    Dism /Online /Get-Drivers /Format:Table > "%USERPROFILE%\Desktop\drivers.txt"
    

    And then provide the drivers.txt on the desktop together with the Logs.zip package as a download?

    Friendly greetings
    Sorry for any mistakes. English is not my native language

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.