Hello, Dynamo seems to be breaking our AdskIdentityManager for some reason, Its happening to several people after multiple runs of a dynamo script? Also, dynamo is forcing revit into a crawl speed after 4-5 runs, meaning it takes like 60 seconds to just move a simple family from one spot to another spot. Please advise!
What version are you on? Can you post a Revit journal and Dynamo log?
i’ve had the same issue within revit 2025 but haven’t had time to go through things yet.
commenting so i get notified of any updates 
I experience the same. Maybe not 60s, but i Revit does perform a lot slower.
Also after i openend Dynamo, and after a few runs, opening a family goes
from like 5s to 15s (or even more).
EDIT
I only have this since Revit 2025.
Can’t open the zip at the moment - I’ll check on Monday when I get a chance.
@jacob.small ok thanks. let me know
Have you or a colleague started a support ticket via the accounts portal for this yet @mix?
@jacob.small no, but I think I found out what the issue was.
Revit 2025 has AdskIdenttiySDK.dll v1.11.9.11
- DynamoForRevit has AdskIdentitySDK.dll v1.10.4
- When Dynamo starts, it runs a second Autodesk Identity Manager instance which logs you out or slows you down.
- Go to C:\Program Files\Autodesk\Revit 2025\
- Copy AdskIdentitySDK.dll
- Go to C:\Program Files\Autodesk\Revit 2025\AddIns\DynamoForRevit\
- Delete AdskIdentySDK.dll
- Paste in AdskIdentySDK.dll from clipboard.
Yeah that is the temp fix - just needed to know who else I might need to loop in. What you are experiencing is unique among reports the team has had (the common issue seen was an ‘unable to sync’ warning), which may be due to your networking environment, infosec policies, or other stuff.
The Revit devs are aware now though, and hope to have a fix into the next hot fix (not point release). In the meantime you can look at scripting the swap on your systems (will be faster than a patch install too).