ComponentOneLicenseAdder warning after update to .779

ComponentOneLicenseAdder warning after update to .779

Posted by: wknauf on 11 June 2026, 10:40 am EST

• 

  wknauf

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 11 June 2026, 10:40 am EST - Updated 11 June 2026, 10:45 am EST

  Hi C1,

  after having installed the C1 update to .779, Visual Studio 2026 Professional shows a warning “The ComponentOneLicenseAdderPackage package did not load correctly” whenever I open a solution:

  

  “ActivityLog.xml” from the screenshot contains nothing helpful I think:

    <entry>
      <record>626</record>
      <time>2026/06/11 14:38:04.567</time>
      <type>Information</type>
      <source>VisualStudio</source>
      <description>Begin package load [ComponentOneLicenseAdderPackage]</description>
      <guid>{92631D4C-9144-4F0A-ABD2-39F70C8D94AF}</guid>
    </entry>
    <entry>
      <record>627</record>
      <time>2026/06/11 14:38:04.583</time>
      <type>Error</type>
      <source>VisualStudio</source>
      <description>SetSite failed for package [ComponentOneLicenseAdderPackage](null)</description>
      <guid>{92631D4C-9144-4F0A-ABD2-39F70C8D94AF}</guid>
      <hr>0x80131509</hr>
      <errorinfo></errorinfo>
    </entry>

  The extensions seems to be installed:
  
  

  

  439×655 33 KB

  Do you have an idea what this means?

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 12 June 2026, 12:24 am EST

  Hello Wolfgang,
  
  Thank you for providing the details.
  
  This behavior has already been reported to our development team, and as per the team the reported issue is a bug. Rest assured, we will update you as soon as we have more information from them.
  
  In the meantime, selecting the “No” option on the dialogue will prevent the message from reappearing during startup. Even though the extension stops working, it would allow you to continue using Visual Studio without this annoying error.
  
  [Bug Tracking ID: C1-10097]
  
  Regards,
  
  Uttkarsh.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 15 June 2026, 7:58 am EST

  Hello Wolfgang,

  The issue has been fixed in the latest version of ComponentOneControlPanel.

  To resolve this issue at your end, please do a fresh installation of C1:

  1. Uninstall ComponentOneControlPanel using Windows Control Panel.
  2. Install the latest installer from https://developer.mescius.com/componentone/download.
  3. Download the C1WinForms Suite.

  Regards,
  
  Uttkarsh.

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 15 June 2026, 9:50 am EST

  The download brings “ComponentOneControlPanel_226.4.391.exe”, and my installed Control panel version is also 2.26.4.391 (see version in screenshot at https://developer.mescius.com/forums/winforms-edition/controlpanel-does-not-display-net-10-winforms-components). So I already have the current ControlPanel. Or should I perform this step anyway?

  What will happen with the license during installation/deinstallation? Will it be kept on my machine or will I have to re-register it?

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 16 June 2026, 2:23 am EST

  Hello Wolfgang,
  
  The ComponentOneControlPanel is our web installer that downloads files directly from our servers. The installer’s version remains v2.26.4.391, however, the development team has updated the latest configuration files on our servers, so the installer now downloads the fixed extension.
  
  Should you still reinstall? Yes, please perform the reinstallation step anyway. Even though the version number matches, a fresh install should resolve the issue.
  
  What happens to your license during uninstallation? Your license will remain completely activated on your machine throughout the reinstallation process. License activation data is maintained entirely separate from the installation.
  
  Will you need to re-register? No, you are not required to re-register your license after a standard reinstallation. A license only gets deactivated if you explicitly choose to deactivate it directly through the License Manager tool.
  
  Regards,
  
  Uttkarsh.

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 16 June 2026, 4:24 am EST - Updated 16 June 2026, 4:29 am EST

  Thanks, I can confirm that this works. Now, version 2026.1.1.2 of the extension is installed.
  
  

  

  410×543 32 KB

  Best regards

  Wolfgang

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 29 June 2026, 2:51 am EST - Updated 2 July 2026, 3:34 am EST

  Strange - the error is back again and seems to happen again for solutions that worked last week. The extension version is still 2026.1.1.2.

  I installed the VS 2026 update from 18.7.0 to 18.7.2 the end of last week, but I am not sure when it was exactly, and I think it still worked afterwards.

  Attaching a second Visual Studio debugger, I found a “System.DivideByZeroException: ‘Attempted to divide by zero.’” with this call stack:
  
  

  

  1136×842 120 KB

  The disassembly of the failing method looks like this:
  
  

  

  1311×184 33.5 KB

  public static string a(string a, int b)
  {
    DateTime dateTime = default(DateTime).AddYears(-(-511634467 ^ 0x1E7EE3F3) >> 1).AddMonths((-413676063 ^ 0x1AFE62F1) + 39211253).AddDays(26.569976851851852);
    if (DateTime.Now > dateTime && 0 == 0)
    {
      int num = -147781983 - -147781983 >> 6;
      num = -(~(-662181717 - -662181717)) / num;
    }
    return h.b.b.c(a, b);
  }
  

  The first line results in a DateTime value “2026-06-27 13:40:46”, which is before “DateTime.Now” and thus enters the “if” where “num” becomes “0”.

  What is the meaning of the DateTime value and is there a workaround?

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 29 June 2026, 5:33 am EST

  Hello Wolfgang,

  We could observe the issue again as well. We’re getting in touch with the development team and will update you once we have more information.

  Regards,
  
  Uttkarsh.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 29 June 2026, 7:01 am EST

  Hello Wolfgang,

  The team is asking if you could share the sample along with exact steps replicating “System.DivideByZeroException” error? It’ll help them trace the issue.

  Regards,
  
  Uttkarsh.

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 29 June 2026, 7:12 am EST

  Hi Uttkarsh,

  what should I share ;-)? It happens with every project that I open with Visual Studio 2026. I just created a new .NET10 “Windows Forms App” sample project, and the message came directly when the solution was automatically opened.

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 30 June 2026, 12:08 am EST

  Hello Wolfgang,

  We were trying to replicate the following:

  “Attaching a second Visual Studio debugger, I found a “System.DivideByZeroException: ‘Attempted to divide by zero.’” with this call stack:”

  We attached a second Visual Studio debugger but did not observe “System.DivideByZeroException" error when ComponentOneLicenseAdder warning occurs. We think we’re missing a step. We did check “Common Language Runtime Exceptions” in Debug → Windows → Exception Settings, but it did not help.

  Edit: We have shared details with the team and will inform you when we have further updates from them.

  Regards,
  
  Uttkarsh.

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 30 June 2026, 2:09 am EST - Updated 30 June 2026, 2:14 am EST

  Hi Uttkarsh,

  you will also have to uncheck “Enable just my code”.
  
  

  

  922×518 37.5 KB

  Then, you will have to skip a lot of VS internal exceptions (maybe uncheck some of them in the “Exception settings” list if they come too often) until you hit the license adder exception. I don’t know whether this is also the reason for the extension not loading, might be caught internally.

  Best regards

  Wolfgang

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 30 June 2026, 3:03 am EST

  Hello Wolfgang,

  Thank you for the information.

  The team is looking into the issue. If you face any issue with this extension, you can uninstall it. It is only required for WebForms.

  Regards,
  
  Uttkarsh.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 8 July 2026, 11:58 pm EST

  Hello Wolfgang,

  As per the team, the reported issue is a bug. [Bug Tracking ID: C1-10415]
  
  Currently we do not any ETA for the fix, but rest assured, we’ll update you once the issue is fixed.

  Regards,
  
  Uttkarsh.