0xC1900101- 0x4001C when I try to update to 22581

Question

I'm still stuck at 22563, every time I update a new version it fails with the same error code: 0xC1900101- 0x4001C, I tried all the methods I could find, it just doesn't work . guys i need your help！

1.I ran SetupDiag and below are the results：

DebugSetupCrash
Found qualifying memory dump during setup, but the debugger binaries were not found. Either examine the memory dump here: C:\$WINDOWS.~BT\Sources\Rollback\WER\ReportQueue\AppCrash_lsass.exe\WER.tmp.mdmp or install the debugger tools from here: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/ to determine the failure.

Last Setup Phase:
Phase Name: Pre OOBE Boot
Phase Started: 3/25/2022 1:16:27 AM
Phase Ended: 1/1/0001 12:00:00 AM
Phase Time Delta: 00:00:00
Completed Successfully? False

Last Setup Operation:
Operation Name: Upgrade security
Operation Started: 3/25/2022 1:15:21 AM
Operation Ended: 3/25/2022 1:15:21 AM
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? True

2.I opened the mdmp file mentioned above using debug,Below is the result of the analysis:

STACK_COMMAND: ~3s ; .cxr ; kb

SYMBOL_NAME: ntdll!RtlFailFast2+0

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

FAILURE_BUCKET_ID: FAIL_FAST_GUARD_ICALL_CHECK_FAILURE_ETWCALLBACK_c0000409_ntdll.dll!RtlFailFast2

OS_VERSION: 10.0.22581.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22581.1

FAILURE_ID_HASH: {cf677f7f-b4bd-97c0-e611-9227fd12e484}

Followup: MachineOwner

Answer 1

Hi 19001014001C-3890 ,

Please run these log collectors and scripts and post share links into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

https://www.tenforums.com/attachments/bsod-crashes-debugging/349147d1634733899-post-problem-reports-here-batch-files-use-bsod-debugging-setupdiag_-_upgrade_failure-2021-10-20-.bat

Administrative command prompt:
PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a separate share link for the memory dump.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

Hi LukeJohnson-9300 ,

Please open a new thread and post a link into this thread.

In the new thread post a share link for :

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/346094d1631611972-post-problem-reports-here-batch-files-use-bsod-debugging-collect_logs_from_event_viewer-2021-09-14.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Read this link on Windows Driver Verifier (WDV): https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
(Do not use the tool until it is communicated in the thread)

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 3

Hi @19001014001C

There is an ongoing issue with some Windows users upgrading from this Insider Preview version of Windows 11. We are waiting for a fix for this from Microsoft.

In the meantime, you could try removing all external devices in case it's a driver it's complaining about.

I hope this answers your question.

Thanks.

--
--If the reply is helpful, please Upvote and Accept as answer--