[BUG] - Scripts Not finding requested file.

[LYNK-INCUU]

Description

So all the scripts that use the files similar to RunAsTI.cmd don't work and give an error that the file can't be found. But if I copy the file path and edit the script like this.. It does work. Issue being. The files in the Atlas folder are read-only and I'm also not going to do this for every script.

Steps to reproduce

Run script that errors out. Edit. Run script again.

Expected behavior

Should complete the changes without any errors.

Actual behavior

Can't find file or partially completes the script.

Atlas Edition

Atlas for Windows 11 23H2

Desktop information

I5 12th gen 2.60ghz 32gb ram ddr4 Gigabyte SSD and Samsung 980 1tb RTX 4060

Additional content

No response

[n00b69]

One of these scripts is the "Enable sleep.cmd"

[acuteaura]

You can add C:\Windows\AtlasModules to $PATH, which is probably the intended way for this to work.

[LYNK-INCUU]

I'll give it an shot

You can add C:\Windows\AtlasModules to $PATH, which is probably the intended way for this to work.

[LYNK-INCUU]

You can add C:\Windows\AtlasModules to $PATH, which is probably the intended way for this to work.

this doesn't seem to work unless i've done it wrong ex notifications on script judt quits without doing anything

[acuteaura]

You did. It needs to be added to the (existing) one called PATH, on the system one above.

[LYNK-INCUU]

You did. It needs to be added to the (existing) one called PATH, on the system one above.

I put it in path before aswell. but it still doesnt run the scripts

[LYNK-INCUU]

its in here but still doesnt work

[acuteaura]

pretty sure there's a bin folder inside there that contains the actual scripts; set it to that?

[Madgique]

For me it fixed adding C:\Windows\AtlasModules\Scripts to $PATH

[LYNK-INCUU]

I put the Path under system and running toggle defender for example gives strange errors and also doesnt find the file whatever one it asks for.

[n00b69]

Sorry but what? Why is this not planned? You literally cannot use some of the scripts in the AtlasOS folder because of this error.

[he3als]

I'm sorry for closing without a reason - that was an accident.

---

I have implemented a different method for adding to the PATH variable for the next release, which should fix this issue.

The PATH variable was likely not set correctly because it was too long for setx to handle properly. This could be caused by software installed before the Atlas Playbook, meaning a fresh Windows install wasn't used. We strongly recommend following the Atlas documentation to install Atlas.

I have rewritten the entire component removal script for v0.4.0, which likely means those weird errors in the Defender script will disappear.