SE protocol not working on standard user account after relaunching.

[iron inlet]

I could not register the protocol when launching SE normally (no write access error). Launching it as Admin worked but when i close it and relaunch it normally it doesn't work anymore. It only seems to work when I launch Steam and SE as Admin which is very annoying. Is there a way around this?

[tranquil glade]

Thanks for posting in the support forums, uniter_343!

Guidelines and First Steps:

1. Please include your se.log file located at <Steamapps>/common/SpaceEngine/system/se.log.
2. Is your installation modded? Not all mod authors keep up with updates, and old or buggy mods can cause many issues, even those that may not seem related.
3. Are you on the latest version? Older versions of SpaceEngine are not supported. Check your Betas tab in Steam to make sure you are on the current version.
4. Have you updated your graphics drivers recently? We only test against up-to-date drivers. Old drivers can cause a plethora of issues.
5. Does your PC meet the system requirements? (Windows 10, Dual core Intel i3 3rd gen / AMD FX or better, 6 GB RAM, GeForce 1050 Ti or Radeon RX 460 (4 GB)).
   Is This a request for help modding? the correct place for mod help is https://discord.com/channels/148933808811409408/1164988630671044638

[zealous tapir]

Considering that this is probably due to recent changes to Windows OS on permissions, it will have to be investigated.

[zealous tapir]

I can confirm that the Steam client had to run with administrative permissions for SE being able to register the se:\ protocol in Windows Registry, since the first Steam version. But back then, once the protocol was recorded in the registry, there was no need to launch again those programs as administrators, at least for the new protocol to work, so as annoying as it could be, it was a one-time-only issue.
I'll check if Windows updates changed this policy, in which case this kind of things will probably need different code to work, or some other manual tweak from users.

[hot idol]

Hello ! Since I saw that there was an issue about the se URL protocol already written down here, I wanted to point out that I managed to run it as administrator to install the protocol in the registry, but Windows says there's no associated application despite the protocol installation, which seems correct when I checked the registry (the path to the Space Engine exe is technically correct). I tried to reboot my computer, to find a way to fix that manually or to reinstall it but no changes since

Here is the translation of the error :

This file does not contain an associated application to perform this action. Install an application or, if you've already done so, create an association on the Default application settings page.

I was wondering whether I was the only one in this situation or not.

[pallid gyro]

I confirm I have the same error like Loic. I "succesful" registry the se protocol from the software, but same problem.

If someone really successful write the protocol se, how you do that?

[hot idol]

I found a way to fix it for now until the protocol registration is fixed on Space Engine
I did a PowerShell script to add it to the HKEY_CURRENT_USER instead (avoiding admin permissions. I had to ask for the path of the SpaceEngine.exe in my case), which is working now. Here is the exe file, but I can also send the source code if it could be used to fix the bug

[hot idol]

The only bug known apart of this is that when the game is closed, even with the url as an argument, it doesn't directly open to the location, but it does when the game is already open

[zealous tapir]

Yes, a zero character looks like is added at the end of the string when the location is passed to the program by the Steam client. Something is passing spurious data to SE.