Open Text Windows Viewer–virtual vs native install

If you have a native install of Open Text Windows Viewer (any version) and want to contaiimagen and co-operate a virtualized Open Text Windows Viewer you might run into a problem if the application uses certain COM-objects. As opposed to star the virtualized instance – the native application gets called every time. Try removing the following value while in monitoring mode;

HKCR\CLSID\ {30446849-11E3-11D0-9D4E-0020AFC0E4C0}\InprocHandler32

If you review the activity using Process Monitor – you will notice that SVCHOST.exe is the process that attempts to start alviewer.exe. The reason is explained by Sasha in one of the previously posted interviews.

Leave a Reply

Your email address will not be published.