Windows Updates 2

[kr7530]

Windows updates tried installing last night and this morning the computer was stuck on installing 3 of 3. We powered it down, when it came back up everything seemed to be fine except catia can't find our license server. Those that didn't install the updates are working fine. Any ideas as to what got changed and what we need to do? We checked the firewall and that seems to be the same as it was and we tried restoring the system but it failed for some reason.

Thanks,
Kevin
V5R22

 

[kr7530]

For anybody that is having the same issue, this is what our IT dept. found

...following Microsoft Update broke the TLS connection for license usage by increasing the key length on the Windows machine to 1024 and the server is only supporting 512.

KB3061518

The fix right now is to update the registry as MS recommends in the articles below

Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman
On the Edit menu, point to New, and then click DWORD Value.
Type ClientMinKeyBitLength for the name of the DWORD, and then press Enter.
Right-click ClientMinKeyBitLength, and then click Modify.
In the Value data box, type 00000200, and then click OK.
Exit Registry Editor, and then restart the computer.

Regards,
Kevin

https://support.microsoft.com/en-us/kb/3061518

https://technet.microsoft.com/library/security/MS15-055

 

[itsmyjob]

thanks for the info.

Are you using LUM or DSLS?

What CATIA level are you using?

Eric N.
indocti discant et ament meminisse periti ​

 

[JeniaL]

this morning the same happened to us. i cant find it in registry \Diffie-Hellman. \KeyExchangeAlgorithms is empty.

 

[kr7530]

We are using DSLS and are on V5R22 with Windows7 Pro

Kevin

 

[GaryBaker]

@tikito

If you don't have the Diffie-Hellman key, I would just simply create it under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms

Then add "ClientMinKeyBitLength" set to 0x00000200(512) as Microsoft suggests.

GB

 

[GaryBaker]

Tata Technologies mentions that removing the KB3061518 will fix the issue (or the workaround above), but also, the DSLS License Server should be on the latest release, ie R2015X.
We are on R2014. We will update our license server this weekend and see if it fixes the issue and allows clients to use a 1024 byte key.

GB

 

[GaryBaker]

Also, the Windows Update being stuck on installing is not related to the license server issue. It is completely separate and can be remedied by simply using CTRL-ALT-DEL to get a normal login screen or restarting the computer with the power button.

GB

 

[JeniaL]

thanks Gary. our day began with uninstalling windows update. finally we got Catia back to work.