KB931768 "navcancl error" Workaround!

This workaround worked for me on a machine running XP SP2. My Temporary
Internet Files folder had been moved from the default location and IE7 would
not run after applying the KB931768 update. My workaround was as follows:

1) Uninstall the KB931768 update (or use System Restore to remove it).
2) Run Internet Explorer 7 and under "Tools - Internet Options - General ",
select "Browsing History - Settings"
3) Move the Temporary Internet Files folder to the default location.
In XP this seems to be "C:\Documents & Settings\username\Local Settings"
In Vista this seems to be "C:\Users\username\Local\Microsoft\Windows"
Here "username" is the account username (E.g. "Alan" in my case) and C: is
the drive on which Windows is installed.
4) Re-install the KB931768 update.
5) If you wish, you can now move the TIF folder by repeating step 2 then
specifying a new location of your choice.

This worked for me - I hope it works for you also (by the way, the Phishing
Filter was On throughout).

Thanks a lot. It worked for me.

It's a good thing that I have two computers networked together or I would
have had a hard time. I remember now that I had moved my temporary files to
another location. Thanks again.

Charlie

"AlanB" wrote:

> This workaround worked for me on a machine running XP SP2. My Temporary
> Internet Files folder had been moved from the default location and IE7 would
> not run after applying the KB931768 update. My workaround was as follows:
>
> 1) Uninstall the KB931768 update (or use System Restore to remove it).
> 2) Run Internet Explorer 7 and under "Tools - Internet Options - General ",
> select "Browsing History - Settings"
> 3) Move the Temporary Internet Files folder to the default location.
> In XP this seems to be "C:\Documents & Settings\username\Local Settings"
> In Vista this seems to be "C:\Users\username\Local\Microsoft\Windows"
> Here "username" is the account username (E.g. "Alan" in my case) and C: is
> the drive on which Windows is installed.
> 4) Re-install the KB931768 update.
> 5) If you wish, you can now move the TIF folder by repeating step 2 then
> specifying a new location of your choice.
>
> This worked for me - I hope it works for you also (by the way, the Phishing
> Filter was On throughout).

I now see I was not the first to suggest this workaround. However the means
by which you move the TIF folder (i.e. via Internet Options in IE or Control
Panel) may be important. My workaround has survived multiple subsequent
reboots and moving the TIF folder away from the default location and back to
where I wanted it.

"CharlieD" wrote:

> Thanks a lot. It worked for me.
>
> It's a good thing that I have two computers networked together or I would
> have had a hard time. I remember now that I had moved my temporary files to
> another location. Thanks again.
>
> Charlie
>
> "AlanB" wrote:
>
> > This workaround worked for me on a machine running XP SP2. My Temporary
> > Internet Files folder had been moved from the default location and IE7 would
> > not run after applying the KB931768 update. My workaround was as follows:
> >
> > 1) Uninstall the KB931768 update (or use System Restore to remove it).
> > 2) Run Internet Explorer 7 and under "Tools - Internet Options - General ",
> > select "Browsing History - Settings"
> > 3) Move the Temporary Internet Files folder to the default location.
> > In XP this seems to be "C:\Documents & Settings\username\Local Settings"
> > In Vista this seems to be "C:\Users\username\Local\Microsoft\Windows"
> > Here "username" is the account username (E.g. "Alan" in my case) and C: is
> > the drive on which Windows is installed.
> > 4) Re-install the KB931768 update.
> > 5) If you wish, you can now move the TIF folder by repeating step 2 then
> > specifying a new location of your choice.
> >
> > This worked for me - I hope it works for you also (by the way, the Phishing
> > Filter was On throughout).

A slightly differen workaround which also works: instead of uninstalling the
update, simply turn off the phishing filter before moving the Temporary
Internet Files folder. In my case, my TIF folder was already in the default
location, so I moved it to a non-default location. Evidently, just moving it
fixed the problem. After it's moved, you can turn the phishing back on.

-Bob


"AlanB" wrote:

> I now see I was not the first to suggest this workaround. However the means
> by which you move the TIF folder (i.e. via Internet Options in IE or Control
> Panel) may be important. My workaround has survived multiple subsequent
> reboots and moving the TIF folder away from the default location and back to
> where I wanted it.
>
> "CharlieD" wrote:
>
> > Thanks a lot. It worked for me.
> >
> > It's a good thing that I have two computers networked together or I would
> > have had a hard time. I remember now that I had moved my temporary files to
> > another location. Thanks again.
> >
> > Charlie
> >
> > "AlanB" wrote:
> >
> > > This workaround worked for me on a machine running XP SP2. My Temporary
> > > Internet Files folder had been moved from the default location and IE7 would
> > > not run after applying the KB931768 update. My workaround was as follows:
> > >
> > > 1) Uninstall the KB931768 update (or use System Restore to remove it).
> > > 2) Run Internet Explorer 7 and under "Tools - Internet Options - General ",
> > > select "Browsing History - Settings"
> > > 3) Move the Temporary Internet Files folder to the default location.
> > > In XP this seems to be "C:\Documents & Settings\username\Local Settings"
> > > In Vista this seems to be "C:\Users\username\Local\Microsoft\Windows"
> > > Here "username" is the account username (E.g. "Alan" in my case) and C: is
> > > the drive on which Windows is installed.
> > > 4) Re-install the KB931768 update.
> > > 5) If you wish, you can now move the TIF folder by repeating step 2 then
> > > specifying a new location of your choice.
> > >
> > > This worked for me - I hope it works for you also (by the way, the Phishing
> > > Filter was On throughout).

It is now July 9. Is there a permanent and definitive fix for the "navcancl
error" problem?
--