For a month or two, my office Windows XP machine has been trouble, throwing virus-like errors in Explorer. A site would load but than instantly turn into an error page as IE shifted from the genuine URL to this f-ed up local URL: res://C:\WINDOWS\system32\shdoclc.dll/navcancl.htm.
It seemed to be random, because sometimes I could visit a bunch of different websites with no problem, but later I would try the same sites and get the error.
It also felt like the keyboard was slow. I would type at my normal blistering pace and every fourth letter would be dropped. I punched my PC's flatscreen twice for that. Dead on, fist into screen. It took both shots with no ill effect, so I have to give the Dell product top marks for that.
I tried Googling that bizarre res: string, but IE did the same FU trick on the Google results page, effectively blocking me out of teching my own problem. So I did my searching on my iMac... I don't know why I'm even bothering to use my PC's web browser, except when somebody at the office sends me an email with a link in it.
I found a lot of forum posts that warned of some sort of spyware. But nobody seemed to have a solution for the issue, aside from running anti-virus / anti-spyware and firewall stuff (of which my company has plenty. I can't even send out print ad files without gumming up my PC Outlook to hell.)
The laggy typing was making me paranoid that I had a keystroke-catcher on my hands, so I began to use the PC even less than usual. The situation floundered like that for weeks, with me occasionally forgetting that I had a problem, trying to use IE, and then getting frustrated all over again.
Today I took another stab at the Google search and found a forum post that, although rife with I'm New To The Internet spelling and typing, seemed to suggest a fix: WinsockXPFix.exe. So I Googled for that and downloaded it without care for company downloading policy. It has something to do with your TCP/IP stack Winsock whogivesashit getting boned somehow or other, and that little .exe file purports to repair it.
It didn't work, but at least it was an attempt.
Anyway, consider this my effort at stacking the web with another instance of this problem, so somebody in the future might come up with an answer to the "res://C:\WINDOWS\system32\shdoclc.dll/navcancl.htm" issue.
I'll be headed right back to my office iMac, thank you very much.