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

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.

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

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.

Hello Rubal Pradhan,

You have identified the two high-probability causes here: the SentinelOne agent and the legacy Dell drivers. The error APC_INDEX_MISMATCH in NTFS.sys typically occurs when a file system filter driver makes a system call at the wrong IRQL (Interrupt Request Level). In your case, simply disabling SentinelOne does not unload its kernel-level filter drivers; they remain attached to the file system stack to prevent tampering, even if the user interface says "Disabled." When the Windows 24H2 setup attempts to migrate the file system structure, these dormant hooks clash with the new kernel, causing the crash. You must completely uninstall SentinelOne. If this is a managed corporate device, you will likely need the "Uninstall Password" from your management console or use the specific SentinelOneCleaner.exe utility (if available to you) to strip the drivers from the System32/drivers folder completely.

Regarding the DDDriver64Dcsa.sys and Memory Integrity, your instinct is correct that these issues are related. This specific driver belongs to the Dell Data Vault Control Device (often part of Dell SupportAssist). The fact that this driver blocked Memory Integrity confirms it is code-integrity incompatible. While renaming the extension to .off stops it from loading, it is safer to remove the service entirely to prevent the OS from attempting to call it during the migration phase. Open an elevated Command Prompt and run sc delete DDVDataCollector and sc delete DDVRules. If you still have Dell SupportAssist or Dell Data Vault installed in Control Panel, uninstall them temporarily. For the upgrade process, keep Memory Integrity (Core Isolation) OFF. We want to minimize the strictness of driver checks during the delicate upgrade phase; you can re-enable it after 24H2 is successfully installed.

Since you can't send me the logs here, you can extract the critical data from the SetupDiagResults.xml yourself. Open that file in a browser or Notepad and look for the <FailureData> tag. If that is generic, open the C:\$Windows.~bt\Sources\Panther\setupact.log file and search (Ctrl+F) for the string FATAL. Look for lines immediately preceding the fatal error that reference "Move File," "Driver," or "Filter." If you see references to SentinelMonitor.sys, S1Agent.sys, or similar, it confirms the antivirus is the blocker. Once SentinelOne is fully uninstalled and the Dell Data Vault services are deleted, attempt the upgrade again using the ISO method.

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