<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to SysProcessCreate stopped working after SP21?</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ce10989980/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ce10989980/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/ce10989980/</id><updated>2026-02-03T06:42:54.732000Z</updated><subtitle>Recent posts to SysProcessCreate stopped working after SP21?</subtitle><entry><title>SysProcessCreate stopped working after SP21?</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ce10989980/?limit=25#7b10" rel="alternate"/><published>2026-02-03T06:42:54.732000Z</published><updated>2026-02-03T06:42:54.732000Z</updated><author><name>ringbaked</name><uri>https://forge.codesys.com/u/ringbaked/</uri></author><id>https://forge.codesys.comc9a2464fc2d347d122e944eb18ae2dc14602b5c6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I ran into something similar after updating to SP21. It’s not really documented well, but the runtime isolation became stricter.&lt;br/&gt;
First test something very simple like:&lt;br/&gt;
pszApplicationName := 'C:\Windows\System32\notepad.exe';&lt;br/&gt;
pszCommandLine := '';&lt;/p&gt;
&lt;p&gt;If that fails, it's definitely security context.&lt;br/&gt;
Alternative architecture&lt;br/&gt;
In some projects we moved the external executable into:&lt;br/&gt;
PlcLogic\&lt;br/&gt;
and executed it from there only.&lt;br/&gt;
&lt;a class="" href="https://geometrydashlite2.io" rel="nofollow"&gt;Geometry Dash Lite&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>SysProcessCreate stopped working after SP21?</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ce10989980/?limit=25#1941" rel="alternate"/><published>2026-02-02T23:06:21.073000Z</published><updated>2026-02-02T23:06:21.073000Z</updated><author><name>nickpoon</name><uri>https://forge.codesys.com/u/nickpoon/</uri></author><id>https://forge.codesys.com61f4c6a7863e9573c45eb571aa06cd108b4b27ab</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'm going through the process of updating the CODESYS Project a machine to 3.5 SP21 (old version was 3.5 SP20). One function that stopped working when upgrading was SysProcessCreate.&lt;/p&gt;
&lt;p&gt;I need to run a .exe file that is located in C:\Program Files\MQTTStream. Some initial searching suggested that there are new security rules that prevent the SoftPLC from reading/writing files to outside of its Device folder (located here - C:\Windows\System32\config\systemprofile\AppData\Roaming\CODESYS\CODESYSControlWinV3x64\24FD6770)&lt;/p&gt;
&lt;p&gt;Relocating files helped fix my JSON file reader/writer functions (which were failing previously), but not the case for SysProcessCreate.&lt;/p&gt;
&lt;p&gt;I've even attempted to just run window's cmd.exe and with:&lt;br/&gt;
pszCommandLine = 'cd /d C:\Windows\System32\config\systemprofile\AppData\Roaming\CODESYS\CODESYSControlWinV3x64\24FD6770\PlcLogic\MQTTStream &amp;amp; sift-proxy.exe --grpc_uri="https://grpc-api.siftstack.com" --api_key="Hc9wIPKE1s4eNGYa34t2CiIv91CeP4J4UIadWmgp" mqtt-client --broker_ip=10.0.10.101 --broker_port=1883 --config_file="mqtt_telemetry_config.json" --username Plantd --password 1234 --stream_metrics --storage_path="sift-proxy-logs"'&lt;/p&gt;
&lt;p&gt;I have not been able to find a lot of documentation on this, and I suspect the new update may have created a bug for SysProcessCreate.&lt;/p&gt;
&lt;p&gt;Any help would be greatly appreciated&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>