Forum Discussion

haeussler's avatar
haeussler
Level 4
8 years ago
Solved

EV Fall Creators Update - No such interface supported

Hello together,

a customer faces the following problem. After update to the Windows 10 Fall Creators Update with EV 11.0.1 CHF5 he is not able to open archived items. Other actions such as restore or the search are working fine.

If the customer installs Windows 10 Fall Creators Update directly (ISO) to the client EV is working fine.
If the customer perfome a Inplace-Update over WindowsUpdate the following errors are shown. (img01.jpg)

Currently he uses as workaround the office repair tool. After that it works also fine.

In the compatibility chart the Fall Creators Update is supported with the current version.

Kind regards,

Lucas

7 Replies

  • Hi there,

    What is the Outlook version?

    Is it possible that the Windows update causes an issue for Outlook.

    Have you also tried recreating the Outlook profile after the Windows update?

    • haeussler's avatar
      haeussler
      Level 4

      Hi,

      the customer uses Outlook 2016 32bit. They already tryed recreating the outlook profile but this doesnt works. Only the repair mode for outlook.

      Any ideas?

      • GertjanA's avatar
        GertjanA
        Moderator

        Hello,

        As you probably have seen, there have been some issues with patches from Microsoft causing issues with Enterprise Vault client (and other software). These have been resolved using registry keys, or using a new client. In your case, as you state that installing the update direct, or repairing Office, I don't think it is one of the patches causing the issue. I'm missing in your initial mail if you have tried reinstalling the EV Client?

        What you also might want to try is to run EVResetClient.exe from the folder where the client is installed. From the description however, this seems to be more related to Microsoft then to Vrts EV. But, we'll try to help as good as we can. I'll look for the KB articles on the 2 issues.

        1 - KB 1

        2 - KB 2

        You might want to check KB 2, which sort of has your description. If the issue is on a system, apply the registry keys, see if that fixes it.