<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/</id><updated>2026-02-06T07:18:03.051000Z</updated><subtitle>Recent posts to Creating Boot Application not working</subtitle><entry><title>Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/?limit=25#cd9c" rel="alternate"/><published>2026-02-06T07:18:03.051000Z</published><updated>2026-02-06T07:18:03.051000Z</updated><author><name>bendsmug</name><uri>https://forge.codesys.com/u/bendsmug/</uri></author><id>https://forge.codesys.com0bc4969572566f4e86709bc233860a56185dfebf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I appreciate your insights on the boot application issue. One perspective to consider is the importance of debugging logs in identifying root causes—perhaps a dedicated session for log analysis could lead to quicker &lt;a href="https://basketballstarsonline.io" rel="nofollow"&gt;basketball stars&lt;/a&gt; resolutions? It might foster collaboration among users facing similar challenges!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/?limit=25#898b" rel="alternate"/><published>2025-09-04T12:36:57.290000Z</published><updated>2025-09-04T12:36:57.290000Z</updated><author><name>leandroct</name><uri>https://forge.codesys.com/u/leandroct/</uri></author><id>https://forge.codesys.com4b45b828de27b5b91d8678f3d9af2c9faac00283</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I did this steps and it worked:&lt;br/&gt;
- Copied Application.app e Application.crc to the Folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\&amp;lt;id_da_cpu&amp;gt;\PlcLogic\Application\&lt;br/&gt;
copied the visu folder content to the folder  C:\ProgramData\CODESYS\CODESYSControlWinV3x64\&amp;lt;id_da_cpu&amp;gt;\PlcLogic\Application\visu\&amp;lt;/id_da_cpu&amp;gt;&amp;lt;/id_da_cpu&amp;gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Changed by Notepad the CODESYSControl.cfg at the folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\&amp;lt;id_ da_cpu=""&amp;gt;\&lt;br/&gt;
Where is &lt;span&gt;[CmpApp]&lt;/span&gt;, addng a line with: Application.1=Application&amp;lt;/id_&amp;gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/?limit=25#f65e/c52b" rel="alternate"/><published>2025-09-04T08:27:33.648000Z</published><updated>2025-09-04T08:27:33.648000Z</updated><author><name>chloereed</name><uri>https://forge.codesys.com/u/chloereed/</uri></author><id>https://forge.codesys.com2e262f4144bc980dedd8a8c0fe7995d45b28754d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;From what you describe, the boot application files are in the right place, but the key step you’re missing is how the runtime knows which application to load. In most cases with CODESYS Control Win, you don’t need to edit CodesysControl.cfg manually. Instead, once you’ve created the boot application (Application.app and .crc), copy them into the runtime instance directory (for example …\E84889DB), then restart the service. The PLC should automatically detect Application.app and start it. If TargetVisu still doesn’t open, double-check that the visualization settings are enabled for TargetVisu (Project → Devices → Visualization), and that you built the project with visualization included before creating the boot application. Editing the config is rarely required unless you’re running multiple applications &lt;a class="" href="https://ballorbit.github.io" rel="nofollow"&gt;ball orbit&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/?limit=25#f65e/177a" rel="alternate"/><published>2025-09-04T08:27:25.584000Z</published><updated>2025-09-04T08:27:25.584000Z</updated><author><name>chloereed</name><uri>https://forge.codesys.com/u/chloereed/</uri></author><id>https://forge.codesys.com77eea04bfee461ac23bb4aebd100ad7d695c681b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;From what you describe, the boot application files are in the right place, but the key step you’re missing is how the runtime knows which application to load. In most cases with CODESYS Control Win, you don’t need to edit CodesysControl.cfg manually. Instead, once you’ve created the boot application (Application.app and .crc), copy them into the runtime instance directory (for example …\E84889DB), then restart the service. The PLC should automatically detect Application.app and start it. If TargetVisu still doesn’t open, double-check that the visualization settings are enabled for TargetVisu (Project → Devices → Visualization), and that you built the project with visualization included before creating the boot application. Editing the config is rarely required unless you’re running multiple applications &lt;a class="" href="https://ballorbit.github.io" rel="nofollow"&gt;ball orbit&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Creating Boot Application not working</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/f9fa0cbe72/?limit=25#f65e" rel="alternate"/><published>2025-09-03T18:30:53.868000Z</published><updated>2025-09-03T18:30:53.868000Z</updated><author><name>leandroct</name><uri>https://forge.codesys.com/u/leandroct/</uri></author><id>https://forge.codesys.com2d40cf5a733a14705c8431c5ab76cf279f58e6ad</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have a Control Win V3.5 SP20 (64-bit) application, and until now, I open the program (with a password) and download it. However, I need to give the client the option to install the program on the Controller, without them having to open it and access the code. So, I followed these steps:&lt;br/&gt;
1 – In the Online =&amp;gt; Create Boot Application menu, I saved the generated files in a directory:&lt;br/&gt;
Application.app&lt;br/&gt;
Application.crc&lt;br/&gt;
PlcLogic\visu\ directory with several files&lt;br/&gt;
2 – In the SysTray, I ran the PLC, and it created a directory. In the root of this directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E84889DB), I pasted Application.app and Application.crc.&lt;br/&gt;
Since it created a \visu directory, I pasted the PlcLogic\visu\ files generated in Create Boot Application into it.&lt;br/&gt;
3 - In the general Codesys directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64), I edited CodesysControl.cfg, adding:&lt;br/&gt;
&lt;span&gt;[CmpLog]&lt;/span&gt;&lt;br/&gt;
Application.1=Application&lt;br/&gt;
4 - When running the PLC, nothing happens and the TargetVisu screen does not open.&lt;br/&gt;
What I'm doing wrong?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>