Share via

Windows 10 20H2 Update failing, rolling back after install

Anonymous
2021-09-08T06:38:38+00:00

It is impossible to install the Windows 10 20H2 update on my notebook, as well as on some customer notebooks. To be more concrete, Windows downloads and installs the update and offers an reboot to complete the installation, just to roll back after the reboot instantly. Also, the update is not found in the Windows Settings but has to be triggered with the Windows Update Assistantor the setup.exe of an Install USB-Stick created with the Media Creation Tool.

Data of my setup:

Affected OS: Windows 10
OS Version: 1909
OS Build: 18363.1593

Affected hardware platform: Lenovo ThinkPad T590

There are various error codes shown in during the update and in the logs, as noted following.

Normal error in Windows update history: 0xC1900101

More detailed error code from the Media Creation Tool USB-Stick: 0xC1900101 - 0x30018

Error code from the BSOD right before rolling back:

  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • What failed: ACPI.sys, another time RtsPer.sys, another time nothing

In the Windows System Event Log, there are some errors as well, those seem interesting:

  • detectionverification not found; driver {DD8E82AE-334B-49A2-AEAE-AEB0FD5C40DD}\DetectionVerification\5&3a99d132&0&0
  • dolby dax api service terminated uexpectetly, it has done this 1 times(s)

In the setupact.log there are many errors stating Windows was unable to move or rename files, e.g.:

  • SPMoveFileWithShortName: Error while setting short name TaskScheduler for \?\C:\Windows.old\Windows\System32\Tasks\Microsoft\Windows\TaskScheduler. Error: 0xC000000D
  • CSetupPlatformApplyRollbackCheckpoint::Rollback: Error while moving \?\C:\Windows\System32\CatRoot\TMPB8AE.tmp to \?\C:\Windows.old\Windows\System32\CatRoot\TMPB8AE.tmp. Error: 0x00000002

From that, I suspect that it is a driver problem, maybe an audio driver problem.

Unfortunately, I could not narrow it down to an exact component or action that can be taken to solve the problem.

I tried to narrow it down and solve it with the following measures as of now:

  • Updating the Drivers via Lenovo System Update and Lenovo Vantage
  • Running the Windows Update Troubleshooter in Windows Settings
  • Running "DISM.exe /Online /Cleanup-image /Restorehealth" and "sfc /scannow"
  • Booting Windows in Safemode and deleting the Cache within "C:\Windows\SoftwareDistribution"
  • Tried various repair and cleanup steps within the WUReset Tool, that helped in the past with Update issues: 2, 3, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
  • Tried to update with the Windows 10 Upgrade Assistant (https://go.microsoft.com/fwlink/?LinkID=799445)
  • Tried to Upgrade with the Windows 10 Media Creation Tool Setup.exe
  • Tried to download and install the next update manually from the Microsoft Update Catalog (https://www.catalog.update.microsoft.com/Home.aspx)
  • Tried updating without Antivir-Software
  • Performed a clean boot and tried to update
  • Disabled and uninstalled drivers of the Intel Wifi and Bluetooth Card, as well as of the Sound controllers in the Device Manager
  • Disabled various I/O devices in the UEFI (WLAN, WWAN, Bluetooth, USB-Ports, Memory Card Slot, Integrated Camera, Integrated Audio, Microphone, Fingerprint Reader, Thunderbolt 3)
  • Deleted the acpi.sys driver file

None of those steps succeeded.

I would be happy about any ideas and suggestions on what to look, to check and try to narrow down the problem and solve it.

Windows for home | Windows 10 | Install and upgrade

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 No comments

10 answers

Sort by: Most helpful
  1. Anonymous
    2021-09-10T08:04:49+00:00

    Another information: As I ran the upgrade tries with the Windows Upgrade Assistant it tried to update straight away to Windows 10 21H1, as I noticed, and not to 20H2 as initially tried by the Windows Update Settings. Maybe to large version jumps could be the problem as well, is there a possibility to conveniently update directly to the next version (2004)?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-09-10T08:00:55+00:00

    Hi Sumit,

    regarding Eset: I saw some logs regarding Authetication Failures with Eset as well in the Event Viewer -> I had uninstalled it in the assumption the issue would be solved by that, if Eset was the problem, but the update still did not work.

    Following the output of reagentc /info:


    Windows Recovery Environment (Windows RE) and system reset configurationInformation: Windows RE status: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: c8dc129d-dd95-11ea-b12c-fa05bf77a38e Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0REAGENTC.EXE: Operation Successful.


    What do you suggest?

    Kind regards,

    Jannik

    Was this answer helpful?

    0 comments No comments
  3. Sumit D - IA 170.7K Reputation points Independent Advisor
    2021-09-10T07:39:23+00:00

    Thanks Jannik.

    >>I had disabled and uninstalled the Realtek sound controller drivers in the Windows Device Manager.

    Realltek PCI E card reader is different from Sound drivers. That is for reading memory cards.

    Secondly, the logs point to multiple issues as I see, and one of them is causing the problem. One is ESET antivirus.

    2021-09-10 08:14:21, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddAntiMalwareFiles (616): Failed to construct file asset [c]: [0x80004005][gle=0x80004005]

    2021-09-10 08:17:45, Warning [SetupHost.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo BCD recovery entry points to invalid location (no winre.wim at C:\Recovery\WindowsRE)

    In the search,

    type cmd, right-click it and choose run as administrator.

    Post the output of reagentc /info command.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-09-10T07:14:20+00:00

    Hello Sumit,

    I had disabled and uninstalled the Realtek sound controller drivers in the Windows Device Manager.

    To be sure, I listet and uninstalled all Realtek drivers and devices, as well as the hidden ones after your comment.

    That didn't help as well.

    You can download the logs from onedrive.

    Note that not all logs are from the same date -> some logs were not available on my drive at every point of time, so I got them from copies of the logs folder I did when the update failed or when viewing them.

    Thanks for your help!

    Sincerely,

    Jannik

    Was this answer helpful?

    0 comments No comments
  5. Sumit D - IA 170.7K Reputation points Independent Advisor
    2021-09-08T07:44:29+00:00

    Hi Jannik,

    I am Sumit here to assist you with this question.

    The driver blames Realtek PCI E Card reader driver. I see that you have tried disabling the same(correct me if I am wrong). Please share the files below for next steps.

    Let us check the Installation log to find why the update failed. Please share the following logs. Please paste the Path in Run directly as the folders may be hidden(Win+R).

    The Panther logs. Files named Setupact.log and Setuperr.log from the following path:

    C:$Windows.~BT\Sources\Panther

    The Rollback logs: These usually are created if Windows Update rolls back. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Rollback

    [Only if the error code is 0xC1900101-0x30018] The Device Install Log from C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

    [Only if the error code is 0xC1900101-20017] Setupact.log and Setuperr.log in %windir%\Panther

    Troubleshoot Feature update Installation failures

    https://answers.microsoft.com/en-us/windows/for...

    To upload files here, see the following article. You must copy the logs to the desktop first and then upload them.

    How to share diagnostic files/logs on the Microsoft community

    https://answers.microsoft.com/en-us/feedback/fo...

    As the log size might be large consider zipping everything before uploading.

    Was this answer helpful?

    0 comments No comments