Why do I get an "Core isolation memory integrity" error when starting my Simulink Desktop Real-Time simulation?

Why do I get the following error message when starting my Simulink Desktop Real-Time (SLDRT) simulation in R2023a Update 4 or later, although it previously worked with no problems on the same Windows computer?

Error reported by S-function 'sldrtsync' in 'sldrt_model/Real-Time Synchronization':

Simulink Desktop Real-Time is not compatible with the Core isolation memory
integrity feature. Please type 'sldrtkernel -setup' and reinstall the
real-time kernel to disable Core isolation memory integrity.

Answer 1

[MathWorks Support Team]

What This Issue Means

Since R2023a Update 4, Simulink Desktop Real-Time (SLDRT) issues an error if it detects that the Core Isolation Memory Integrity feature of Windows is enabled. See this Microsoft Support page for more information on this operating system feature:

Device Security > Core Isolation > Memory Integrity - Microsoft Support

Unfortunately, the Core Isolation Memory Integrity feature is incompatible with the real-time kernel, and recent builds of Windows 11 turn the feature on by default. So if you encounter the reported error message, it could be that the feature has been re-enabled on your Windows system through an IT system update.

Try This Workaround

Option 1: Re-run the SLDRT kernel setup

Since R2023a Update 4, we try to automatically disable the Core Isolation Memory Integrity feature during real-time kernel installation. Re-run the setup as suggested by the error message:

>> sldrtkernel -setup

Restart your computer and verify that your model runs in the real-time kernel now.

Option 2: Consult your system administrator

If running "sldrtkernel -setup" doesn't work, it means that you might not have the necessary permissions to change the Core Isolation Memory Integrity settings, or that system settings or security policies managed by IT have reverted the change. Consult your IT system administrator to disable this feature on your Windows system, as it is incompatible with the real-time kernel. If IT policies prevent this, consider using an offline PC with fewer restrictions or a dedicated environment where the feature can be safely disabled without compromising security.