<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Could not write options file at...</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/63c353334d/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/63c353334d/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/63c353334d/</id><updated>2026-09-07T06:20:05.048000Z</updated><subtitle>Recent posts to Could not write options file at...</subtitle><entry><title>Could not write options file at...</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/63c353334d/?limit=25#61ab" rel="alternate"/><published>2026-09-07T06:20:05.048000Z</published><updated>2026-09-07T06:20:05.048000Z</updated><author><name>AntonZ</name><uri>https://forge.codesys.com/u/antonz/</uri></author><id>https://forge.codesys.com07b12260e08ac65844c23d08f7beedf68df3b9d1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I ran into a similar issue, albeit not the exact same conditions nor the same file if I recall correctly. As a workaround I have used an elevated account to give my regular user account write access to the specific directory where the failure occurred. &lt;/p&gt;
&lt;p&gt;It is not pretty and I am not happy with it. It does work.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Could not write options file at...</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/63c353334d/?limit=25#6a93" rel="alternate"/><published>2026-09-04T16:36:35.265000Z</published><updated>2026-09-04T16:36:35.265000Z</updated><author><name>bigwhig</name><uri>https://forge.codesys.com/u/bigwhig/</uri></author><id>https://forge.codesys.coma9d08435114f842d91b6419680d5af5f6fdaedad</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Using Codesys 3.5.21.5. Tried installing both by full .exe file and using codesys installer. Installation requires elevation and completes just fine. However when running Codesys and closing the IDE, options-files are not written:&lt;/p&gt;
&lt;p&gt;&lt;img alt="" rel="nofollow" src="https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/e/e12fc5495f96a4f5cdcedf5edb06344525a146d4.png"/&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" rel="nofollow" src="https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/2/23b69aa31796f95f4c91d790bfdd416d3295f3bb.png"/&gt;&lt;/p&gt;
&lt;p&gt;Seems regular users are only given read-access to these files:&lt;br/&gt;
&lt;img alt="" rel="nofollow" src="https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/1/18bcff07f91e8eb4d500e07c6028a707b95a1331.png"/&gt;&lt;/p&gt;
&lt;p&gt;Running Codesys as admin works as admins have full access. Haven’t been necessary before to run as admin.&lt;/p&gt;
&lt;p&gt;Don’t think I have the issue on my work-laptop, but have experienced this on a number of other computers. Above screenshots are from my private stationary running Windows 11 Pro:&lt;br/&gt;
&lt;img alt="" rel="nofollow" src="https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/c/c115048e07fa4d4d276086099e3864e88aa2afe0.png"/&gt;&lt;/p&gt;
&lt;p&gt;Anyone else experiencing this? Is this by design or a known issue?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>