Guardian 3.3.8 will stop including its own copy of System.Management.dll and use the copy that ships with Revit. Until then:
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:
System.PlatformNotSupportedException. β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.
System.PlatformNotSupportedException. See the tip below to turn on logging. βSystem.Management.dll may be involved. We haven't confirmed cases beyond pyRevit and Elum Tools. 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.
C:\Program Files\Autodesk\Revit 20XX for the Revit version you're fixing, and copy System.Management.dll. !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. System.Management.dll to System.Management.dll.bak. 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.
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.
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.
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:
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.
If Guardian still isn't working after these steps, contact Guardian Support and include:
C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics Contact support: getguardian.tech/contact-support
Guardian 3.3.8 will stop including its own copy of System.Management.dll and use the copy that ships with Revit. Until then:
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:
System.PlatformNotSupportedException. β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.
System.PlatformNotSupportedException. See the tip below to turn on logging. βSystem.Management.dll may be involved. We haven't confirmed cases beyond pyRevit and Elum Tools. 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.
C:\Program Files\Autodesk\Revit 20XX for the Revit version you're fixing, and copy System.Management.dll. !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. System.Management.dll to System.Management.dll.bak. 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.
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.
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.
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:
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.
If Guardian still isn't working after these steps, contact Guardian Support and include:
C:\Users\USERNAME\AppData\LocalLow\Guardian\Diagnostics Contact support: getguardian.tech/contact-support
Contact our support team to receive personalized assistance.