@SJamal85Aside from folder layout / pathing issues, if you try to run a script hidden in the background (unsigned,) without any user interaction, it will fail unless the execution policy is set to "Bypass." I don't think I've ever run an unsigned script without it being set to "Bypass."
"Set-ExecutionPolicy - Parameters" -> https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy...
"Bypass. Nothing is blocked and there are no warnings or prompts.
Unrestricted. ...If you run an unsigned script that was downloaded from the internet, you're prompted for permission before it runs."
How to: Sign application and deployment manifests | Methods of signing scripts
NOTE: It also depends on what revision of Powershell the host machine has, ( must have WMF 5.1 ) how up-to-date the cmdlets are, whether it has the latest certificates / protocols, etc (even though that's almost outside of the scope of what you're trying to accomplish. I'm more describing roadblocks which would hinder the functionality / usefulness of your script over the long-term. )
# ExecutionPolicy -List
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser -Force
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope LocalMachine -Force;
Set-PSReadLineOption -HistorySaveStyle SaveNothing -MaximumHistoryCount 1;
Write-Output "Remove-Module PSReadline" | Out-File -FilePath $PROFILE -NoNewline -Width 24;
# Set-Content -Value "Remove-Module PSReadline" -NoNewline -Path $PROFILE;
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12;
Install-PackageProvider -Name NuGet -Scope AllUsers -Force;
Install-PackageProvider -Name PowerShellGet -Scope AllUsers -Force;
Get-Module -ListAvailable | Update-Module -Scope AllUsers -Force;
Update-Help -Verbose -Force -ErrorAction SilentlyContinue;
Obviously you could also run a batch file instead, that utilizes powershell without a profile. In theory, you could use this if you wanted to to launch another script to get around access restrictions, to chain scripts / batch files in succession, or it's an environment with a mix of batch files, powershell scripts, etc, where you might only want a few cmdlets, and the rest of the focus is on other scripting languages.
powershell -noprofile -Command "& {New-Item -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\temporaryentry'}"
powershell -noprofile -Command "& {Remove-Item -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\temporaryentry'}"
The onus is on the person installing the MSIX package, to verify whether or not it's safe to use. It's not like this is enabling malicious software, and there are plenty of ways to add safeguards. You could find a way to sign all of your scripts and code before distributing them, with public / private key certificates. It seems more like this is just for personal use, so it would be hard to justify that type of workload. You could even use OpenSSL 3.x to generate it, and convert it to a .PFX file afterwards. To distribute it though, you would probably need to leverage either a post-paid or free certificate authority, for code signing or just generating RSA / ECC certs. It really depends on what it is. I mean I compiled OpenSSL on Windows, and then used it to generate a whole bunch of generic certs by hand ( utilizing cryptographically secure seed values on an air-gapped device, with virtual memory disabled, etc. I erased my seed values after with Sdelete. )
