Da du ikke kan åbne et link kopier jeg det hele herind, der er mange der har problemet, men kan løses ved dette her:
You Cannot Open New Internet Explorer Window or Nothing Happens After You Click a Link
Gælder for
This article was previously published under Q281679
SYMPTOMS
When you click a hyperlink in an e-mail message or on a Web page, or right-click a hyperlink on a Web page and then click Open in New Window, you may experience one or more of the following symptoms:
Nothing happens.
The new window may be blank.
You may receive a scripting error message.
When you use the Print command or the Print Preview command in Internet Explorer, nothing may happen.
When you try to connect to Web folders, you may receive the following error message:
The current operation could not be completed because an unexpected error has occurred.
CAUSE
This behavior may occur for any of the following reasons:
The (Default) value setting in one or more of the following registry keys points to an incorrect location for the Urlmon.dll file:
[HKEY_CLASSES_ROOT\CLSID\{79eac9e0-baf9-11ce-8c82-00aa004ba90b}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{79eac9f1-baf9-11ce-8c82-00aa004ba90b}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{79eac9f2-baf9-11ce-8c82-00aa004ba90b}\InprocServer32]
This may occur if you install a customized version of Internet Explorer that was created with the Internet Explorer Administration Kit (IEAK) version 5.01 Service Pack 1 (SP1), 5.5 SP1, or 6.0.
The following registry key is missing or damaged:
HKLM\SOFTWARE\Classes\Interface\{00020400-0000-0000-C000-000000000046}
One or more of the following files is missing, damaged, or improperly registered:
Url.dll
Mshtml.dll
Actxprxy.dll
Oleaut32.dll
Shell32.dll
Shdocvw.dll
RESOLUTION
To resolve this problem in Internet Explorer, follow these steps:
Quit all programs that are running.
Click Start, and then click Run.
Type regsvr32 urlmon.dll, and then click OK.
When you receive the "DllRegisterServer in urlmon.dll succeeded" message, click OK.
If this does not resolve the problem, repeat steps 2 through 4 for each of the following files (in step 3, replace Urlmon.dll with each of the file names below):
Shdocvw.dll
Msjava.dll
Actxprxy.dll
Oleaut32.dll
Mshtml.dll
Browseui.dll
Shell32.dll (Windows XP and Windows 2000 only)
If the problem is still not resolved, verify that the following registry values are present and correct:
HKLM\SOFTWARE\Classes\Interface\{00020400-0000-0000-C000-000000000046}
Name: (Default)
Value: IDispatch
HKLM\SOFTWARE\Classes\Interface\{00020400-0000-0000-C000-000000000046}\ProxyStubClsid
Name: (Default)
Value: {00020420-0000-0000-C000-000000000046}
HKLM\SOFTWARE\Classes\Interface\{00020400-0000-0000-C000-000000000046}\ProxyStubClsid32
Name: (Default)
Value: {00020420-0000-0000-C000-000000000046}
If the problem is still not resolved, reinstall Internet Explorer. If you are using the version of Internet Explorer that is included with your operating system, reinstall or repair your operating system.
Internet Explorer Administration Kit Users
If this problem occurs after you install a customized version of Internet Explorer that was created with the Internet Explorer Administration Kit (IEAK) version 5.01 Service Pack 1 (SP1), 5.5 SP1, or 6.0 and is resolved by re-registering the Urlmon.dll file, contact Microsoft Product Support Services to obtain the appropriate fix below.
IEAK for Internet Explorer 6
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
------------------------------------------------------
11-Oct-2001 19:45 6.0.2710.1100 189,440 Ie6wzd.exe
Note This hotfix is not distributed by using a hotfix installer package but is an actual binary hotfix that you must manually replace. To do this, rename the old Ie6wzd.exe file in your IEAK installation folder\Iebin\Optional\EN folder, manually copy the hotfix into that folder, and then rebuild your IEAK package to have the hotfix included inside your package.
Important If Automatic Version Synchronization (AVS) is applied to your IEAK installation after you use this fix, you must manually apply this hotfix again.
IEAK for Internet Explorer 5.5
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
18-Dec-2000 17:22 5.50.4612.1800 183,056 Ie5wzd.exe
Note This hotfix is not distributed by using a hotfix installer package, but is an actual binary hotfix that you must manually replace. To do this, rename the old Ie5wzd.exe file in your IEAK installation folder\Iebin\Optional\EN folder, manually copy the hotfix into that folder, and then rebuild your IEAK package to have the hotfix included inside your package.
Important If Automatic Version Synchronization (AVS) is applied to your IEAK installation after you use this fix, you must manually apply this hotfix again.
IEAK for Internet Explorer 5.01
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
---------------------------------------------------------
01-Nov-2000 11:01a 5.0.3210.3100 177,424 Ie5wzd.exe
Note This hotfix is not distributed by using a hotfix installer package, but is an actual binary hotfix that you must manually replace. To do this, rename the old Ie5wzd.exe file in your IEAK installation folder\Iebin\Optional\EN folder, manually copy the hotfix into that folder, and then rebuild your IEAK package to have the hotfix included inside your package.
Important If Automatic Version Synchronization (AVS) is applied to your IEAK installation after you use this fix, you must manually apply this hotfix again.