mirror of
https://github.com/ElectronNET/Electron.NET.git
synced 2026-02-03 21:25:13 +00:00
Cannot build app in non-admin PowerShell session #958
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mu88 on GitHub (Jun 17, 2024).
Problem description
When trying to build an Electron.NET app in a non-admin PowerShell session, it fails when creating a symlink. When doing the same in an admin shell, everything works nicely.
Versions
23.6.28.0.30020.8.1electronize build /target win)Steps to Reproduce
dotnet tool restoredotnet electronize build /target winLogs
@hswlab commented on GitHub (Jan 9, 2025):
I have currently the same issue. Did you managed to solve this issue meanwhile?
@mu88 commented on GitHub (Jan 10, 2025):
unfortunately not ☹️
@biel-correa commented on GitHub (May 12, 2025):
Same issue here, in my case not even in admin powershell is working
@FlorianRappl commented on GitHub (Oct 31, 2025):
Outdated - use
ElectronNET.CoreandElectronNET.Core.AspNet.See Wiki / What's New.
@mu88 commented on GitHub (Nov 3, 2025):
That's still an issue, see this branch. Here's the output from a non-admin PS session when running
dotnet publish .\FotoManager\FotoManager.csproj -p:PublishProfile=win-x64:@FlorianRappl please reopen the issue - thank you
@FlorianRappl commented on GitHub (Nov 3, 2025):
I was able to build without having a privileged PS session. I am not sure if this is related at all to Electron.NET (besides the issue arises in
electron-builder, which is part of Electron).Here's what Google has to say about it:
I can only suspect that the Node.js installation (i.e., how
electron-builderitself is run) might be responsible for the behavior. This could explain why it works for me in a non-elevated session.@mu88 commented on GitHub (Nov 4, 2025):
So you haven't installed Node.js system-wide?
@FlorianRappl commented on GitHub (Nov 4, 2025):
I have a standard NVM-based installation on Windows. This works in the user account as it should. In general you don't want system-wide installations as its all user account-based anyway.
@mu88 commented on GitHub (Nov 4, 2025):
If you work with tools like Chocolatey, you have to
@FlorianRappl commented on GitHub (Nov 4, 2025):
Sounds rather like an issue with Chocolatey - as mentioned there is not much we can do here as the issue is not in Electron.NET.
@softworkz commented on GitHub (Nov 14, 2025):
First of all, this appears to be about code signing.`
@FlorianRappl - I suppose you don't have signing configured?
All others - do you have signing enabled?
What's weird about this is that the error is about libcrypto.dylib
This is a macOS specific library and there's no use for it on a Window system...