how to disable browser integration

[Hugo]

How do I prevent Foxit to open pdf files inside the browser window for IE6 (and for firefox too).

With acrobat reader there was a setting to allways open pdf files in the acrobat window, althought IE did not show a download dialog.

with foxit, IE does show a standard download dialog, but when I click "open" it will be embedded in IE nevertheless

On a related note, how do I uninstall foxit? there was no installer, so which settings do I have to change so that windows behaves as if it does not know anything about pdf at all?

thanks for any help

[Andreasm82]

>>On a related note, how do I uninstall foxit? there was no installer, so which settings do I have to change so that windows behaves as if it does not know anything about pdf at all?

Just delete foxitreader :)

[Hugo]

>>>On a related note, how do I uninstall foxit? there was no installer, so which settings do I have to change so that windows behaves as if it does not know anything about pdf at all?

>Just delete foxitreader :)

Uhm, but to integrate with IE foxit must have made some changes to the registry, right? what will happen to them once I remove foxit?

I actually do not want to remove foxit completely, just remove all registry and other changes.

[GeoffB]

How do I prevent Foxit to open pdf files inside the browser window for IE6 (and for firefox too).

I looked at this today. There's two key bits you need to look at in your
registry (and some other stuff, if you're a clean freak!)...

(1) In HKCR, there's a key called '.pdf'. Edit or delete that (that's the basic
file association for .pdf files).

(2) the above .pdf entry refers to another link, also in HKCR, called
'FoxitReader.Document'. Inside that one, there's a lot more stuff.
The file open on double-click functionality is the result of the
HKCR\FoxitReader.Document\shell\open\command\ ( Default ) entry.
Removing that stops the file open thing. Its actually OK to remove the
whole "FoxitReader.Document" section I think. If you're not using
Foxit, you don't need that at all.

Those two are the bits that make the file association work. There are other
bits in the registry, searching for "FoxitReader.Document" and removing
will clean most stuff. I haven't done an exhaustive search, but when
I removed .pdf + anything referring to "FoxitReader.Document", both windows
and the Foxit PDF executable behaved as if Foxit PDF reader hadn't
been installed at all.


With acrobat reader there was a setting to allways open pdf files in the acrobat window, althought IE did not show a download dialog.
Careful, since you're going to drop IE and never use it again (haha. IE is evil, want to stop spyware, stop using ie) and instead use Firefox, then opening
PDF Files (with Adobe Acrobat Reader set to the default handler) actually
breaks Firefox, slows it down, etc. If you go to Tools -> Options -> Downloads -> Plugins in Firefox and turn OFF everyhing PDF and PDF-like, then it opens PDFs externally in the reader, not in the browser, and it works a lot more smoothly.


with foxit, IE does show a standard download dialog, but when I click "open" it will be embedded in IE nevertheless

This is something the browser is choosing to do, not Foxit. Maybe Adobe offers a dialog to do the browser's dirty work for it, but it's really Microsoft's problem, not Adobe. Follow the instructions above for Firefox, I expect that IE should have some similar capability in there somewhere - it's the same concept.


On a related note, how do I uninstall foxit? there was no installer, so which settings do I have to change so that windows behaves as if it does not know anything about pdf at all?

Well,I actually just wrote an installer. That won't help you now of course, 'cos the 'uninstall' only removes the parts it adds itself. My installer does the basic step (1) and (2) I talked about above, and removes only those when you uninstall. (It also puts the Foxit PDF Reader files in a directory in Program Files, makes icons in the start menu (+ desktop + quick start if you want) and sets up the file association if you want). That will revert to "windows doesn't know about pdf" state, but it doesn't completely clean the registry of all Foxit PDF stuff (that's not necessarily bad, unless you're a clean freak! - there's no particular problem with leaving Foxit stuff in there). My installer does that, and then when you run Foxit PDF Reader, it adds a bunch more stuff. I didn't have time to research everything so far, so my installer doesn't attempt to add (or remove) everything.

Details on the installer are in my post in the "Can you please get a normal installer" thread on this forum. My installer uses a free (Inno Setup) installer builder, and I've included full source code inside the installer (in the license section) so if the Foxit Folks decide they want to offer an installer option with their already great reader, then I hope the work I've done already will help them get a good head start.

thanks for any help

You're most welcome sir, I hope this info is useful!

GeoffB :1_11:

[arthur]

GeoffB, quite profession answer! :1_11:
Our design team will add an option to disable IE association later, then you will be able to view PDF outside the browser.

[KyferEz]

I would REALLY LOVE to see an option to disable browser integration added to the Foxit Reader software. I hate PDFs loading in my browser; and sometimes I don't want to right-click and save the PDF, just quickly view it if it's a small file.

I have looked, and do not see a way to alter that... I don't want to disassociate PDFs with Foxit Reader (as I want to double-click the file in explorer and have it launch in Foxit), I just don't want Foxit to load inside Firefox or Internet Explorer (Firefox being the preferred browser).

Thank you,
KyferEz

[Boz]

This has been talked about so many times! There are also many other similar threads.

As you can see above on September 8th, 2005, arthur said it would be done. But here it is 1-1/2 years later, and it still isn't done!

[Boz]

When will the ability to choose to disable browser integration be available?

[alvian]

In the absence of a disable switch in Foxit, here is the next best thing: A registry hack. It worked for me using XPPro IE6-SP1 & Foxit 2.1.

(Note: The registry key is "FoxitReader.Document", all one word. There is a bug in the forum software that inserted a space between "Do" and "cument". Damn bugs everywhere!)

Disable browser integration (save PDF dialogue appears)
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00000002

Enable browser integration (read PDF in IE6)
------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00010000

[Boz]

I tried this to Disable browser integration (save PDF dialogue appears).
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00000002
I copied the text in the Code Box into notepad and named it "Disable browser integration.reg" ran it, and received a confirmation.

Unfortunately, it didn't disable browser integration for me on XP Home SP2 with IE6.

Any advice, alvian? Do you think I did something wrong?

[alvian]

How do I prevent Foxit to open pdf files inside the browser window for IE6 (and for firefox too).

With Foxit, IE does show a standard download dialog, but when I click "open" it will be embedded in IE nevertheless


In the absence of a disable switch in Foxit, here is the next best thing: A registry hack. It worked for me using XPPro IE6-SP1 & Foxit 2.1.

(Note: The registry key is "FoxitReader.Document", all one word. There is a bug in the forum software that inserted a space between "Do" and "cument". Damn bugs everywhere!)

Disable browser integration (save PDF dialogue appears)
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
"EditFlags"=dword:00000002

Enable browser integration (read PDF in IE6)
------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
"EditFlags"=dword:00010000

I tried this to Disable browser integration (save PDF dialogue appears).

Unfortunately, it didn't disable browser integration for me on XP Home SP2 with IE6.


Dear Hugo and Boz,

I have re-read Hugo's first post and his problem description, and Boz's problem with my registry switch. I've come to the conclusion that my registry hack is only half the solution.

The original registry hack controls whether or not the "File Download" dialogue box appears on the screen. (This is assuming you haven't cleared the "Always ask before opening this type of file" option box.) With EditFlag=10000h, the dialogue box does not appear and the PDF opens in the browser right away. With EditFlag=2, the dialogue box appears and you are given a choice of "Cancel" (nothing happens), "Save" (save a copy to file) or "Open".

Hugo had wanted a stand-alone Foxit windows to take over the display of the PDF file when you press "Open", but with my hack the PDF still gets opened in the browser. It was a mistake on my part because originally I only wanted to control the appearance of the "File Download" dialogue box and not really the browser integration.

When you press "Open" the browser downloads the PDF and calls on the "Local Server" to open it inside the browser. Suppose it cannot find a "Local Server" then the browser will ask Windows to deal with the PDF. Windows should use the .pdf file association and start Foxit separately. The registry key for Foxit's "Local Server" is listed below but you cannot simply delete the entry because Foxit is smart enough to repair the "damage", so that the "delete" only works once before you have to delete the key again. :1_22: Instead my solution is to clear the "Local Server" value and then set the key to Read-only. It is going to get messy if you haven't played with registry permission before.

So here is my full solution to the problem Hugo described two years ago. I hope he is still reading this forum. :1_32: The solution is not pretty but it works... I've verified it fully this time around. My apology to Boz who followed my half-solution and was disappointed. :1_01:

Also note my system configuration: WinXP Pro SP2, IE6 for XP, Foxit 2.2. I don't have XP Home and so I cannot verify my procedure works for it.

(1) Start Registry Editor under an Admin or Owner account.

(2) Set "EditFlag=2" as I described earlier.

(3) Go to "HKEY_CLASSES_ROOT\CLSID\{14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}\LocalServer32", double-click the "Default" icon, press "Delete key" to clear the value and click "OK" to confirm.

(2+3 alternate) Save this as a registry file and import it.
--------- Beware of forum bug which inserts random spaces ---------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
"EditFlags"=dword:00000002

[HKEY_CLASSES_ROOT\CLSID\{14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}\LocalServer32]
@=""
--------- End of file ---------

(4) Right-click the "LocalServer32" icon in the tree, select "Permissions..." Dialogue box opens.

(5) Click Advanced, another dialogue box opens.

(6) Clear the "Inherit from parent..." option box. Another dialogue box opens immediately.

(7) Click "Copy" and you are returned to the dialogue box in step (5).

(8) In the "Permission entries" box remove all entries EXCEPT for the "Allow - Users - Read" entry (should be the first entry). A quick way to do this is left-click the second entry, then Shift-Left-Click the last entry (i.e. left-click while holding the Shift key), and then click the "Remove" button.

(9) Check again. If you made a mistake then press "Cancel" or "Escape key" and repeat from step (5). You want only one entry, that of "Allow Users Read".

(10) When you are sure, press "OK" button to return to the dialogue box of step (4). Press "OK" to return to the main window of Registry Editor. Close Registry Editor.

(11) Test to see if it works for you.

(12) To reverse the procedure (suppose you want integration back), right-click "LocalServer32", click "Permission..." and "Advanced". Remove the only entry in the box and then check the "Inherit from parent..." box. Click "OK" and "OK" to return to Registry Editor. Exit Registry Editor. Start Foxit to repair the "damage" automatically. Change EditFlag to suit your taste.

I hope this works now. Happy New Year.
Alvian.

[foxedifino]

Since all I get in firefox is a blank screen (unless I use the IE tab plugin)
I decided to disable it all together.

In firefox goto tools>options>content tab>manage button>
it pops up download actions screen.
Select line with pdf and hit the change action button.
Then select the new option you want.

Life is so much better now that pdf's dont open in the browser.

Don't know how to fix it in IE, but I dont use it except when I have to, and then I use the IE tab plugin

[scr621]

In the absence of a disable switch in Foxit, here is the next best thing: A registry hack. It worked for me using XPPro IE6-SP1 & Foxit 2.1.

(Note: The registry key is "FoxitReader.Document", all one word. There is a bug in the forum software that inserted a space between "Do" and "cument". Damn bugs everywhere!)

Disable browser integration (save PDF dialogue appears)
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00000002

Enable browser integration (read PDF in IE6)
------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00010000
Is there a registry hack for Foxit v2.2 Windows Vista (32 bit) please?

[scr621]

In the absence of a disable switch in Foxit, here is the next best thing: A registry hack. It worked for me using XPPro IE6-SP1 & Foxit 2.1.

(Note: The registry key is "FoxitReader.Document", all one word. There is a bug in the forum software that inserted a space between "Do" and "cument". Damn bugs everywhere!)

Disable browser integration (save PDF dialogue appears)
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00000002

Enable browser integration (read PDF in IE6)
------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00010000
Whoop de doo!
I copied the above registry details & ran it & guess what? It works for Foxit v2.2 Windows Vista 32 bit.....yay!

[scr621]

In the absence of a disable switch in Foxit, here is the next best thing: A registry hack. It worked for me using XPPro IE6-SP1 & Foxit 2.1.

(Note: The registry key is "FoxitReader.Document", all one word. There is a bug in the forum software that inserted a space between "Do" and "cument". Damn bugs everywhere!)

Disable browser integration (save PDF dialogue appears)
-----------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00000002

Enable browser integration (read PDF in IE6)
------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\FoxitReader.Do cument]
@="PDF Document"
"EditFlags"=dword:00010000
I take that back, it doesn't work for Windows Vista 32 bit.................boo hoo

[alvian]

I take that back, it doesn't work for Windows Vista 32 bit.................boo hoo

Firstly I do not have Vista and so if MS changed the definition of EditFlag in Vista then I cannot help you.

Secondly can you describe what happened after you incorporated the registry hack? Did the "Save File" dialog box appear when you clicked on a PDF link?

If you want the PDF to appear in a separate Foxit window then you need the advanced registry hack that appears on top of page 2 of this thread, titled "New solution to control browser integration". The basic registry hack alone only controls the appearance of the "Save File" dialog box. It was my mistake for publishing the basic hack (I misread what Hugo & Boz wanted), sorry.

Alvian.

[dwboston]

Also note my system configuration: WinXP Pro SP2, IE6 for XP, Foxit 2.2. I don't have XP Home and so I cannot verify my procedure works for it.

(1) Start Registry Editor under an Admin or Owner account.

(2) Set "EditFlag=2" as I described earlier.

(3) Go to "HKEY_CLASSES_ROOT\CLSID\{14E8BBD8-1D1C-4D56-A4DA-D20B75EB814E}\LocalServer32", double-click the "Default" icon, press "Delete key" to clear the value and click "OK" to confirm.

(4) Right-click the "LocalServer32" icon in the tree, select "Permissions..." Dialogue box opens.

(5) Click Advanced, another dialogue box opens.

(6) Clear the "Inherit from parent..." option box. Another dialogue box opens immediately.

(7) Click "Copy" and you are returned to the dialogue box in step (5).

(8) In the "Permission entries" box remove all entries EXCEPT for the "Allow - Users - Read" entry (should be the first entry). A quick way to do this is left-click the second entry, then Shift-Left-Click the last entry (i.e. left-click while holding the Shift key), and then click the "Remove" button.

(9) Check again. If you made a mistake then press "Cancel" or "Escape key" and repeat from step (5). You want only one entry, that of "Allow Users Read".

(10) When you are sure, press "OK" button to return to the dialogue box of step (4). Press "OK" to return to the main window of Registry Editor. Close Registry Editor.

(11) Test to see if it works for you.

(12) To reverse the procedure (suppose you want integration back), right-click "LocalServer32", click "Permission..." and "Advanced". Remove the only entry in the box and then check the "Inherit from parent..." box. Click "OK" and "OK" to return to Registry Editor. Exit Registry Editor. Start Foxit to repair the "damage" automatically. Change EditFlag to suit your taste.

I hope this works now. Happy New Year.
Alvian.
Woo-hoo! Works for me on XP Pro SP2, Maxthon 1.6/IE6. Thanks Alvian! :1_13:

And remember kids...

********************* ********************* ********************* ********************* ********************* *********************
Before you mess around with the registry, ALWAYS back up (export) the branch you're about to change, so if things go south you can easily restore (import) the original, clean configuration. This is SO IMPORTANT, YOU CAN'T IMAGINE!
********************* ********************* ********************* ********************* ********************* *********************

[Bernskov]

GeoffB, quite profession answer! :1_11:
Our design team will add an option to disable IE association later, then you will be able to view PDF outside the browser.

Whan are you going to make good on this?

[christina]

Sorry, Most probably you will see it on our next upgrade after 3.0. Thanks.

[Bernskov]

would it be possible to expose your release plan, so those of us that have features 'pending' could get a glimpse of what is expected and even more important - when.

Things like "open in native application" and a light version have been years in the making. Some kind of promise that FoxitSoftware sticks to would be highly appreaciated.

[christina]

would it be possible to expose your release plan, so those of us that have features 'pending' could get a glimpse of what is expected and even more important - when.

Thanks for pointing this out. But I don't think this is a feasible way since there are so many modifications.

Things like "open in native application" and a light version have been years in the making. Some kind of promise that FoxitSoftware sticks to would be highly appreaciated.

Sorry to have kept yours waiting so long. You know there are so many things need to be done. What I can say is to beg to be understood.

While those features mostly talked about will definitely call many attentions of our team. Please, just post within this forum to support and push forward the feature thread your desire, or write to our support email accout.