he3als

Also, 23H1 doesn't exist, and 23H2 doesn't exist for Windows 10. I'm confused on what you did.

Try enabling troubleshooting in the Atlas folder

Are you on v0.3.1/v0.3.2?

Hi - does this still happen in v0.4.0?

Was this after following the documentation to reinstall? Upgrades from previous versions to v0.4.0 aren't supported.

Can you please send the `TIOutput.txt` in the Atlas folder inside of `%ProgramData%\AME\Logs`? The PATH variable is somehow messed up.

Atlas doesn't replace the PATH variable, it just appends to it. https://github.com/Atlas-OS/Atlas/blob/main/src/playbook/Configuration/atlas/start.yml#L9 I'm not too sure what could be wrong or how to reproduce your issue.

Scripts in the Atlas folder should say that they're finished, e.g.:  If they don't, the script isn't launching, likely due to RunAsTI not functioning. Can you open a Command...

Although a proper GUI is a better user experience, it's not a priority as it only changes a little functionally, that's why we haven't got one currently. However, as @PencilNavigator...

I agree. Unless there's a proven problem with SuperFetch on SSDs, I don't think it should be disabled. Microsoft also doesn't recommend the service to be disabled for desktop users.