Update riscv-and-xtensa.md

[ryankopf]

The old statement was incorrect, because if the installer is not run as administrator, it fails to permanently set the environment variables without telling you. I have also submitted a PR to display a clearer error message in espup.

[ryankopf]

After a bit more investigation, the change is still warranted, but the reason may actually be related to Windows's undocumented caching of registry values. However the problem is easily reproduceable by deleting your environment variables with Regedit, restarting your PC, and running the espup install command.

[SergioGasquez]

After a bit more investigation, the change is still warranted, but the reason may actually be related to Windows's undocumented caching of registry values. However the problem is easily reproduceable by deleting your environment variables with Regedit, restarting your PC, and running the espup install command.

But did you have to use admin privileges when running the espup command to get the environment automatically picked up?

[ryankopf]

I am going to have to test again later, but no it seemed like being administrator wasn't a majaor factor, but rather there is some kind of registry caching that doesn't complete unless you completely restart your PC.

[SergioGasquez]

Hi! Did you had a chance to look into this?

[ryankopf]

I was unable to determine the final cause, but it seems like there is some kind of undocumented caching of these registry values on Windows (tried on both 10 & 11). So a note about encouraging users to restart, on Windows, if it doesn't work immediately would still be a good idea.