Navcancl / ieframe.dll - Solution

Problem solved!

I've solved this problem by restoring the temporary internet files folder
the default folder. I changed the TIF folder for some reasons, but now I
have to chage it back to solve this problem. The default folder in Vista
should be like:
C:\Users\%YOUR_USER_NAME%\AppData\Local\Microsoft\ Windows\Temporary Internet
Files

In my case, I don't need to chage the phishing filter any more. Everything
is working just fine!

"Marshall Kiam-Laine" wrote:

> Problem : ie7 refuses to open
> after Installing update KB 931768
>
> Solution : find C:\program files\ iexplore.exe
> right click and "Run as administrator"
> After ie7 has opened :
> Tools\options\Advanced - Disable Pfishing.
>
> should be ok now - but of course be extra Alert for
> any Fishing emails.
>
>
> ----------------------------------------------------
>

> How about this for a solution. Use Firefox.

Wouldn't that just be another workaround?

--

Ronnie Vernon
Microsoft MVP
Windows Shell/User


"Feliks Dzerzhinsky" <fdzerzhinsky@kgb.su> wrote in message
news:e69dX%238kHHA.4684@TK2MSFTNGP03.phx.gbl...

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Marshall Kiam-Laine wrote:

>> Problem : ie7 refuses to open after Installing update
>> KB 931768
>>
>> Solution : find C:\program files\ iexplore.exe
>> right click and "Run as administrator"
>> After ie7 has opened : Tools\options\Advanced - Disable
>> Pfishing.
>>
>> should be ok now - but of course be extra Alert for any Fishing emails.
>>
>>
>> ----------------------------------------------------

> That is not a solution. It is only a workaround. The solution is for
> MS to fix the %$#@! thing.
>
> BTW, the IE7 phishing filter has nothing to do with email...only sites.
>
> How about this for a solution. Use Firefox.
>
> - --
> Iron Feliks
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGRG5GIEgejQPpTu4RCiQiAJ4td2Qf+opXQotsekUIeH i9QLMSvACgq3u/
> r4JJZFG2HyCOVZtqmmA5AbE=
> =44LY
> -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ronnie Vernon MVP wrote:

>> How about this for a solution. Use Firefox.

>
> Wouldn't that just be another workaround?
>

True, but it got your attention. :-)

- --
Iron Feliks
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGRKfsIEgejQPpTu4RCk3FAKCYauoLHPlHiZ4y5VYusR oJqRpxFACdEDSD
uy37XHLnim7zmJe7AIwzpts=
=9k4/
-----END PGP SIGNATURE-----

On Fri, 11 May 2007 06:28:01 -0700, tony wrote:

> Problem solved!
>
> I've solved this problem by restoring the temporary internet files folder
> the default folder. I changed the TIF folder for some reasons, but now I
> have to chage it back to solve this problem. The default folder in Vista
> should be like:
> C:\Users\%YOUR_USER_NAME%\AppData\Local\Microsoft\ Windows\Temporary Internet
> Files
>
> In my case, I don't need to chage the phishing filter any more. Everything
> is working just fine!

I wonder if you would be able to move it again now if this would stay
working? Sometimes reverting to default settings to "re-unites" the
troubled piece of the puzzle and then it once again behaves as expected.

On the other hand, staying at the default setting is good prevention
against a future update assuming a defined path for a user configurable
item.

It would be interesting to know if you don't mind shifting these around a
bit. If you would rather not, that's understandable too...

--
Sharon F
MS-MVP ~ Windows Shell/User

I've tried it and, with no luck, it happened again. If you change the default
TIF folder, the problem will come back again.

"Sharon F" wrote:

> On Fri, 11 May 2007 06:28:01 -0700, tony wrote:
>

> > Problem solved!
> >
> > I've solved this problem by restoring the temporary internet files folder
> > the default folder. I changed the TIF folder for some reasons, but now I
> > have to chage it back to solve this problem. The default folder in Vista
> > should be like:
> > C:\Users\%YOUR_USER_NAME%\AppData\Local\Microsoft\ Windows\Temporary Internet
> > Files
> >
> > In my case, I don't need to chage the phishing filter any more. Everything
> > is working just fine!

>
> I wonder if you would be able to move it again now if this would stay
> working? Sometimes reverting to default settings to "re-unites" the
> troubled piece of the puzzle and then it once again behaves as expected.
>
> On the other hand, staying at the default setting is good prevention
> against a future update assuming a defined path for a user configurable
> item.
>
> It would be interesting to know if you don't mind shifting these around a
> bit. If you would rather not, that's understandable too...
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User
>

On Fri, 11 May 2007 16:38:01 -0700, tony wrote:

> I've tried it and, with no luck, it happened again. If you change the default
> TIF folder, the problem will come back again.

Thanks, Tony. Appreciate your taking the time to find out if this would
work or not.

--
Sharon F
MS-MVP ~ Windows Shell/User

Well, that's ridiculous.
People with roaming profiles hate TIF in the profile dir.
They should be able to change this option.

I had the same problem. Seems TIF change is bad.

Hmmm..Firefox, eh? It's also got that nice HTML snippet viewer feature...!
If only MS would analyze their competitors before planning development!
(Frontpage/Expression vs. Dreamweaver, VS.NET vs Eclipse, IE vs.
Firefox...oh well, maybe someday...)


"Sharon F" wrote:

> On Fri, 11 May 2007 16:38:01 -0700, tony wrote:
>

> > I've tried it and, with no luck, it happened again. If you change the default
> > TIF folder, the problem will come back again.

>
> Thanks, Tony. Appreciate your taking the time to find out if this would
> work or not.
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User
>

On Fri, 1 Jun 2007 12:00:00 -0700, WaterMoccasin wrote:

> Well, that's ridiculous.
> People with roaming profiles hate TIF in the profile dir.
> They should be able to change this option.

I agree with you. The option to change location is available within the UI.
It shouldn't be a surprise that some folks move it. IMO, an update should
not break this. It should check the current value of this variable instead
of assuming the cache is still at the default location.

--
Sharon F
MS-MVP ~ Windows Shell/User