Windows Vista: “Unable to cast object of type ‘System.String’ to type ‘Microsoft.Group.Policy.Reporting.Extensions.Registry.RegistryValue’.” error message when you try to generate a report for a GPO

SUPPORT SOLUTION:
Consider the following scenario:You have a computer that is running one of the following operating systems: Windows VistaWindows Server 2008 Windows 7Windows Server 2008 R2You use the Group Policy Management Console (GPMC) to connect to a domain controller from the computer.You select a Group Policy object (GPO), and then you disable the Windows Firewall: Allow Logging Group Policy setting in the following path: Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall\Domain ProfileYou try to generate a report for the GPO in GPMC. In this scenario, you receive the following error message:An error occurred while generating report: Unable to cast object of type ‘System.String’ to type ‘Microsoft.Group.Policy.Reporting.Extensions.Registry.RegistryValue’. Note You can use either of the following methods to generate a report for a GPO in the GPMC MMC snap-in:Method 1: Select the Group Policy object, and then click the Settings tab in the panel on the right side. Method 2: Run the Group Policy Results Wizard. The issue occurs because the GPMC treats the Group Policy-related registry value as a string. This causes an unhandled invalid cast exception during type cast conversion when GPMC is generating the GPO report. Hotfix information
2, ‘resolution’);
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 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: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) 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
3, ‘resolution’);
To apply this hotfix, you must be running one of the following operating systems:Windows Vista Service Pack 2 (SP2)Windows Server 2008 Service Pack 2 (SP2)Windows 7 Windows Server 2008 R2Additionally, you must have Remote Server Administration Tools (RSAT) installed on the computer that is running Windows Vista or Windows 7. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base: 935791  (http://support.microsoft.com/kb/935791/ ) How to obtain the latest Windows Vista service pack For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base: 968849  (http://support.microsoft.com/kb/968849/ ) How to obtain the latest service pack for Windows Server 2008 Registry information
3, ‘resolution’);
To use the hotfix in this package, you do not have to make any changes to the registry.Restart requirement
3, ‘resolution’);
You do not have to restart the computer after you apply this hotfix.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace a previously released hotfix.File information
3, ‘resolution’);
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 Vista and Windows Server 2008 file information notes
4, ‘resolution’);
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only “Windows Vista” is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows Vista” on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to. The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.Collapse this tableExpand this table VersionProductSR_LevelService branch 6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDRThe 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 and for Windows Vista” section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain 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 Server 2008 and of Windows Vista
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.serveradmintools.reporting.dll6.0.6002.226051,654,78410-Mar-201108:52×86Microsoft.grouppolicy.serveradmintools.interop.dll6.0.6002.22605142,84810-Mar-201108:52×86For all supported x64-based versions of Windows Server 2008 and of Windows Vista
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.serveradmintools.interop.dll6.0.6002.22605148,48010-Mar-201108:49×64Microsoft.grouppolicy.serveradmintools.reporting.dll6.0.6002.226051,654,78410-Mar-201108:49×86Microsoft.grouppolicy.serveradmintools.interop.dll6.0.6002.22605142,84810-Mar-201108:49×86For all supported IA-64-based versions of Windows Server 2008
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.serveradmintools.interop.dll6.0.6002.22605163,32810-Mar-201108:45IA-64Microsoft.grouppolicy.serveradmintools.reporting.dll6.0.6002.226051,654,78410-Mar-201108:45×86Microsoft.grouppolicy.serveradmintools.interop.dll6.0.6002.22605142,84810-Mar-201108:45×86Windows 7 and Windows Server 2008 R2 file information notes
4, ‘resolution’);
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 that each hotfix applies to.The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.Collapse this tableExpand this table VersionProductSR_LevelService branch 6.1.760 0 . 20xxxWindows 7 and Windows Server 2008 R2RTMLDRThe 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 extremely important to maintain 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
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.reporting.dll6.1.7600.207971,851,39210-Sep-201004:46×86For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.reporting.dll6.1.7600.207971,851,39210-Sep-201004:46×86For all supported IA-64-based versions of Windows Server 2008 R2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformMicrosoft.grouppolicy.reporting.dll6.1.7600.207971,851,39210-Sep-201004:46×86 Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates Additional file information
2,
Additional file information for Windows Vista and for Windows Server 2008
3,
Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
4,
Collapse this tableExpand this tableFile nameMsil_microsoft.grouppoli..dmintools.reporting_31bf3856ad364e35_6.0.6002.22605_none_2d9b6092a1038691.manifestFile versionNot ApplicableFile size5,196Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size2,253Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameX86_microsoft.grouppoli..radmintools.interop_31bf3856ad364e35_6.0.6002.22605_none_e070888e28472319.manifestFile versionNot ApplicableFile size7,758Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableAdditional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
4,
Collapse this tableExpand this tableFile nameAmd64_microsoft.grouppoli..radmintools.interop_31bf3856ad364e35_6.0.6002.22605_none_3c8f2411e0a4944f.manifestFile versionNot ApplicableFile size7,786Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameMsil_microsoft.grouppoli..dmintools.reporting_31bf3856ad364e35_6.0.6002.22605_none_2d9b6092a1038691.manifestFile versionNot ApplicableFile size5,196Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size2,269Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameX86_microsoft.grouppoli..radmintools.interop_31bf3856ad364e35_6.0.6002.22605_none_e070888e28472319.manifestFile versionNot ApplicableFile size7,758Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableAdditional files for all supported IA-64-based versions of Windows Server 2008
4,
Collapse this tableExpand this tableFile nameIa64_microsoft.grouppoli..radmintools.interop_31bf3856ad364e35_6.0.6002.22605_none_e0722c8428452c15.manifestFile versionNot ApplicableFile size7,772Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameMsil_microsoft.grouppoli..dmintools.reporting_31bf3856ad364e35_6.0.6002.22605_none_2d9b6092a1038691.manifestFile versionNot ApplicableFile size5,196Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size1,585Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableFile nameX86_microsoft.grouppoli..radmintools.interop_31bf3856ad364e35_6.0.6002.22605_none_e070888e28472319.manifestFile versionNot ApplicableFile size7,758Date (UTC)10-Mar-2011Time (UTC)09:01PlatformNot ApplicableAdditional file information for Windows 7 and for Windows Server 2008 R2
3,
Additional files for all supported x86-based versions of Windows 7
4,
Collapse this tableExpand this tableFile nameMsil_microsoft.grouppolicy.reporting_31bf3856ad364e35_6.1.7600.20797_none_4a6438e5259bc7da.manifestFile versionNot ApplicableFile size2,860Date (UTC)10-Sep-2010Time (UTC)05:03PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size1,653Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot ApplicableFile nameX86_eadd938e7b841a7c626889d595543c85_31bf3856ad364e35_6.1.7600.20797_none_c883825b61bf9880.manifestFile versionNot ApplicableFile size702Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot ApplicableAdditional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
4,
Collapse this tableExpand this tableFile nameAmd64_eadd938e7b841a7c626889d595543c85_31bf3856ad364e35_6.1.7600.20797_none_24a21ddf1a1d09b6.manifestFile versionNot ApplicableFile size704Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot ApplicableFile nameMsil_microsoft.grouppolicy.reporting_31bf3856ad364e35_6.1.7600.20797_none_4a6438e5259bc7da.manifestFile versionNot ApplicableFile size2,860Date (UTC)10-Sep-2010Time (UTC)05:03PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size1,663Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot ApplicableAdditional files for all supported IA-64-based versions of Windows Server 2008 R2
4,
Collapse this tableExpand this tableFile nameIa64_eadd938e7b841a7c626889d595543c85_31bf3856ad364e35_6.1.7600.20797_none_c885265161bda17c.manifestFile versionNot ApplicableFile size703Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot ApplicableFile nameMsil_microsoft.grouppolicy.reporting_31bf3856ad364e35_6.1.7600.20797_none_4a6438e5259bc7da.manifestFile versionNot ApplicableFile size2,860Date (UTC)10-Sep-2010Time (UTC)05:03PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size1,460Date (UTC)10-Sep-2010Time (UTC)08:00PlatformNot Applicable