Environment start scripts

Hello,

Thank you for your feedback.

I moved your thread to the PowerShell Universal Support section.

Do you get any specific errors related to this scenario?

Best regards,

Not really.
The errors I get are related to function not being recognised, standard Powershell error message.

@tcheguri84 Could you please share your current environments.ps1 file in your .universal folder? I'd like to try to reproduce your issue in my environment.

Sure...

Publish-RSQLFunctions.ps1

Get-ChildItem -Path 'C:\ProgramData\UniversalAutomation\Repository\.universal\functions' -Exclude $MyInvocation.MyCommand.Name,'Add-RSQLEndpoints.ps1' -Recurse | Where-Object { $_.Extension -eq '.ps1' } | ForEach-Object {
    . ($_.FullName)
}

Environments.ps1

New-PSUEnvironment -Name "Agent" -Path "Universal.Agent" -Variables @('*') 
New-PSUEnvironment -Name "Integrated" -Path "Universal.Server" -Modules @('ActiveDirectory', 'dbatools', 'RaboSQL') -Variables @('*') -PersistentRunspace -StartupScript @('C:\ProgramData\UniversalAutomation\Repository\.universal\functions\Publish-RSQLFunctions.ps1') 
New-PSUEnvironment -Name "Windows PowerShell 5.1" -Path "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe" -Modules @('ActiveDirectory', 'dbatools', 'RaboSQL') -Variables @('*') -PersistentRunspace -StartupScript @('C:\ProgramData\UniversalAutomation\Repository\.universal\functions\Publish-RSQLFunctions.ps1') 
New-PSUEnvironment -Name "Windows PowerShell 7" -Path "C:\Program Files\PowerShell\7\pwsh.exe" -Modules @('ActiveDirectory', 'dbatools', 'RaboSQL') -Variables @('*') -PersistentRunspace -StartupScript @('C:\ProgramData\UniversalAutomation\Repository\.universal\functions\Publish-RSQLFunctions.ps1')

@tcheguri84 Thank you. I'll let you know once we have a fix or a workaround.

Ok. Thank you

@Adam Driscoll did you have the time to test it? Thanks

@tcheguri84 Yes, I did and was able to reproduce this problem. We have a fix already merged and it will be in 2026.2.2. That will be out this week.

@tcheguri84 Yes, I did and was able to reproduce this problem. We have a fix already merged and it will be in 2026.2.2. That will be out this week.

@Adam Driscoll
Great news, thank you again.

@Adam Driscoll after the upgrade to the latest version I am getting this:

HTTP Error 500.32 - Failed to load .NET Core host
Common solutions to this issue:
The app was likely published for a different bitness than w3wp.exe/iisexpress.exe is running as.
Troubleshooting steps:

• Check the system event log for error messages
• Enable logging the application process' stdout messages
• Attach a debugger to the application process and inspect

For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.

I am running PSU on IIS 10. Could you please help?

I found my mistake. Nevermind. Thanks

@Adam Driscoll I have completed the upgrade however the issue remains. This is an App page.

I am also getting this error on 2026.2.2.0

@malcolmradelet @tcheguri84 I'm sorry to hear that. I've reactivated the issue and we will take another look. I'll post an update if we need more information.