Setup Failure - 0xc1900101

Caledon Ken · Thursday at 11:11 AM

Running Windows 11 Pro V23H2 (22631.4751)

Yesterday I was offered the upgrade to 24H2. I did the restart, it didn't process very long, did a reboot and BSOD'ed.

Setup Failure - 0xc1900101

It rolled back successfully. I did have Super Anti Virus and Malwarebytes running. Did the same upgrade on another computer, same AV's no issues. I would add the upgrade to 11 and the subsequent upgrade to 23H2 had the AV's running.

Checked drivers - two reporting difficulties (they were hidden) SASDIFSV and SASKUTIL ( assume they are part of Super Anti Spyware)
Drive C has 112GB free.
Scanned C: no errors
Recently ran SFC /scannow and it repaired errors. That was in last three days.
I pause updates, and removed Power Toys (not using anyway), Malwarebytes and Super Anti Spyware. ( I know they recommend removing AV, I was lazy on initial run)
Resumed updates and was not offered the 24H2 update. Checked again today, still not being offered.
Reinstall Malwarebytes.

System Specs for System 1 should be used, they are up to date.

Used the BSOD log Collector V2 and Matthew's Update Failure bat. Both Zip files on Onedrive.

Zip files deleted

One question, after running these log collectors are there any files I need to clean up within my system other than the two zip files. Was reading thread with Matthew's bat file and there was some mention GenFileList?

As Windows in not offering the update to me I assume there is a Microsoft initiated block on my system.

If further info is required I will collect.

If the root caused can be identified I would appreciate.

Thank you.

FreeBooter · Thursday at 12:00 PM

The error code 0xC1900101 is a generic rollback code that indicates an incompatible driver. This error can occur when trying to install a system update or upgrade to the latest Windows version.

Here are some things you can try to fix this error:

Check your internet connection
Run the Windows Update Troubleshooter
Free up disk space
Update your drivers
Uninstall third-party antivirus software
Upgrade BIOS

SetupDiag

SetupDiag works by examining Windows Setup log files. This article shows how to use the SetupDiag tool to diagnose Windows Setup errors.

learn.microsoft.com

FreeBooter · Thursday at 12:01 PM

Windows 10 upgrade resolution procedures - Windows Client

Discover general troubleshooting procedures for dealing with 0xC1900101, the generic rollback code thrown when something goes wrong during a Windows 10 upgrade.

learn.microsoft.com

Caledon Ken · Thursday at 3:41 PM

Thanks

My Internet connection is all wired and I move very large files to the net without issue.
As documented in my post I have 112GB free on C:
No drivers report issues and all are up to date. Did have two from SAS reporting issues, uninstalled SAS
I will uninstall AV's next time I'm offered 24H2
There is no BIOS update available
I can look at Update trouble shooter but this is the first failed update. Either patch Tuesday or Feature.

Caledon Ken · Thursday at 3:48 PM

Okay Update Trouble shooter found -- results below --- it didn't fix anything and listed as "I" which I assume is informational. Ran again, same results so it is not "Fixing" anything

IsPostback_RC_PendingUpdates

IsPostback: False

WaaSMedicService

Issue found by:BinaryHealthPlugin;DynamicProtectionPlugin

IsPostback_RC_PendingUpdates

IsPostback: True

Service Status

Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException

Service Status

Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException

Collection information
Computer Name:	XCODE
Windows Version:	10.0
Architecture:	x64
Time:	Thursday, January 30, 2025 3:43:32 PM

dacrone · Thursday at 3:55 PM

Download the iso, disconnect Ethernet and upgrade

Caledon Ken · Thursday at 4:12 PM

As my system is on a block list I'm reluctant to force an inplace upgrade. In my original thread zbook recommended I post in BSOD with information files requested.

zbook · Thursday at 5:17 PM

Some findings:

a) BSOD
b) problems with digital signatures
c) Microsoft Windows 11 Pro Build: 22631
d) upgrade failure error code 0xC1900101, 0x20017
e) problems with user mode drivers apple, smart card

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums

2) Run setupdiag > post a share link

https://go.microsoft.com/fwlink/?linkid=870142

3) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

4) Create a new restore point

Create System Restore Point in Windows 11

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

5) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

6) Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

7) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

Customized tests will then be posted for the next run of WDV.

WDV can run continuously during the testing.

For any BSOD post a new V2 share link into the newest post.

Code:

2025-01-29 14:53:43, Info                  SP     LastCrashDumpInfo: BugcheckCode 133

Code:

Event[1280]
  Log Name: System
  Source: Service Control Manager
  Date: 2025-01-04T21:15:03.9630000Z
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: XCode
  Description:
The SASKUTIL service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Code:

Event[7746]
  Log Name: System
  Source: Service Control Manager
  Date: 2025-01-29T09:00:04.1600000Z
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: XCode
  Description:
The SASDIFSV service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Code:

Event[8178]
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2025-01-29T14:56:11.8000000Z
  Event ID: 20
  Task: Windows Update Agent
  Level: Error s
  Opcode: Installation 
  Keyword: Installation,Failure,
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description:
Installation Failure: Windows failed to install the following update with error 0xC1900101: Windows 11, version 24H2.

Code:

Event[8065]
  Log Name: System
  Source: volmgr
  Date: 2025-01-29T14:55:22.4110000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: XCode
  Description:
Crash dump initialization failed!

Code:

Event[4943]
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2025-01-19T12:17:23.9090000Z
  Event ID: 10110
  Task: User-mode Driver problems.
  Level: Critical 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Event[4944]
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2025-01-19T12:17:23.9160000Z
  Event ID: 10116
  Task: User-mode Driver problems.
  Level: Critical 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description:
The device Apple iPhone (location 0000.0014.0000.014.006.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Event[4945]
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2025-01-19T12:17:23.9160000Z
  Event ID: 10116
  Task: User-mode Driver problems.
  Level: Critical 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description:
The device Apple Mobile Device USB Device (location 0000.0014.0000.014.006.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Event[4946]
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2025-01-19T12:17:23.9170000Z
  Event ID: 10116
  Task: User-mode Driver problems.
  Level: Critical 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XCode
  Description:
The device Microsoft Usbccid Smartcard Reader (WUDF) (location 0000.0014.0000.003.001.000.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process.  Please contact the device manufacturer for more information about this problem.

Caledon Ken · Friday at 7:13 AM

Thanks zbook.

So as I look over those findings I see the two SAS drivers I identified are clearly identified and those are the digital signatures issues. It states those drivers could not be verified, from your code boxes, and driver verification is necessary for the update hence it crashed. The 0xC1900101 - 0x20017 is listed as a driver error in MS's documentation. (This covers your findings b) and d) )

The Apple and Smart card errors are a result of devices not being connected which I understand is the correct way to proceed with an update. (finding e))

The above basically encompasses the findings other than it BSOD'ed, find a) and I'm on Windows 11, findings c).

Given this I think my first course of action should be, remove Malwarebytes, take a system image and try again.

I will report back.

I'll also start to work through list.

Megahertz · Friday at 7:48 AM

I had some issues with Win 11 24h2 so I restored the Win 11 23h2 image backup.
Had seen may issues with 24H2 so I would stay with 23h2

Caledon Ken · Friday at 7:54 AM

Thanks for the feedback. Interesting that MS says it good to go and is basically rolling it out by force.

zbook did some great work on my BSOD. Sure enough the SAS drivers were involved in the failure.

zbook · Friday at 2:14 PM

Uninstall Super antispyware using the applicable uninstall tool:

https://secure.superantispyware.com/SASUNINST64.EXE?_gl=1*v9kd50*_gcl_au*MTU3MDI0NTY1OS4xNzM4Mjc1ODQ3

SUPERAntiSpyware FAQ - How do I uninstall SUPERAntiSpyware?

Frequently Asked Question: How do I uninstall SUPERAntiSpyware?

www.superantispyware.com

Caledon Ken · 2025-02-03T08:57:20-0500

Thanks zbook for doing the actual analysis. I hope I rep'ed you properly.

zbook · 2025-02-03T11:59:44-0500

Please update the version or build.

Caledon Ken · 2025-02-04T09:47:04-0500

Okay. once I move to 24H2

Setup Failure - 0xc1900101

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Wish to be flying

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar threads