# Some problems installing v2027.0.0 in Windows 11

**URL:** <https://scilab.discourse.group/t/some-problems-installing-v2027-0-0-in-windows-11/1227>\
**Category:** General usage\
**Created:** [October 18, 2026, 2:47pm UTC](https://scilab.discourse.group/t/some-problems-installing-v2027-0-0-in-windows-11/1227 "2026-10-18T14:47:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![martrant](https://avatars.discourse-cdn.com/v4/letter/m/e19b73/32.png) [@martrant](https://scilab.discourse.group/u/martrant)\
**Post date:** [October 18, 2026, 2:47pm UTC](https://scilab.discourse.group/t/some-problems-installing-v2027-0-0-in-windows-11/1227/1 "2026-10-18T14:47:58Z")

</div>

Installing v2027.0.0 in Windows 11 (26H2) had certain problems which are likely  
caused by the (default: ON in ordinary Win11 installations) “Smart App Control”  
of Windows 11.  
I’m describing below my personal experience, so that fellow users will be aware  
of these potential issues and avoid the un-necessary hassle and angst.

Upon running the newly-installed Scilab v2027 app, two pop-ups inform the user that:

a. “You chose to install Scilab with the fftw module.  
This module requires: C:/PROGRA~1/SCILAB~1.0/bin/libfftw3-3.dll (GPL licence)  
Scilab will use standard fft by default until you install this library.  
See help fftw for more information.”

```auto
My comment: But this .dll WAS actually installed in the right folder, 
            so I gathered (a posteriori, of course) that probably Windows
            "Smart App Control" somehow prevented its registration in Windows.                             

```

b. “C:\Program Files\scilab-2027.0.0\bin\external\_objects.dll is  
either not designed to run on Windows or it contains an  
error. Try installing the program again using the original  
installation media or contact your system administrator or the  
software vendor for support. Error status 0xc0e90002”

```auto
 My comment: Same as above.

```

So, given that the installation of v2027.0.0 was indeed botched, I proceeded  
to uninstall it, in the usual way, using Windows Settings → Apps. But again  
I got a pop-up explaining that Smart App Control would not allow the uninstaller  
executable to run because it could not verify its creator. Fine, I thought,  
I’ll just disable the Smart App Control and then uninstall & re-install v2027.0.0.  
This I did, and everything went fine and dandy, and v2027 was installed and launched  
without a hitch, and I tested it against some .sce files of my own, and everything  
went as expected.  
Then, I proceeded to re-enable Smart App Control in Windows 11 (yes, I know, but  
I happen to be octogenarian+, so, likely to overlook something fishy, therefore  
better to play safe, esp. with an idiotic OS like windows.) But, alas, no dice,  
I was met with a greyed-out selection button for “ON” and no way to re-enable  
Smart App Control in Windows Settings.  
Googling, I found this was a known issue after the October update for Windows 11,  
and there was a temp fix by Microsoft to repair this issue by adding two Windows  
Registry settings and restarting the computer, as explained here:

```auto
https://www.windowsdigitals.com/smart-app-control-grayed-out-kb5127648/

```

I hope the future v2027.0.1 will take care of the uninstaller being a persona-non-grata  
with Windows Smart App Control. I assume this hassle happened because v2027.0.0 was likely  
developed and tested (before release) in Windows 11 PCs which were configured to be in  
“Developer” mode. In this mode, a lot of ordinary system security checks are pre-set to “OFF”  
by default.

All the best and happy Scilabbing everyone.