Guardian Roles, Licensing or Activity Tracking Not Working? Resolving DLL Conflicts with Elum Tools or pyRevit

service-bulletins
Knowledge Base
Guardian Roles, Licensing or Activity Tracking Not Working? Resolving DLL Conflicts with Elum Tools or pyRevit
Status
Active. A fix is planned for Guardian 3.3.8 (release date not yet set).
Guardian Version
3.3.7 and earlier
Revit Version
2025 and later
Last Updated
Oct 9, 2026

Resolution

Guardian 3.3.8 will stop including its own copy of System.Management.dll and use the copy that ships with Revit. Until then:

  • No symptoms? No action is needed. Before updating pyRevit or Elum Tools, check Known Cases below. ‍
  • pyRevit 7.0.0 or later: Reinstall v6.5.3 from the pyRevit GitHub releases page and hold off on upgrading until Guardian 3.3.8 is installed. This has resolved most reported cases, but not all. ‍
  • Elum Tools 2027.1.0.7, 2026.6.0.7 or 2025.9.0.7: Elum's download page only offers the latest build for each Revit year, so going back may not be possible. Ask your IT team about the workaround below. ‍
  • Need Guardian working right away? (Not recommended long-term) Temporarily disabling pyRevit stops the conflict and confirms it's the cause. The same works for Elum Tools. ‍
  • Managing multiple machines? See IT / Enterprise Deployments below.

Important Notes

  • ‍Missing activity can't be recovered. User activity isn't recorded while the conflict is present, so we recommend acting promptly.
  • ‍pyRevit v6.5.3 doesn't resolve every case. If symptoms continue on v6.5.3, contact Guardian Support.
  • ‍Only the builds listed in Known Cases have been verified. We don't have information on builds released between the compatible and current versions. If you're on one, treat it as possibly affected.
  • The workaround isn't always reliable. It can restore Guardian, but it doesn't work in every case, especially with pyRevit installations that use custom configurations.

Original Issue

Revit 2025 and later load all add-ins into a shared environment, where only one copy of a given system file can be in use at a time. Guardian and some builds of pyRevit and Elum Tools each include their own copy of System.Management.dll, and whichever copy loads first is used by all of them.

Some add-in copies are a limited version that can't make Windows system calls. Depending on which copy loads first:

  • Guardian is affected when it ends up using a limited copy. It can't complete the checks it relies on for role recognition, licensing and activity tracking, and logs System.PlatformNotSupportedException. ‍
  • pyRevit or Elum Tools may be affected when they end up using Guardian's copy instead of their own.

Load order can change between sessions, so the issue can seem to come and go, and each add-in works normally when the others are disabled. Β 

This was largely resolved with earlier releases of both add-ins but has returned with pyRevit 7 and the latest Elum Tools builds. If you resolved it before, you may see it again after updating.

Symptoms

  • Role misidentification: Administrators don't see their role-appropriate tools in the Guardian ribbon. ‍
  • Licensing unresponsive: The Licensing button does nothing. ‍
  • Activity not recorded: User activity is missing from Guardian reporting for the affected period. ‍
  • Works only in isolation: Guardian works normally when other add-ins are disabled. ‍
  • Log error: The Guardian diagnostic log contains System.PlatformNotSupportedException. See the tip below to turn on logging. ‍
  • Returned after an update: Symptoms started, or came back, after updating pyRevit or Elum Tools.

Known Cases

  • pyRevit: Versions before v6.5.3, v7.0.0 and later, and some v6.5.3 installations are affected. Most v6.5.3 installations are not. ‍
  • Elum Tools:
    • Revit 2027: 2027.1.0.7 and builds before 2027.1.0.3 are affected. 2027.1.0.3 is not.
    • Revit 2026: 2026.6.0.7 and builds before 2026.6.0.3 are affected. 2026.6.0.3 is not.
    • Revit 2025: 2025.9.0.7 and builds before 2025.9.0.3 are affected. 2025.9.0.3 is not. ‍
  • ‍Other add-ins: Any add-in that includes its own copy of System.Management.dll may be involved. We haven't confirmed cases beyond pyRevit and Elum Tools.

Workaround for Earlier Versions

Note:
Use this only if going back to a compatible add-in version isn't possible.
This workaround is intended for IT administrators.
‍
It doesn't always work.
This replaces the add-in's copy on disk, but Guardian 3.3.7 and earlier can still share their own copy in memory, so results depend on load order. It's especially unreliable with pyRevit installations that use custom configurations.
‍
Validation status:
We've confirmed it can restore Guardian. We haven't fully tested its effect on pyRevit or Elum Tools, so test on one machine, including the add-in's own features, before deploying widely.
‍
You're modifying another vendor's files.
This requires administrator rights, may be undone by add-in updates and may affect support from that vendor. Always back up the original file.

Step 1 β€” Locate the Revit source file

  1. Close Revit.
  2. Go to C:\Program Files\Autodesk\Revit 20XX for the Revit version you're fixing, and copy System.Management.dll.

Step 2 β€” Replace the file: Elum Tools

  1. Open the !ElumTools.bundle folder: C:\ProgramData\Autodesk\Revit\Addins\20XX\!ElumTools.bundle for Revit 2025 and 2026, or C:\Program Files\Autodesk\Revit\Addins\2027\!ElumTools.bundle for Revit 2027.
  2. Rename the existing System.Management.dll to System.Management.dll.bak.
  3. Paste the copy from Step 1. Use the Revit folder for the same year as the add-in folder.
  4. Repeat for each Revit version that has Elum Tools installed.

Step 2 β€” Replace the file: pyRevit

pyRevit can keep a copy of System.Management.dll in several engine folders. Use the PowerShell command in the tip below to find every copy, then rename each one to System.Management.dll.bak and paste the copy from Step 1 in its place. Common locations:

  • C:\Program Files\pyRevit-Master\
  • %AppData%\pyRevit-Master\

Go back to pyRevit v6.5.3 instead if pyRevit uses custom engines, clones or extension locations, or if one pyRevit installation serves several Revit versions. We haven't validated the replacement in those setups. Note that some v6.5.3 installations are still affected. If symptoms continue on v6.5.3, the replacement may not help either, so contact Guardian Support.

Step 3 β€” Restart Revit

  1. Restart Revit and open a model.
  2. Check that role-appropriate tools appear in the Guardian ribbon, Licensing responds and activity is being recorded.
  3. Check that the add-in you modified still works as expected.
  4. Restart Revit once more and check again, since results can depend on load order.

To undo: close Revit, delete the pasted file and rename System.Management.dll.bak back to System.Management.dll. Reinstalling or updating the add-in also restores its original file.

Tip: Diagnosing Other Add-ins

If symptoms continue, or you don't use pyRevit or Elum Tools, use these steps to confirm the conflict and find the add-in involved.

1. Check the Guardian log. The most reliable sign of this conflict is System.PlatformNotSupportedException in the Guardian diagnostic log.

  1. On the affected machine, open Guardian Settings > About and press Ctrl+Alt+Shift+D to turn on diagnostic logging. Logging is off by default.
  2. Reproduce the issue, for example by clicking Licensing.
  3. Open the log files in C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics, replacing USERNAME with the Windows user name, and search for PlatformNotSupportedException.

2. Find add-ins that include the DLL. Revit loads add-ins from these locations:

Location Used by
C:\ProgramData\Autodesk\Revit\Addins\20XX All users, Revit 2025 and 2026
C:\Program Files\Autodesk\Revit\Addins\2027 All users, Revit 2027
%AppData%\Autodesk\Revit\Addins\20XX Current user only, any version

This PowerShell command lists Revit's own copies of System.Management.dll first, then every copy in the add-in folders and the default pyRevit folders, with size and version:

$revit = Get-Item "C:\Program Files\Autodesk\Revit 20*\System.Management.dll" ` 

  -ErrorAction SilentlyContinue 

$paths = "C:\ProgramData\Autodesk\Revit\Addins", 

         "C:\Program Files\Autodesk\Revit\Addins", 

         "$env:APPDATA\Autodesk\Revit\Addins", 

         "C:\Program Files\pyRevit-Master", 

         "$env:APPDATA\pyRevit-Master" 

$addins = Get-ChildItem $paths -Recurse -Filter System.Management.dll ` 

  -ErrorAction SilentlyContinue 

@($revit) + @($addins) | Select-Object FullName, 

  @{n="KB";e={[math]::Round($_.Length/1KB)}}, 

  @{n="Version";e={$_.VersionInfo.FileVersion}} 

Compare sizes, not versions. A limited copy can report the same version number as Revit's own copy but be much smaller. For example, Revit 2026's copy is about 305 KB, while the limited copy included with some add-ins is about 70 KB.

A smaller copy shows that an add-in could be involved, but it doesn't prove a conflict. Confirm with the Guardian log before acting. Add-ins other than pyRevit and Elum Tools, such as DiRoots One and DiRoots ProSheets, also include a smaller copy. We haven't had reports involving them, but they may be worth checking.

Some add-ins install files elsewhere. Open the add-in's .addin file in a text editor, find the <Assembly> tag, and check the folder it points to.

3. Isolate the add-in. Close Revit and rename one suspect .addin file to .addin.off so Revit skips it. Re-enable add-ins one at a time until the symptoms return.

IT / Enterprise Deployments
Pin versions:
Until Guardian 3.3.8 is deployed, keep pyRevit at v6.5.3 (which resolves most, but not all, cases) and Elum Tools at the compatible versions in Known Cases, and pause automatic updates for both.

Check machines:
The PowerShell command in the tip above lists copies for a person to review. It isn't a ready-made detection script, but your team can adapt it for SCCM, Intune or your RMM tool, for example by flagging any add-in copy much smaller than Revit's. Treat a flagged machine as a reason to check the Guardian log, not as confirmation of the conflict.

Re-check after add-in updates:
Updates or repairs can restore the add-in's original DLL.

After Guardian 3.3.8:
Undo any replacements and, after confirming on a test machine, lift the version pins.

Further Assistance

If Guardian still isn't working after these steps, contact Guardian Support and include:

  • Your Guardian, Revit and add-in versions
  • Guardian diagnostic logs from C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics
  • The output of the PowerShell command in the tip above, if you ran it

Contact support: getguardian.tech/contact-support

Knowledge Base
Guardian Roles, Licensing or Activity Tracking Not Working? Resolving DLL Conflicts with Elum Tools or pyRevit
Status
Active. A fix is planned for Guardian 3.3.8 (release date not yet set).
Guardian Version
3.3.7 and earlier
Revit Version
2025 and later
Last Updated
Oct 9, 2026

Resolution

Guardian 3.3.8 will stop including its own copy of System.Management.dll and use the copy that ships with Revit. Until then:

  • No symptoms? No action is needed. Before updating pyRevit or Elum Tools, check Known Cases below. ‍
  • pyRevit 7.0.0 or later: Reinstall v6.5.3 from the pyRevit GitHub releases page and hold off on upgrading until Guardian 3.3.8 is installed. This has resolved most reported cases, but not all. ‍
  • Elum Tools 2027.1.0.7, 2026.6.0.7 or 2025.9.0.7: Elum's download page only offers the latest build for each Revit year, so going back may not be possible. Ask your IT team about the workaround below. ‍
  • Need Guardian working right away? (Not recommended long-term) Temporarily disabling pyRevit stops the conflict and confirms it's the cause. The same works for Elum Tools. ‍
  • Managing multiple machines? See IT / Enterprise Deployments below.

Important Notes

  • ‍Missing activity can't be recovered. User activity isn't recorded while the conflict is present, so we recommend acting promptly.
  • ‍pyRevit v6.5.3 doesn't resolve every case. If symptoms continue on v6.5.3, contact Guardian Support.
  • ‍Only the builds listed in Known Cases have been verified. We don't have information on builds released between the compatible and current versions. If you're on one, treat it as possibly affected.
  • The workaround isn't always reliable. It can restore Guardian, but it doesn't work in every case, especially with pyRevit installations that use custom configurations.

Original Issue

Revit 2025 and later load all add-ins into a shared environment, where only one copy of a given system file can be in use at a time. Guardian and some builds of pyRevit and Elum Tools each include their own copy of System.Management.dll, and whichever copy loads first is used by all of them.

Some add-in copies are a limited version that can't make Windows system calls. Depending on which copy loads first:

  • Guardian is affected when it ends up using a limited copy. It can't complete the checks it relies on for role recognition, licensing and activity tracking, and logs System.PlatformNotSupportedException. ‍
  • pyRevit or Elum Tools may be affected when they end up using Guardian's copy instead of their own.

Load order can change between sessions, so the issue can seem to come and go, and each add-in works normally when the others are disabled. Β 

This was largely resolved with earlier releases of both add-ins but has returned with pyRevit 7 and the latest Elum Tools builds. If you resolved it before, you may see it again after updating.

Symptoms

  • Role misidentification: Administrators don't see their role-appropriate tools in the Guardian ribbon. ‍
  • Licensing unresponsive: The Licensing button does nothing. ‍
  • Activity not recorded: User activity is missing from Guardian reporting for the affected period. ‍
  • Works only in isolation: Guardian works normally when other add-ins are disabled. ‍
  • Log error: The Guardian diagnostic log contains System.PlatformNotSupportedException. See the tip below to turn on logging. ‍
  • Returned after an update: Symptoms started, or came back, after updating pyRevit or Elum Tools.

Known Cases

  • pyRevit: Versions before v6.5.3, v7.0.0 and later, and some v6.5.3 installations are affected. Most v6.5.3 installations are not. ‍
  • Elum Tools:
    • Revit 2027: 2027.1.0.7 and builds before 2027.1.0.3 are affected. 2027.1.0.3 is not.
    • Revit 2026: 2026.6.0.7 and builds before 2026.6.0.3 are affected. 2026.6.0.3 is not.
    • Revit 2025: 2025.9.0.7 and builds before 2025.9.0.3 are affected. 2025.9.0.3 is not. ‍
  • ‍Other add-ins: Any add-in that includes its own copy of System.Management.dll may be involved. We haven't confirmed cases beyond pyRevit and Elum Tools.

Workaround for Earlier Versions

Note:
Use this only if going back to a compatible add-in version isn't possible.
This workaround is intended for IT administrators.
‍
It doesn't always work.
This replaces the add-in's copy on disk, but Guardian 3.3.7 and earlier can still share their own copy in memory, so results depend on load order. It's especially unreliable with pyRevit installations that use custom configurations.
‍
Validation status:
We've confirmed it can restore Guardian. We haven't fully tested its effect on pyRevit or Elum Tools, so test on one machine, including the add-in's own features, before deploying widely.
‍
You're modifying another vendor's files.
This requires administrator rights, may be undone by add-in updates and may affect support from that vendor. Always back up the original file.

Step 1 β€” Locate the Revit source file

  1. Close Revit.
  2. Go to C:\Program Files\Autodesk\Revit 20XX for the Revit version you're fixing, and copy System.Management.dll.

Step 2 β€” Replace the file: Elum Tools

  1. Open the !ElumTools.bundle folder: C:\ProgramData\Autodesk\Revit\Addins\20XX\!ElumTools.bundle for Revit 2025 and 2026, or C:\Program Files\Autodesk\Revit\Addins\2027\!ElumTools.bundle for Revit 2027.
  2. Rename the existing System.Management.dll to System.Management.dll.bak.
  3. Paste the copy from Step 1. Use the Revit folder for the same year as the add-in folder.
  4. Repeat for each Revit version that has Elum Tools installed.

Step 2 β€” Replace the file: pyRevit

pyRevit can keep a copy of System.Management.dll in several engine folders. Use the PowerShell command in the tip below to find every copy, then rename each one to System.Management.dll.bak and paste the copy from Step 1 in its place. Common locations:

  • C:\Program Files\pyRevit-Master\
  • %AppData%\pyRevit-Master\

Go back to pyRevit v6.5.3 instead if pyRevit uses custom engines, clones or extension locations, or if one pyRevit installation serves several Revit versions. We haven't validated the replacement in those setups. Note that some v6.5.3 installations are still affected. If symptoms continue on v6.5.3, the replacement may not help either, so contact Guardian Support.

Step 3 β€” Restart Revit

  1. Restart Revit and open a model.
  2. Check that role-appropriate tools appear in the Guardian ribbon, Licensing responds and activity is being recorded.
  3. Check that the add-in you modified still works as expected.
  4. Restart Revit once more and check again, since results can depend on load order.

To undo: close Revit, delete the pasted file and rename System.Management.dll.bak back to System.Management.dll. Reinstalling or updating the add-in also restores its original file.

Tip: Diagnosing Other Add-ins

If symptoms continue, or you don't use pyRevit or Elum Tools, use these steps to confirm the conflict and find the add-in involved.

1. Check the Guardian log. The most reliable sign of this conflict is System.PlatformNotSupportedException in the Guardian diagnostic log.

  1. On the affected machine, open Guardian Settings > About and press Ctrl+Alt+Shift+D to turn on diagnostic logging. Logging is off by default.
  2. Reproduce the issue, for example by clicking Licensing.
  3. Open the log files in C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics, replacing USERNAME with the Windows user name, and search for PlatformNotSupportedException.

2. Find add-ins that include the DLL. Revit loads add-ins from these locations:

Location Used by
C:\ProgramData\Autodesk\Revit\Addins\20XX All users, Revit 2025 and 2026
C:\Program Files\Autodesk\Revit\Addins\2027 All users, Revit 2027
%AppData%\Autodesk\Revit\Addins\20XX Current user only, any version

This PowerShell command lists Revit's own copies of System.Management.dll first, then every copy in the add-in folders and the default pyRevit folders, with size and version:

$revit = Get-Item "C:\Program Files\Autodesk\Revit 20*\System.Management.dll" ` 

  -ErrorAction SilentlyContinue 

$paths = "C:\ProgramData\Autodesk\Revit\Addins", 

         "C:\Program Files\Autodesk\Revit\Addins", 

         "$env:APPDATA\Autodesk\Revit\Addins", 

         "C:\Program Files\pyRevit-Master", 

         "$env:APPDATA\pyRevit-Master" 

$addins = Get-ChildItem $paths -Recurse -Filter System.Management.dll ` 

  -ErrorAction SilentlyContinue 

@($revit) + @($addins) | Select-Object FullName, 

  @{n="KB";e={[math]::Round($_.Length/1KB)}}, 

  @{n="Version";e={$_.VersionInfo.FileVersion}} 

Compare sizes, not versions. A limited copy can report the same version number as Revit's own copy but be much smaller. For example, Revit 2026's copy is about 305 KB, while the limited copy included with some add-ins is about 70 KB.

A smaller copy shows that an add-in could be involved, but it doesn't prove a conflict. Confirm with the Guardian log before acting. Add-ins other than pyRevit and Elum Tools, such as DiRoots One and DiRoots ProSheets, also include a smaller copy. We haven't had reports involving them, but they may be worth checking.

Some add-ins install files elsewhere. Open the add-in's .addin file in a text editor, find the <Assembly> tag, and check the folder it points to.

3. Isolate the add-in. Close Revit and rename one suspect .addin file to .addin.off so Revit skips it. Re-enable add-ins one at a time until the symptoms return.

IT / Enterprise Deployments
Pin versions:
Until Guardian 3.3.8 is deployed, keep pyRevit at v6.5.3 (which resolves most, but not all, cases) and Elum Tools at the compatible versions in Known Cases, and pause automatic updates for both.

Check machines:
The PowerShell command in the tip above lists copies for a person to review. It isn't a ready-made detection script, but your team can adapt it for SCCM, Intune or your RMM tool, for example by flagging any add-in copy much smaller than Revit's. Treat a flagged machine as a reason to check the Guardian log, not as confirmation of the conflict.

Re-check after add-in updates:
Updates or repairs can restore the add-in's original DLL.

After Guardian 3.3.8:
Undo any replacements and, after confirming on a test machine, lift the version pins.

Further Assistance

If Guardian still isn't working after these steps, contact Guardian Support and include:

  • Your Guardian, Revit and add-in versions
  • Guardian diagnostic logs from C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics
  • The output of the PowerShell command in the tip above, if you ran it

Contact support: getguardian.tech/contact-support

Need More Help?

Contact our support team to receive personalized assistance.

Guardian graphic