Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot start an application to open a file that has an associated file name extension after you specify the file association by using GPP in Window 7 or in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • On a computer that is running Windows Server 2008 R2 or Windows 7, you use Group Policy Management Console (GPMC) to manage a domain-based Group Policy object (GPO).
  • You create an Open With preference item under User Configuration\Preferences\Control Panel Settings\Folder Options to associate a file name extension with an application. You specify command line parameters to start the application. For example, you associate the .xnk file name extension with Outlook.exe, which is started with "C:\Program Files\Microsoft Office\OFFICE12\Outlook.exe" /x "%1".
  • You deploy the Group Policy preference to client computers.
  • You try to open a file that has the file name extension that is specified in the Group Policy preference.
In this scenario, you cannot open the file, and you receive an error message. For example, you receive the following error message when you try to open an .xnk file:
Cannot start Microsoft Office Outlook. The command line argument is not valid. Verify the switch you are using.
Note When you check the registry entries that are created by the Group Policy preference setting, you find incorrect values for the command line parameters that are used to start the application. For example, you locate the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.xnk\OpenWithList
You find that the value for the "a" registry entry is set to Outlook.exe\" /x \"%1\", which includes an additional double quotation mark (the first double quotation mark).

↑ Back to the top


Cause

The issue occurs because the Group Policy Management Editor cannot handle command line parameters correctly.

↑ Back to the top


Resolution

Note When you specify the Open With preference item, you must enclose the program path in quotation marks if you specify command line parameters to start the program. For example, you must input "C:\Program Files\Microsoft Office\OFFICE12\Outlook.exe" /x "%1" in Associated Program.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem that is described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 with Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 with Service Pack 1 (SP1)
Additionally, you must have Remote Server Administration Tools (RSAT) installed on the computer that is running Windows 7 or Windows 7 SP1.

Registry information

You do not have to make any changes to the registry to use this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system to which each hotfix applies.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.20881585,21615-Jan-201105:32x86
Gpprefcl.dll6.1.7601.21642585,21615-Jan-201105:33x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.20881785,92015-Jan-201106:18x64
Gpprefcl.dll6.1.7601.21642785,92015-Jan-201106:19x64
Gpprefcl.dll6.1.7600.20881585,21615-Jan-201105:32x86
Gpprefcl.dll6.1.7601.21642585,21615-Jan-201105:33x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7600.208811,504,25615-Jan-201105:11IA-64
Gpprefcl.dll6.1.7601.216421,505,28015-Jan-201105:09IA-64
Gpprefcl.dll6.1.7600.20881585,21615-Jan-201105:32x86
Gpprefcl.dll6.1.7601.21642585,21615-Jan-201105:33x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size2,350
Date (UTC)15-Jan-2011
Time (UTC)14:28
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_37a52e51c370b85d.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:08
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_39b7cb51c075cddc.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:06
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_93c3c9d57bce2993.manifest
File versionNot applicable
File size53,972
Date (UTC)15-Jan-2011
Time (UTC)07:01
PlatformNot applicable
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_95d666d578d33f12.manifest
File versionNot applicable
File size53,972
Date (UTC)15-Jan-2011
Time (UTC)07:03
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,633
Date (UTC)15-Jan-2011
Time (UTC)14:28
PlatformNot applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_9e187427b02eeb8e.manifest
File versionNot applicable
File size34,836
Date (UTC)15-Jan-2011
Time (UTC)06:00
PlatformNot applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_a02b1127ad34010d.manifest
File versionNot applicable
File size34,836
Date (UTC)15-Jan-2011
Time (UTC)05:59
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_37a52e51c370b85d.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:08
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_39b7cb51c075cddc.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:06
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_37a6d247c36ec159.manifest
File versionNot applicable
File size53,970
Date (UTC)15-Jan-2011
Time (UTC)06:51
PlatformNot applicable
File nameIa64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_39b96f47c073d6d8.manifest
File versionNot applicable
File size53,970
Date (UTC)15-Jan-2011
Time (UTC)06:59
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,183
Date (UTC)15-Jan-2011
Time (UTC)14:28
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7600.20881_none_37a52e51c370b85d.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:08
PlatformNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.21642_none_39b7cb51c075cddc.manifest
File versionNot applicable
File size53,968
Date (UTC)15-Jan-2011
Time (UTC)06:06
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2489291
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2011
Exists online : False
Views : 210