Before I forward this issue to our QA team for further analysis,I need your help to provide with us the following information:ġ:Please describe the working environment of your Foxit PhantomPDF and OS information？Did you install it on a server environment or end users' computers. RedFive ,I sincerely apologize for the stange issue you encounterred with.As far as I know,there is no other user has reported such issue yet. Tried Googling, searching forums and the KB, but not finding anything similar. That was in the middle of a bunch of other msi installer events regarding office 16 updates.ĭid Office 16 just kill foxit? if so, why? Was Foxit trying to do updates and failed? We've seen this on at least 5 workstations as of this morning. You must undo the changes made by that installation to continue. An installation for Foxit PhantomPDF is currently suspended. 'Product: Office 16 Click-to-Run Extensibility Component - Error 1704. The only evidence, in one user's event log was this: The folder structure for Foxit Phantom still existed in Program Files, but ALL of the executable, dlls etc were gone. Pretty much all of the installs needed someone to manually set Phantom as default PDF app, but whatever.Īnyway, everything was fine until this morning, when several users had their applications disappear. Ran the script remotely through n-central. Ended up not using the Transforms and XMLs, instead using the msi options. Installed Phantom on about 35 workstations last week using the deployment guides.

Anyone else have this issue? the other night after hours, ALL of the Foxit files disappeared from Program Files (x86), leaving the file structure in place.

Foxit phantompdf portable