Error when opening the debug console
XtermBlazor fit addon assets failed to initialize.
Error: XtermBlazor fit addon assets failed to initialize.
at registerXtermFitAddon (https://psu.ad.spscc.ctc.edu/assets/js/site.js?v=2026.3.3-37052641275:415:11)
at async w.beginInvokeJSFromDotNet (https://psu.ad.spscc.ctc.edu/_framework/blazor.server.js?v=2026.3.3-37052641275:1:4167)
at async Xt._invokeClientMethod (https://psu.ad.spscc.ctc.edu/_framework/blazor.server.js?v=2026.3.3-37052641275:1:67161)
at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, JSCallType callType, Object[] args)
at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args)
at PowerShellUniversal.PsuTerminal.OnAfterRenderAsync(Boolean firstRender) in D:\a\powershell-universal\powershell-universal\src\Universal.Server\Shared\Components\PsuTerminal.razor:line 144
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
Is there a known fix for this?
All Comments (2)
Hello,
Thank you for sending the full error.
This is a known issue in PowerShell Universal 2026.3.3 with the terminal in the admin console.
It happens when a code editor loads on the page before the terminal opens, for example on an app editor page, or on Home or Apps after you leave an editor.
The editor grabs a small add-on that the terminal needs to size itself, so the terminal cannot start and shows the "fit addon assets failed to initialize" error.
The fix is done and will ship in the next release, 2026.3.4 (ticket PSU-1417, for internal reference only).
Until then, you can avoid the error this way:
Press F5 to reload the page, then open the terminal before you open any code editor.
If you need the terminal while you edit, open PowerShell Universal in a second browser tab and open the terminal there first.
Another user reported the same behavior on our forum, and you can follow that thread here: https://forum.devolutions.net/topics/56595/202632--admin-terminal-doesnt-open-on-all-pages
The terminal itself is documented here: https://docs.devolutions.net/powershell-universal/automation/terminals/
If the error still shows on a fresh page load before any editor is open, please tell us which page you were on and which browser you use.
Best regards,
Patrick Ouimet
Hello,
Thank you for your patience while our team looked into the issue you reported.
I'm happy to let you know that the latest version of PowerShell Universal (2026.3.4) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/download-center/#psu
Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.
Thank you for your collaboration.
Best regards,
Maxim Robert