PowerShell Universal - 3.8.12

PowerShell Universal - 3.8.12

Release Notes


  • Fixed an issue where endpoints that use the -Path parameter would not update context after git sync (#2335)


  • Fixed an issue where radio groups could not be disabled dynamically (#2341)
  • Fixed an issue where editing a single dashboard page would cause all pages to refresh (#2342)
  • Fixed issue with New-UDAppBar -Footer (#2176)
  • Fixed an issue where Transfer List allowed disabled Transfer List Item to be transferred “to the right” (#2311)
  • Fixed an issue where New-UDAlert with quotes wouldn’t render properly (#2240)
  • Fixed an issue where New-UDUpload would have invalid colors by default (#2326)
  • Fixed an issue where New-UDDatePicker\New-UDTimePicker -TimeZone didn’t work with daylight savings
  • Fixed an issue where New-UDMenu had an extra div that didn’t align for horizontal layout
  • Fixed an issue where New-UDMenu -Icon didn’t have any padding around the icon


  • Fixed an issue where -ExperimentalFeatures would get removed when changing settings in the UI (#2255)
  • Fixed an issue where the file system watcher and\or git sync could fail to pick up changes (#2335/#1984)
  • Fixed an issue where discard changes would show an error in the admin console (#2316)
  • Fixed an issue where PSCredential secrets would not work across nodes in the database vault (#2339)


1 Like

Is anybody else having problems Styling or modules in this version?

A ton of custom written modules fail to work for me. As soon as I revert to 3.8.11 it all starts working again.

I am using the containerized version docker.io/ironmansoftware/universal:3.8.12-ubuntu-20.04 of this release. My container fell over before I could get any meaningful debug logs.

I haven’t tried yet but thanks for heads up.

Looks like I have a similar issue. Troubleshooting for a few hours already.
As I can see, PSU does not add the $Respository/Modules directory to $ENV:PSModulePath. Also, it somehow does not read Repo modules even if the Repository path is added persistently.

That would make sense.

The CSS which was out of wack was all specified in custom modules.

I am on leave at the for the next week, so I am unable to test any more.

I can kind of reproduce this so I’m curious if you have some more info on how your instances are configured.

This is how I can do it:

  1. Create a new module called MyMod
  2. Define a function to display an alert.
function New-MyAlert {
    New-UDAlert -Text "Hello"
  1. Create a dashboard that uses this function.
New-UDDashboard -Title 'PowerShell Universal' -Pages @(
    New-UDPage -Name 'Home' -Content {
  1. View the dashboard and see that it cannot find the function.
  2. Attempt to restart the dashboard and it still cannot find the function.
  3. Import the module directly: Ipmo MyMod
  4. Alert is displayed
  5. Remove the import and restart the dashboard, alert is displayed.
  6. Change from the Integrated environment to 7.3.4 and alert is displayed

At least in my environment, it seems like module auto-loading isn’t working for some reason in the integrated environment but loading the module manually works. Running the dashboard in 7.3.4 finds the module. I’m running the 3.8.12 docker container.

The PSModulePath always contains the Repository\Module path in my tests.

Apologies for the delay in replying. I have been on Annual Leave.

The above matches what I saw.

Was any bug or change identified on this problem? I can see GitHub issue #2376 which is closed.

I am happy to leave this be if it is fixed in newer versions, if it is just a cosmetic bug.