What issue or error are you experiencing?
After updating PHP from 8.3.29 to 8.3.36 in Local 10.1.2, Windows Smart App Control repeatedly blocked PHP executables and DLL files.
Windows Event Viewer (CodeIntegrity, Event ID 3077) confirms that the following Local PHP components were blocked:
-
php.exe(10 recorded blocks) -
php_mbstring -
php_sodium -
php_fileinfo -
php_sqlite3 -
php_pdo_sqlite -
php_ftp -
Three ImageMagick DLLs
There were 28 blocking events recorded between 07:17 and 07:48 on October 24, 2026 (Japan Standard Time).
Local’s WordPress version indicator remains stuck loading indefinitely, even after restarting Local.
WordPress itself is accessible. The WordPress Site Health screen confirms PHP 8.3.36, and the homepage, pricing page, and WordPress admin dashboard can be opened.
However, we are concerned that PHP extensions and command-line functionality may not be working correctly.
What steps can be taken to replicate the issue?
-
Use Local 10.1.2 on Windows 11 with Smart App Control enabled.
-
Open an existing WordPress site using PHP 8.3.29.
-
Select PHP 8.3.36 from Local’s PHP version dropdown.
-
Apply the update.
-
Observe repeated Smart App Control blocking notifications.
-
Check Windows Event Viewer under
Microsoft → Windows → CodeIntegrity → Operationalfor Event ID 3077. -
Notice that the WordPress version indicator in Local remains stuck loading.
We also checked the PHP binaries. Both PHP 8.3.29 and PHP 8.3.36 were reported as unsigned (NotSigned).
The WordPress site was backed up before updating PHP. No Windows security settings have been disabled.
System Details
-
Local Version: 10.1.2
-
Operating System: Windows 11, version 25H2, build 26200.9711
-
Smart App Control: Enabled
-
PHP version before update: 8.3.29
-
PHP version after update: 8.3.36
-
Web server: nginx
-
Database: MySQL 8.4.0
Questions for Local Support
-
Is this a known compatibility issue between Local’s PHP 8.3.36 binaries and Windows Smart App Control?
-
Can Local provide signed or otherwise Smart App Control-compatible PHP executables and extensions?
-
Is there an officially supported way to resolve this issue without disabling Smart App Control or downgrading PHP?
-
Could the blocked
php.exeexplain why Local cannot retrieve the WordPress version? -
Are there any plans to release an updated PHP 8.3.36 package addressing this issue?
We would appreciate a secure resolution that allows us to continue using Local without weakening Windows security.
We can provide redacted CodeIntegrity Event ID 3077 details if needed. We have not attached Local logs because they may contain sensitive information.