[Tool, Solution, or Feature Name] - A clear and concise description of what the bug is

[FrogTales]

Gateway Version: 2606 2.7.4.18
Extension Version various as described/shown but the first occurring is version 6.0.3 of Server Manager and Computer Management

To Reproduce
Steps to reproduce the behavior:

1. Have the managed device in an Enforced mode WDAC/ACfB policy with the "Disable Script Enforcement" option toggled OFF.
2. Go to all connections/server manager.
3. Click on the device being managed that has WDAC enforced.
4. The first error message pictured below will come up (referring to Microsoft.SME.ServerManager).
5. This can be worked around by uninstalling the specified version of the module in question and installing an older version instead (4.26.0 in the case of Microsoft.SME.ServerManager), and the device overview page can be viewed, at which point the second error notification shown (Microsoft.SME.Shell) appears.
6. Click on any of a number of tools with an associated PowerShell Module (e.g. Events) and a similar error to the others described/shown appears, referencing a module respective to the tool selected (e.g. Microsoft.SME.EventViewer).
7. Some of these (EventViewer) can be worked around as described in step 5, but others (e.g. Microsoft.SME.Shell) do not appear to have an extension in WAC I can see by the same name to try an older version of.

Expected behavior
For connections to devices and browsing between tools to occur successfully and without error notification. Company policy also requires us to have WDAC enforced and to have the script enforcement option turned on.

Screenshots & Additional context
Using in conjunction with Windows Defender Application Control/App Control for Business, when the device being managed is in Enforced mode and has the "Disable Script Enforcement" option toggled OFF, attempting to connect to the device results in an error as described.

It appears that the PowerShell modules being referenced in the error notifications all have the version number inside their .psd1 file set to '0.0.0' and having script enforcement on results in them being blocked from running due to their internal version number not matching that of the folder it's located in, etc. Those that the described work around works for have a matching version number inside the .psd1.

1:

2: