Windows 11, version 24H2 Install error and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGR.sys)

Question

Hi,

When trying to update from 23H2 TO 24H2 via Windows Update, it fails with this error:-

"Windows 11, version 24H2 Install error - 0xc1900101"

"The Windows 11 version 24H2 install error with code 0xc1900101 is typically a driver-related issue. This error is a generic rollback code that often appears during upgrade or installation when the system encounters incompatible drivers, hardware conflicts, or corrupt system files."

After installing update and rebooting, it gives a BYOD of SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGR.sys) and sometimes APC_INDEX_MISMATCH (NTFS.sys).

I would really like some assistance on this as I have been working to fix this for the past two weeks now. The device is an Optiplex 7060.

Thank you.

Answer 1

Thank you very much! I will try this and let you know what happens.

Answer 2

The error code 0xc1900101 during the upgrade from Windows 11 version 23H2 to 24H2 is indeed commonly associated with driver-related issues. Here are some steps you can take to troubleshoot and potentially resolve the problem:

1. Check Device Manager for Driver Issues: Open Device Manager and look for any devices with a yellow exclamation mark. This indicates a driver issue. Right-click on these devices and select Update Driver Software or Uninstall to reinstall the drivers.
2. Update All Drivers: Ensure that all drivers, especially for critical components like network adapters and storage controllers, are up to date. You can check the manufacturer's website for the latest drivers.
3. Review Event Logs: Use Event Viewer to check for any logs that might indicate hardware or driver conflicts during the upgrade process.
4. Check for Third-Party Software Conflicts: Sometimes, third-party antivirus or security software can interfere with the upgrade process. Consider temporarily disabling or uninstalling such software before attempting the upgrade again.
5. Ensure BIOS is Updated: Check if there are any BIOS updates available for your Optiplex 7060. An outdated BIOS can sometimes cause compatibility issues.
6. Repair Unsigned Drivers: If you have any unsigned drivers, consider repairing or removing them, as they might not be compatible with the new version of Windows.
7. Backup and Recovery Plan: Always ensure you have a backup and recovery plan in place before performing major updates, especially in production environments.

If the issue persists after trying these steps, you may need to consider a clean installation of Windows 11 version 24H2 as a last resort.

Answer 3

Hello VP,

I did run the setupdiag tool and have the two logs. Would it be possible to sent you the setupact and setupper logs? I do not really understand what is going on in them.

I did update the drivers and BIOS on the computer using the Dell too when I started investigating this issue. The only antivirus software we use is SentinelOne in our workplace. I did run the fltmc filters command to see what drivers might be causing the issue. The drivers it showed me are bindflt, UCPD,SysmonDrv, SentinelMonitor, ElasticEndpointDriver, storqosflt, wcifs, WIMMount, CldFlt, bfs, CmgPassThrough, CmgShieldFFE, FileCrypt, luafv, npsvctrig, Wof, FileInfo and WinSetupMon. I tried disabling a few of these but I guess now I'll look into seeing if I can uninstall these.

On the topic of memory integrity, when I attempted to turn it on, it said there were incompatible drivers on the system preventing it from being turned on. It showed me one incompatible driver and after uninstalling, I was still unable to turn it on. After doing a good amount of research, I found that a dell driver called DDDriver64Dcsa.sys that makes memory integrity not turn on. Not sure if it was related in anyway but saw a few discussions post that said they were able to upgrade after fixing the memory integrity issue.

Along with that, on the computer I am testing on, I used to be able to mount the install file and run the setup for 24H2. On the restart, it would just give me a BYOD screen stating the errors I mentioned in the question. But after uninstalling the DDDriver64Dcsa.sys driver, at the end of the setup, a small box appears that says "Windows 11 Installation has failed". The easiest solution would be to do a clean install but there are a lot of computers with specific applications on them so that would not be feasible. If there is any way I can send you the logs then please let me know. Thank you for your message.

Rubal

Answer 4

Hello Rubal Pradhan,

The combination of error 0xc1900101 with FLTMGR.sys (Filter Manager) and NTFS.sys Stop codes during the reboot phase is a strong indicator that a file system filter driver, typically belonging to antivirus software, disk encryption tools, or storage controllers, is causing a kernel-level conflict when the OS attempts to migrate data to the new 24H2 WIM image. Since FLTMGR.sys coordinates the I/O operations between the file system and drivers, a crash here means the upgrade process is being intercepted and killed by a driver that isn't compatible with the 24H2 kernel changes.

To pinpoint the exact driver causing the rollback, you should download and run the SetupDiag tool directly from Microsoft's Learn repository. This utility parses the C:\$Windows.~bt\Sources\Panther\setupact.log and generates a SetupDiagResults.xml file that will usually explicitly name the driver (e.g., iaStorA.sys, symefasi.sys, etc.) responsible for the failure. While you are doing that, you must address the Dell Optiplex 7060 specifics. This model often defaults to "RAID On" in the BIOS SATA Operation settings, which utilizes the Intel Rapid Storage Technology (RST) driver. You need to navigate to the Dell support page for the Optiplex 7060 and install the latest Intel Rapid Storage Technology Driver and the latest BIOS firmware update. The generic drivers Windows Update pulls are often insufficient for the storage controller migration in 24H2.

Furthermore, because FLTMGR.sys is involved, you must fully uninstall (not just disable) any third-party antivirus, firewall, or VPN software (such as Sophos, McAfee, or Bitdefender) before attempting the upgrade again. Disabling these programs leaves their filter drivers hooked into the kernel stack, which continues to cause the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED crash. Additionally, navigate to Windows Security > Device Security > Core isolation and ensure Memory integrity is toggled Off. The 24H2 update enforces stricter driver code integrity, and older drivers on the Optiplex 7060 attempting to load in the new environment can trigger these specific BSODs if Memory Integrity is active during the install. Once the BIOS and storage drivers are updated, third-party security apps are removed, and Memory Integrity is disabled, perform the upgrade again using the Windows 11 24H2 ISO (mount it and run setup.exe) rather than Windows Update for a more stable install path.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Answer 5

Hello VP,

Thank you for your response. I have the logs from the SetupDiag but I am unsure on what driver might be causing the computer to crash. If it is possible, I would like to send them to you to investigate, During the start of my troubleshooting, I did install the DellSupport Assist to update the BIOS and drivers.

I also ran the fltmc filters command and it gave me some drivers as well. There are a few drivers which I disabled but it still juggled between the two errors. The only 3rd party antivirus that is installed on the devices is SentinelOne. Disabling it caused the APC_INDEX_MISMATCH (NTFS.sys) error.

The computer was not letting me turn on memory integrity. It gave me a specific driver that was incompatible but after uninstalling it, it still said that there were incompatible drivers present on the computer. I found another driver named DDDriver64Dcsa.sys from online discussions which was causing this issue for other people. I renamed it to DDDriver64Dcsa.off just to disable it and I was able to turn on memory integrity. I am only mentioning this because I saw a few discussion posts that told me being unable to update and unable to turn on memory integrity might be related. I wanted to get your thought on this as well.

Thank you again for your response. I hope to hear from you soon.