[pulsar-next] context-menu of explorer doesn't work

[asiloisad]

Thanks in advance for your bug report!

• Have you reproduced issue in safe mode?
• Have you used the debugging guide to try to resolve the issue?
• Have you checked our FAQs to make sure your question isn't answered there?
• Have you checked to make sure your issue does not already exist?
• Have you checked you are on the latest release of Pulsar?

What happened?

A context-menu PulsarNext Electron doesn't work. An error pop up.

Pulsar version

1.124.2025011501-next

Which OS does this happen on?

🪟 Windows

OS details

10

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

1. Right click in folder of Windows Explorer
2. Click PulsarNext Electron

Additional Information:

No response

[savetheclocktower]

I didn't even know this was a thing.

[confused-Techie]

Thanks a ton for reporting this issue!
This most certainly has to do with the fact the binary name has been changed to PulsarNext, and will likely be resolved by the time we properly ship the application.

Just to double check though, did you right click the folder itself, or the background page within a folder?

[asiloisad]

If I turn on all options in Settings/System, then it revert to off after program reloaded/restarted.

And there are two different context-menu items created by PulsarNext. Both don't work.

[asiloisad]

I have tested it

• in context-menu of directory background,
• in context-menu of directory,
• in context-menu of file.

[confused-Techie]

Interesting, thanks for the update.

Like I said, pretty sure this will be resolved once we revert the binary name back to just Pulsar, once PulsarNext is properly shipped.

But in the meantime, for anybody working on PulsarNext, this behavior is controlled in ./src/main-process/win-shell.js. The last few functions control what's actually added to the registry. A quick look doesn't have anything that pops out about why this would stop working, but based on the path shown in the error message of the issue, it seems maybe we aren't escaping a space or something if the installation path is truly Pulsar Next like I'm assuming.