Microsoft KB Archive Search

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.

  1. Home
  2. Logon Windows 7 freezes when a GPO setting name contains two consecutive "%" characters

Logon Windows 7 freezes when a GPO setting name contains two consecutive "%" characters

View products that this article applies to.

Symptoms


Consider the following scenario:
  • You have a domain controller that runs Windows Server 2008 R2 and a Windows 7 client.
  • You create a test user and set the user’s home share to a network home share in user's properties.
  • You make the home share inaccessible, for example, stop the home share.
  • You create a new Group Policy Object (GPO), and link it to user’s Organizational Unit (OU). 
  • You edit the GPO for the "Folder" settings in Group Policy Preference (GPP), to set the path to "%HOMESHARE%%HOMEPATH%Outlook Personal Folders".
  • You disable the Fast Logon on the Windows 7 client.
  • You try to log on the client by using the test user.
In this scenario, the logon operation freezes.

↑ Back to the top

Resolution

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 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
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 Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix if w32tm.exe is running on the computer when you apply the 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
  • 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
    1.22xxx    		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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. 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.7601.22520590,33622-Nov-201309:36x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7601.22520790,52822-Nov-201310:01x64
Gpprefcl.dll6.1.7601.22520590,33622-Nov-201309:36x86
Gpprefcl.dll6.1.7601.22520590,33622-Nov-201309:36x86
For all supported IA64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Gpprefcl.dll6.1.7601.225201,522,17622-Nov-201309:10IA-64
Gpprefcl.dll6.1.7601.22520590,33622-Nov-201309:36x86

↑ 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 Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_2018cc6716d45caa18d9d10c6caf21c2_31bf3856ad364e35_6.1.7601.22520_none_6bea263dffc008a4.manifest
File versionNot applicable
File size711
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_39cb51e7c0677fc6.manifest
File versionNot applicable
File size53,968
Date (UTC)22-Nov-2013
Time (UTC)10:10
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File propertyValue
File nameAmd64_0e480e5bc8ba09c48a5d17b5e65a1630_31bf3856ad364e35_6.1.7601.22520_none_9dc84d2581e31742.manifest
File versionNot applicable
File size715
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_2018cc6716d45caa18d9d10c6caf21c2_31bf3856ad364e35_6.1.7601.22520_none_c808c1c1b81d79da.manifest
File versionNot applicable
File size713
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_619feb242c4a790e3002d54e7dfbd811_31bf3856ad364e35_6.1.7601.22520_none_9f34f7bd01a1bea3.manifest
File versionNot applicable
File size715
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_652e659fd8739fb7be8a12428d71a988_31bf3856ad364e35_6.1.7601.22520_none_c7db3e419fb82bb6.manifest
File versionNot applicable
File size1,070
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_95e9ed6b78c4f0fc.manifest
File versionNot applicable
File size53,972
Date (UTC)22-Nov-2013
Time (UTC)10:35
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameWow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_a03e97bdad25b2f7.manifest
File versionNot applicable
File size34,836
Date (UTC)22-Nov-2013
Time (UTC)09:52
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_39cb51e7c0677fc6.manifest
File versionNot applicable
File size53,968
Date (UTC)22-Nov-2013
Time (UTC)10:10
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported IA64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_c6d2e906b8192f9f653a15bc2348fb15_31bf3856ad364e35_6.1.7601.22520_none_1ae83d4cde601df2.manifest
File versionNot applicable
File size1,068
Date (UTC)22-Nov-2013
Time (UTC)13:34
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_39ccf5ddc06588c2.manifest
File versionNot applicable
File size53,970
Date (UTC)22-Nov-2013
Time (UTC)09:56
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22520_none_39cb51e7c0677fc6.manifest
File versionNot applicable
File size53,968
Date (UTC)22-Nov-2013
Time (UTC)10:10
SHA-1 hashNot applicable
MD5 hashNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2912760
Revision : 1
Created on : 1/7/2017
Published on : 3/11/2014
Exists online : False
Views : 187