Published Folder / Branding broke after 5.3.3 upgrade?

Product: PowerShell Universal
Version: 5.3.3

MSI install, SQL backend (separate server), OIDC login.

Since upgrading to 5.3.3, none of the images in a published folder are available. All receiving http 400 error codes.

Turned up logging and seeing the following in the system log:

2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware] The request path /images/Black_Small.png does not match an existing file
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware] The request path does not match the path filter
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware] The request path does not match the path filter
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.Routing.Matching.DfaMatcher] 1 candidate(s) found for the request path ‘/images/Black_Small.png’
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.Routing.Matching.DfaMatcher] Endpoint ‘gRPC - Unimplemented service’ with route pattern ‘{unimplementedService}/{unimplementedMethod:grpcunimplemented}’ was rejected by constraint ‘unimplementedMethod’:‘Grpc.AspNetCore.Server.Model.Internal.GrpcUnimplementedConstraint’ with value ‘Black_Small.png’ for the request path ‘/images/Black_Small.png’
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.Routing.Matching.DfaMatcher] Endpoint ‘gRPC - Unimplemented service’ with route pattern ‘{unimplementedService}/{unimplementedMethod:grpcunimplemented}’ is not valid for the request path ‘/images/Black_Small.png’
2025-02-27 16:55:44.010 -05:00 [DBG][Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware] Request did not match any endpoints
2025-02-27 16:55:44.013 -05:00 [INF][Microsoft.AspNetCore.Hosting.Diagnostics] Request finished HTTP/2 GET https://XXXX.com/images/Black_Small.png - 400 0 null 3.7516ms

I’ve attempted to delete the published folder and recreate it with the same results. Items such as “https://XXXX.com/assets/logo.png” are available without issue.

If you need more information or would like me to open an issue, please let me know.

Looks like the local path to the folder was potentially modified. Once putting back to the exact C:\ path, the images are now appearing.