There are network adapters on the system that are disabled and TurboActivate couldn't read...

[Hans Donkersloot]

Today whenever I start IntelliJ I am faced with this screen:

I believe it's because my trail has ended, and I do have a key to activate, but I'm not able to do anything (not even get to the offline activation) without IntelliJ closing and disabling Illuminated Cloud

[Scott Wells]

Hi, Hans. That issue is actually caused by the licensing software independent of the relationship between trial and full license. On Windows 7 it means that you need to ensure that all network interfaces are enabled long enough for the licensing software to be able to create a unique "fingerprint" for the machine. You can disable unused network interfaces after that. On higher versions, in particular Windows 10, it could mean that you have a WMI corruption. Here's how to resolve that:

https://support.quest.com/vworkspace/kb/88861/how-to-repair-or-fully-rebuild-windows-wmi-repository

You mentioned that it's disabling the plugin. That was a behavior of Illuminated Cloud 1. Illuminated Cloud 2 should keep the plugin enabled but disable its features. Can you verify that you have the Illuminated Cloud 2 plugin installed and not the older one?

Let me know whether any of that helps or not.

[Hans Donkersloot]

Whoops, I am using Illuminated Cloud 1, not Illuminated cloud 2

[Hans Donkersloot]

Hi Scott, thanks for the quick reply! I am on Windows 10, but unfortunately I've tried the repair of WMI and windows reports that "WMI repository is consistent". The night before I started having issues I installed windows update KB4456655 , KB4457146 , and KB4457128 - I'm not sure if it's a coincidence that I started having these issues directly after installing these updates or not

[Scott Wells]

Okay. Can you run these two commands:

Get-WmiObject MSFT_NetAdapter -Namespace root\StandardCimv2

and:

Get-WmiObject -Class "win32_networkadapter" | Format-List *

and capture the output of each in a text file, then send me those files? I'll need to send them to the licensing software vendor who should be able to determine what's going on quickly. Thanks, and sorry for the nuisance! We'll get it figured out for you.

[Hans Donkersloot]

I'm getting an Error when I try and run the first command (Though the second command completed just fine):

and what is the easiest way to send you the text files with the output?

[Scott Wells]

You can email them to [e-mail]. I should have mentioned that you need to run those commands via PowerShell (not cmd), and you may need to do so as administrator if you have the ability to do so on your machine.

[Hans Donkersloot]

I've sent the .txt file of the output for the second command to that email. Unfortunately I am running the commands in PowerShell and as an administrator, but the first command still gives me an error

[Scott Wells]

Got it, Hans. Thanks. And yes, I noticed the PS prefix to the prompt after I sent that message. I've forwarded the details to the licensing software vendor for additional information. Hopefully they'll give a solution quickly. I'll let you know as soon as I receive something.

[Scott Wells]

Hans, they still think it's a bad WMI and provided this detailed info on how to try to fix it:

https://wyday.com/limelm/help/faq/#fix-broken-wmi

Can you try that and see whether it helps or not? Please let me know either way.

[Hans Donkersloot]

Unfortunately, no dice. Perhaps they are not wrong with the bad WMI as when i try and run the Get-NetAdapter command I recieve this error:

I've also tried salvaging and rebuilding my WMI from scratch (even though it says it's okay) but neither have worked. I also ran the WMI Diagnosis Utility 2.2 suggested from that link, I will email you the log results if that can help at all

[Scott Wells]

Okay. Let me follow up with the licensing folks since they're the subject matter experts in this area and see what they suggest.

[Scott Wells]

Issue was WMI corruption that, according to Wyday, would be prohibitively difficult to repair. User chose to install Ubuntu vs. reinstalling Windows.