https://devzone.nordicsemi.com/f/nordic-q-a/42928/nrf-connect-for-desktop-windows-startup-switches-to-escape-path-special-charactersRunning into this with nRF Connect v2.6.1 for Windows What happens is that the top-level app installs and runs fine, any apps that are added and launched within (or directly using a shortcut) fail with a popup error window saying: Tried to invokeen-USTelligent Community 13Fri, 25 Jan 2019 15:06:15 GMThttps://devzone.nordicsemi.com/thread/167990?ContentTypeID=1Fri, 25 Jan 2019 15:06:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8173fe84-c4d5-4cd6-b13d-061d535774a5J&#248;rgen Holmefjord<p>I have reported your issue to the developers.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167705?ContentTypeID=1Thu, 24 Jan 2019 15:30:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ea4bcc20-41e5-4108-8241-0f108f45f5f8talknk<p>Unsure how to force the apps to use them inside the application without changing the code; unless there is a flag/switch to pull that inheritance into the application?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167703?ContentTypeID=1Thu, 24 Jan 2019 15:26:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b3e7f569-ee3e-4bc3-975a-6357e83f90c9talknk<p>Likely this shows up with any of the standard special characters.&nbsp;</p> <p>A quick look at app.asar shows me this issue possibly comes from the generic use of path, maybe a posix or win32 specific implementation will behave more consistently?</p> <p>Musing on it, this seems to be happening as the apps are not running in the windows shell, rather they are running in the generic, universal shell, while the parent electron application behaves properly in the windows shell.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167666?ContentTypeID=1Thu, 24 Jan 2019 14:01:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f9ca4cdf-2f1f-4bf4-a93e-ebba9f450523awneil<p>As a workaround, can you use the 8.3 &quot;short&quot; names ... ?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167665?ContentTypeID=1Thu, 24 Jan 2019 13:58:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ad7d870e-c1f4-40a5-ae0a-cf03176b7112J&#248;rgen Holmefjord<p>What kind of special characters are you having issues with? I will put a request to the development team to add this option.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167500?ContentTypeID=1Wed, 23 Jan 2019 23:42:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f04f4945-2479-49ea-b785-1c94f8105c72talknk<p>Perhaps you can put in the ticket request for that installer option?</p> <p>I would settle for consistent programming practices myself.</p> <p></p> <p>Unfortunately neither suggestion so far answers my rather simple question.</p> <p></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167499?ContentTypeID=1Wed, 23 Jan 2019 23:29:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7a91e0f1-df10-4060-bbd2-e6f7a9b7c279awneil<p>Or have a separate location for such stuff with a &quot;friendly&quot; path ...</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167497?ContentTypeID=1Wed, 23 Jan 2019 23:20:05 GMT137ad170-7792-4731-bb38-c0d22fbe4515:41628750-d968-4647-bde7-f25e5635cd4atalknk<p>I will suggest that to IT, maybe they can amend their username practice.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/167495?ContentTypeID=1Wed, 23 Jan 2019 22:59:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:342dce9c-02f7-48f3-802b-2e22c37bccefawneil<p>Always best to just avoid the problem in the first place:</p> <p><a href="https://www.avrfreaks.net/comment/2048571#comment-2048571">www.avrfreaks.net/.../2048571</a></p><div style="clear:both;"></div>