Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 27
Like Tree4Likes

Thread: Revit 2017 Signed Addins NOT Always Loading

  1. #11
    Member aperte's Avatar
    Join Date
    August 9, 2011
    Posts
    60
    Current Local Time
    12:01 PM
    Thanks for hashing all this out, guys. I'll keep an eye on this thread and see what y'all finalize on (Plan C) ;-)
    Happy new year!

  2. #12
    Member troygates's Avatar
    Join Date
    December 17, 2010
    Location
    Southern California
    Posts
    143
    Current Local Time
    11:01 AM
    Here is an update to what I am currently doing with Revit 2017 addins...

    Unsigned certificates
    I have created a batch file that will create a registry DWORD (32-bit) Value for each of the addins in the following location:

    Code:
    HKEY_CURRENT_USER\SOFTWARE\Autodesk\Revit\Autodesk Revit 2017\CodeSigning\
    The name of the DWORD is the GUID found inside the .addin file called <AddInId>. The DWORD value is 1. (See screenshot attached below)


    Here is an example for importing my BIM Consortium addin, which is currently unsigned, into the registry. You can add all of the addin GUIDs to the reg file instead of doing each one individually.

    bimcon.reg file:

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\SOFTWARE\Autodesk\Revit\Autodesk Revit 2017\CodeSigning]
    "08286877-1fdf-4dec-bb62-0a6259c5aedb"=dword:00000001
    bimcon.bat file

    Code:
    reg import bimcon.reg

    Signed Addins
    First you need to extract the certificate file from the addin. To find which file contains the certificate, you have to look inside the .addin file for the file listed in the <Assembly>. It will be a DLL file. Using Bluebeam's addin as an exmaple, here is what they have in their .addin file:

    Code:
    <Assembly>C:\Program Files\Bluebeam Software\Bluebeam Revu\2016\Pushbutton PDF\Revit\Revit2017\BbRevitAddin2017.dll</Assembly>

    Browse to the file's location in Explorer and right-click it to get to its properties. Go to the Digital Signatures tab and click the Details button. In the next dialog, click on the View Certificate button. In the next dialog, go to the Details tab and click the Copy to File button. This starts an export wizard, just click through the prompts using the default values and then select a location for the certificate file. (See attached image below for visual steps).

    Once you have the certificate file exported, use the following commandline (put in a bat file for easier execution) to install the certificate in your computer.

    Code:
    certmgr.exe -add Bluebeam.cer -c -s -r localMachine TrustedPublisher
    NOTE: You will need to have Visual Studio or the Windows SDK installed to have the certmgr.exe file. If you don't want to install either of those contact me and I will send you the program file since I can't upload an exe file to this forum.


    Let me know if anything isn't clear and I will edit this post to clarify.
    Attached Thumbnails Attached Thumbnails Revit 2017 Signed Addins NOT Always Loading-unsigned-addins-registry.png   Revit 2017 Signed Addins NOT Always Loading-extract-certificatate.png  
    cganiere likes this.

  3. #13
    Administrator Gordon Price's Avatar
    Join Date
    December 7, 2010
    Location
    Rotterdam, South Holland
    Posts
    3,034
    Current Local Time
    08:01 PM
    Troy,
    You can also extract the certificate of a signed addin right from the installer. No need to install and go hunting for a DLL. And, you beat me to the topic. I was planning on blogging on this very thing as soon as I have my Managed Dynamo Rollouts stuff done. A day late and a dollar short.

    Gordon

  4. #14
    Member troygates's Avatar
    Join Date
    December 17, 2010
    Location
    Southern California
    Posts
    143
    Current Local Time
    11:01 AM
    I didn't know about the installer part, that's great to know. Will save me a lot of trouble.

    I think you should still blog about it, I think its important to get in front of as many people as possible because its only going to get worse in the upcoming releases.

  5. #15
    Administrator Gordon Price's Avatar
    Join Date
    December 7, 2010
    Location
    Rotterdam, South Holland
    Posts
    3,034
    Current Local Time
    08:01 PM
    Yeah, I plan on it. Maybe in a week or so, to spread it out. I may use it as one of my first YouTube videos too. Good stuff. Thanks for posting here. Best place to get the info first.

    Gordon

  6. #16
    Administrator Gordon Price's Avatar
    Join Date
    December 7, 2010
    Location
    Rotterdam, South Holland
    Posts
    3,034
    Current Local Time
    08:01 PM
    Interesting. It seems like there may be more to handling the unsigned stuff than just the one registry tweak. I just installed the new Zoom2Awesomer, and still getting the popup on the application. Sigh.

  7. #17
    Member Barrie's Avatar
    Join Date
    August 3, 2011
    Location
    Kent, UK
    Posts
    217
    Current Local Time
    08:01 PM
    I wanted to see if choices were being written to the users registry so I renamed CodeSigning to old_CodeSigning and rebooted the user's computer. A new version of CodeSigning was created but unexpectedly it has sorted the issue so much as the user isn't being prompted every session. Perhaps the registry entry had become corrupt.

  8. #18
    Junior Member
    Join Date
    April 12, 2011
    Posts
    10
    Current Local Time
    11:01 AM
    Quote Originally Posted by Barrie View Post
    I wanted to see if choices were being written to the users registry so I renamed CodeSigning to old_CodeSigning and rebooted the user's computer. A new version of CodeSigning was created but unexpectedly it has sorted the issue so much as the user isn't being prompted every session. Perhaps the registry entry had become corrupt.
    It is recreating the HKEY_CURRENT_USER CodeSigning entries from the duplicate entries under
    HKEY_USERS\S-1-5-21-3041061553-3618483182-1112744232-1807\Software\Autodesk\Revit\Autodesk Revit 2017\CodeSigning

    (note that the last 4 or 5 digits vary from machine to machine, and appears to be random/unique; on my Win10 machine it ends with -1670 and on other's Win7 machines values include -1701 -1806 -1807 .

    A reboot is not required; I deleted them from HKCU and after a few minutes, they reappeared, and I had not reopened Revit.

    The presence of the CodeSigning entries in both locations does not prevent Revit from randomly reprompting.

    I hope we can get to the bottom of this, because having Revit randomly re-prompt even after choosing Always Load is quite annoying to users.

    Has anyone tested if this is still going to be a problem in 2018?

    Perhaps Autodesk programmers don't understand the meaning of "always". ;(

    @Gordon - Hi from Portland - Rusty

  9. #19
    New Member
    Join Date
    November 6, 2017
    Posts
    2
    Current Local Time
    08:01 PM
    hi rgesner,

    did you get any further in this? it appears the random reprompt still happens in 2018. would die for knowing the answer to this.

    cheers mo

  10. #20
    New Member
    Join Date
    November 6, 2017
    Posts
    2
    Current Local Time
    08:01 PM
    i found out, that by deleting all entries within HKEY_CURRENT_USER\Software\Autodesk\Revit\Autodesk Revit 20XX\CodeSigning and restarting Revit choosing "always load" again the choice sticks. I don't know if it will return in the future but this held up for a few weeks now without problems.

    hope this helps.

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. Replies: 0
    Last Post: May 27th, 2016, 06:45 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •