Paul Patruno 

Please advise what version of Trados Studio and MultiTerm you are using.  Incompatibility between these products can be the cause of problems.  The current versions are:

Trados Studio 2022 - 17.0.3.11695
MultiTerm 2022 - 17.0.0.1685

I am using both latest versions of Trados Studio and MultiTerm.

The issue with Windows 11 version 2H22 "Object reference no set to an instance of an object" is also there with Studio 2021 SR2 16.2.12.9338 and Multiterm 2021 16.0.0.1658 on y backup laptop (I will have to reimage it back to windows version 1H22.

Paul

Paul,

How can I set back the notifications on my RWS community account as I am missing those notifications on my recents posts?

I have installed again Windows 11 version 2H22 after the latest Studio 22 version 17.0.4.1329 update and got the same issue when trying to add a new term to the existing Termbase. Before the update, the project I used was the same, the Termbase was the same and I had no error reported.

I will have to revert again to my image of Windows 11 version 1H22.

One more issue. I started Multiterm 2022 170.0.0.1685 and tried to open a termbase and Multiterm crashed after showing this error message

Paul Patruno 
That error message is documented here
The solution is to uninstall and reinstall Multiterm. 

OK for the Multiterm. That was on my backup laptop and it is a side issue. I will reinstall it.

The main issue is that upgrading Windows from Windows 11 version 2H21 to Windows 11 version 2H22 makes TRADOS STUDIO to be in error.

Error message "Object reference no set to an instance of an object"

It happened to me twice with a first install 17 days ago running Studio 2022 SR2 17.0.3.11695 and Multiterm 2022 2022 - 17.0.0.1685

Last time was 2 days ago running Studio 2022 SR2 17.0.4.1329 and Multiterm 2022 170.0.0.1685

If you could post the error details, I might be able to help.
Also, have you tried uninstalling and reinstalling Trados Studio as well?

Trados Studio was working perfectly before the Windows update and failed when trying to Add a New Term from Studio 2022 after the update and is working perfectly after I reverted to the previous image of Windows.

I have installed the windows version 2H22 twice and reverts to version 2H21 twice, and at every time I got the small windows Error message "Object reference no set to an instance of an object".

I have my work to do and need to be able to update my termbase for running my QA. 

Finally, I got some time to try a thisd time and after install of the Windows update 2H22, I got the same issue.

This time, I decided to try a Studio repair and after the repair, trying to Add a New Term from Studio 2022 worked again without the dreadful  error message "Object reference no set to an instance of an object".

Still puzzled, but relieved, to see that a working Studio would become corrupted by an update to Windows 11.

Finally, I got some time to try a thisd time and after install of the Windows update 2H22, I got the same issue.

This time, I decided to try a Studio repair and after the repair, trying to Add a New Term from Studio 2022 worked again without the dreadful  error message "Object reference no set to an instance of an object".

Still puzzled, but relieved, to see that a working Studio would become corrupted by an update to Windows 11.

Paul Patruno 

Similar here. After update to Win 22H2 the term recognition in Studio was broken. Reorganizing all termbases didn't help, but a repair of Studio did. Now all works as expected.

Paul 

Across people have sent a warning that their software will not work with Windows 22H2 and they will release a patch on a date xx.xx.2022. Might be a good idea for RWS to send out a message, that a repair installation of Trados Studio after this Windows update might be necessary.