https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64697#M17430 I was having the same problem, happy to say that the above solution of reregistering the dll fixed it.<BR />Thanks for your help.<BR /><BR /> Mon, 02 Sep 2019 16:09:00 GMT JosephHayward 2019-09-02T16:09:00Z https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64694#M17427 Hi all. I'm currently developing a PoC for a client, and the resource pc I've been provided runs on Windows 7, and I started developing with MS Office 2010 installed. Midway through development, the pc had an automatic installation of the Office 365 2016 package. After that installation, I have not been able to spy any element using AA mode, nor identify previously spied elements. This is obviously a problem as they were the only solution for certain parts of the process. When attempting to spy in AA mode, I can generally only spy the main window (where before I could spy individual elements). For a "Save As" Windows prompt I can see individual elements but not succesfully spy them. The errors I get when attempting to spy are of the following type: System.ApplicationException: Unable to cast COM object of type 'System.__ComObject' to interface type 'Accessibility.IAccessible'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{618736E0-3C3D-11CF-810C-00AA00389B71}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). at BluePrism.AMI.clsAMI.Spy(clsElementTypeInfo&amp; elementType, List`1&amp; identifiers) at AutomateUI.frmIntegrationAssistant.HandleSpyOrLaunchClick(Object sender, EventArgs e) I have tried the solution outlined here: <A href="https://blogs.msdn.microsoft.com/sm...ft-visualstudio-ole-interop-iserviceprovider/" target="test_blank">https://blogs.msdn.microsoft.com/sm...ft-visualstudio-ole-interop-iserviceprovider/</A> but to no avail. Any input is much appreciated! Thanks in advance, Nico Tue, 29 Jan 2019 18:03:00 GMT https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64694#M17427 NicoEsposito 2019-01-29T18:03:00Z https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64695#M17428 We too got same issues,then downgraded to 2010 version Tue, 29 Jan 2019 20:47:00 GMT https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64695#M17428 Murali_MohanKon 2019-01-29T20:47:00Z https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64696#M17429 Did you tried to reregister OLEACC.DLL? from cmd with administrator rights: cd c:\windows\system32\ regsvr32.exe oleacc.dll &nbsp; Fri, 01 Mar 2019 19:06:00 GMT https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64696#M17429 MindaugasBresku 2019-03-01T19:06:00Z https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64697#M17430 I was having the same problem, happy to say that the above solution of reregistering the dll fixed it.<BR />Thanks for your help.<BR /><BR /> Mon, 02 Sep 2019 16:09:00 GMT https://community.blueprism.com/t5/Product-Forum/Unable-to-spy-in-AA-mode-after-Office-2016-update/m-p/64697#M17430 JosephHayward 2019-09-02T16:09:00Z