Hello all,
My first post on here, so please forgive any inadvertent transgressions.
As the subject line indicates, I'm having problems after upgrading to Foxit Portable v. 9.3.0.10826, last week.
Initially, I sought help on the Foxit Reader forum, http://forums.foxitsoftware.com/forum/portable-document-format-pdf-tools....
I realise that cross-posting is frowned upon but since the response there suggests that it is a PortableApps problem, I'll just paste my own posts here:
"I've been very happy with free Foxit Reader, and recommended it to may others. It's always been fine for me, and I value the facility to add highlights, comments, and take snapshots. Great!
I use the portable edition on a USB drive permanently plugged in, because I like the idea of keeping the Windows intallation as "clean" as possible, together with being able to try the odd utility from time to time with no uninstallation problems. Again, been fine for quite some time.
This week, Foxit Reader suggested updating. I declined the prompt in case it would do a full OS install, but went back to the Portable Apps main screen where the update was offered, and did it from there. I now have 9.3.0.10826.
Problem: Although the Foxit Reader app would open normally, and any pdf could be opened from within the programme, clicking on pdf files in explorer or on desktop shortcuts produced the message that I needed to reinstall FR because I was missing localService.dll. Reinstalled a couple of times, but nothing changed. Checked W7 file associations, - all OK. Tried changing file association to another pdf reader (portable app), everything back to normal, but not as good as Foxit.
File associations returned to Foxit, and I'm back to dll error message.
Did a system file check which advised me that "Scannow windows resource protection did not find any integrity violations".
Could some kind person tell me what I am missing, please, (apart from a dll !) I'm slightly IT savvy, but not overly so, and don't want to dabble with the registry. "
"Many thanks, (moderator) for your advice and fast response. However, I'm wondering whether your comments apply to the PORTABLE installation which is what I'm having trouble with. In that situation, Foxit correctly does not appear in the add/remove programmes, this process being performed through the PortableApps.com application and platform.
In fact, I'm wondering whether the update provided there could (inadvertently) be for the DESKTOP version of your product, and this might be the reason for my problem. Nevertheless I assume that it would have originated from your own developers.
As I mentioned in my original post, I prefer to use portable apps kept on my permanently attached USB drive when possible for the very reason that I want to avoid having to make manual changes to the registry when uninstalling software, since I am not confident about doing so. As requested, I now include a screenshot of the error message when trying to open the portable version directly from a pdf file, although as stated, Foxit Reader functions OK if opened first. Other (portable) readers will start their programme directly from the pdf document, as was previously the case with Foxit Reader until the 9.3 update was applied. It is this behaviour that makes me unsure that the update was intended for the portable version. I really don't want to install the desktop version at this point in case the problem persists and I am then driven to having to mess with the registry. "
My posts there are accompanied by a screenshot of the error message.
I must advise that I've held off doing the v16 PortableApps update, as I've read of some people having current problems with that here, and don't want to complicate things further, at the moment.
I like Foxit, but installing it within Windows OS goes against the advantages of using PortableApps, of which I am an enthusiast. As I've mentioned, Foxit has been great until now, but I've been obliged to switch to another pdf reader from PortableApps, at least for the moment.
Can anyone advise me, please?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
In my previous post, I now realise that I failed to explain that the Foxit moderator advised me that their company had not produced the portable version that I am having difficulty with. I had wrongly assumed that PortableApps had obtained it from them, but their advice would now suggest that maybe the update downloaded from PortableApps had been converted by themselves. It is for that reason that I am now enquiring on this forum, and hope that someone can enlighten me. Thank you.
As mentioned at the top of the page when creating a forum post, please "include system details (OS version, 32 vs 64-bit, install path, new vs upgrade, etc)."
Sometimes, the impossible can become possible, if you're awesome!
Apologies for my omissions.
OS is Windows 7 premium, 32 bit
Not sure how exactly to specify install path, but thePortableApps application was installed some time ago directly on my USB drive, where the contents of it's directory are as follows:
H:\PortableApps\PortableApps.com\PortableAppsUpdater.exe
H:\PortableApps\PortableApps.com\readme.txt
H:\PortableApps\PortableApps.com\whatsnew.txt
H:\PortableApps\PortableApps.com\PortableAppsPlatform.VisualElementsManifest.xml
H:\PortableApps\PortableApps.com\App
H:\PortableApps\PortableApps.com\Assets
H:\PortableApps\PortableApps.com\Data
H:\PortableApps\PortableApps.com\Other
H:\PortableApps\PortableApps.com\PortableAppsBackup.exe
H:\PortableApps\PortableApps.com\PortableAppsBackupRestore.exe
H:\PortableApps\PortableApps.com\PortableAppsPlatform.exe
As mentioned in my previous post, versions up to 9.2 worked perfectly fine, but after update (directly within the app. platform) to 9.3, pdfs can be opened only within the app (starting it first), and not from the files themselves. I have described my attempts to resolve this by ensuring that file associations are correct.
File version is 2.2.1.0 of 6/10/18. but only applied last week. The opened Foxit app shows Version: 9.3.0.10826 (number copied and pasted)
Grateful for any help, and will be happy to provide any further information required.
How did you associate it with local files? You can not use the file association settings within the app itself as this will not work correctly. You must use a third party tool to associate FoxitReaderPortable.exe with PDF files.
Sometimes, the impossible can become possible, if you're awesome!
Thank you for your interest and your response.
I'm afraid that I do not recall how my pdf files previously came to be associated with Foxit Reader Portable 9.2, downloaded about a year ago from the PortableApps platform. I suspect that the association occurred automatically, but I cannot be sure of this.
After updating to 9.3 (through the platform) I experienced the problem and error message previously referred to, regarding missing dll
As a working pdf reader is essential to me, the following procedure was followed:
Desktop screen
Windows/globe symbol bottom left in tray
Default programmes
Associate a file type or protocol with a programme
pdf selected from list of file types
Options (originally) : 2007 Microsoft Office component, Microsoft Office Word, Firefox, Foxit reader 9.2, Other programmes
Browse
Navigate to USB 'H' drive
Portable Apps
Foxit reader portable folder
Foxit reader portable.exe selected (Version verified by properties: 6/10/18 creation date).
Following this procedure enabled me to associate pdf files with both the other two portable apps installed, Sumatra and XnView. Both associations were successful in turn, but the error message came back when Foxit was restored as the default.
Subsequent to this, these alternative apps became selectable in the list of recommended programmes. However, I noticed that the option for Foxit remained labelled as ver. 9.2, even though the updated exe (verified as above) was selected. This may be a clue. But this association process has worked because of two indications as follows, (1) On dismissing the error message Foxit does momentarily open, (2) when the association with Foxit has been made, it consistently produces the Foxit error message. That same association process was sucessfully used to select one of the other two pdf readers installed within PortableAps pending resolution of the Foxit problem.
The fact remains, however, that prior to the update, Foxit 9.2 worked impeccably. I have tried repeating the update as the error message suggests.
I hope that this detail helps, and I look forward to receiving the favour of your further advice. Thank you.
For me disabling a plugin by renaming solved the problem:
FoxitReaderPortable\App\Foxit Reader\plugins\ConnectedPDFPlugin.fpi.disabledByJLi
This is fixed in Foxit Portable 9.5.0.20723.
Sometimes, the impossible can become possible, if you're awesome!