You are unable to update the target location of offline file shares in the Offline File client side cache without administrative permission in Windows Server 2008 R2 or in Windows 7

Symptoms

Consider the following scenario:

Scenario 1

  • The Folder Redirection feature is enabled for the user to redirect his/her documents to a file server.

  • You enable the Offline Files feature on a computer that is running Windows Server 2008 R2 or Windows 7.

  • You change the destination file server location for the user’s redirected documents to a new location. Or if the new file server location represents a different physical storage location, you move the user’s data from the old file server location to the new file server location.

    Note This would be the case if the redirected documents location is changing because a file server is now to be access through a different DFS name.

  • When the updated Folder Redirection policy applies to the user’s computer, you want the data that is already in the Offline Files cache to be renamed to reflect the new file server name without transferring the data from the old server location to the new server location through the client.

In this scenario, you cannot guarantee the sequence of the Folder Redirection policy update and a script running to rename the items in the Offline Files cache will guarantee that the user’s configuration is updated correctly without generated unnecessary network traffic. Also, if the user does not have administrative credentials, renaming items in the Offline Files cache is not allowed. However, in Windows XP this can be done for users without administrative credentials.

Scenario 2

  • You pin some file server content into the Offline Files cache for users through a logon script or Offline Files Group Policy on a computer that is running Windows Server 2008 R2 or Windows 7.

  • The content is moving to a different file server or a different DFS location.Therefore the content will be available through a new name.

  • You want the user to continue to caching the data without requiring the data to be re-cached from the new server location.

In this scenario, you cannot script the rename of the content in the Offline Files cache if the user does not have administrative credentials on the computer and this action will require a restart of the client computer to take effect. However, in Windows XP a script running in as non-administrative user could do this without requiring a computer restart.

Resolution

To resolve this problem, install the following hotfix on the affected computer. After you install the hotfix, you can update the shared folder record in the CSC cache without administrative credentials.

Note: Although this hotfix is included in Windows Server 2008 R2 and Windows 7 SP1 you will need to add the registry to enable the functionality. Further will you need to install below additional hotfix to make the RenameItemEx method available in SP1:

2610379 The Folder Redirection policy does not work if a previous user sets a redirected folder to an offline mode in Windows 7 or in Windows Server 2008 R2

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 Web site:

http://support.microsoft.com/contactus/?ws=supportNote 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 or Windows Server 2008 R2.

Registry information

Notes

  • If you use the Folder Redirection feature, you are must create the following registry key for the hotfix to take effect.

  • For traditional share folders, you can use a login script. The login script uses the RenameItemEx method of the Win32_OfflineFilesCache Class. For more information about the Win32_OfflineFilesCache class , visit the following Web site:http://msdn.microsoft.com/en-us/library/bb309182(VS.85).aspx

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in WindowsTo use the hotfix in this package, you must create a registry key. To do this, follow these steps:

  1. In Registry Editor, locate the following registry subkey:



    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer

  2. Under the Explorer registry subkey, click Edit, click New, click DWORD Value, type FolderRedirectionEnableCacheRename, and then press ENTER.

  3. Set the decimal value of the FolderRedirectionEnableCacheRename registry entry to 1.

  4. Exit Registry Editor.

Restart requirement

You must 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 that each hotfix applies to.

  • 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 extremely 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 name

File version

File size

Date

Time

Platform

Cscapi.dll

6.1.7600.20641

34,816

11-Feb-2010

06:54

x86

Cscdll.dll

6.1.7600.20641

23,040

11-Feb-2010

06:54

x86

Cscobj.dll

6.1.7600.20641

138,752

11-Feb-2010

06:54

x86

Offlinefileswmiprovider.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Offlinefileswmiprovider_uninstall.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Csc.sys

6.1.7600.20641

387,584

11-Feb-2010

03:17

x86

Cscmig.dll

6.1.7600.20641

109,568

11-Feb-2010

06:54

x86

Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms

Not Applicable

3,144

11-Feb-2010

07:04

Not Applicable

Cscsvc.dll

6.1.7600.20641

546,304

11-Feb-2010

06:54

x86

Microsoft-windows-offlinefiles.mof

Not Applicable

1,776

13-Jul-2009

20:25

Not Applicable

Apps.inf

Not Applicable

62,334

11-Feb-2010

03:10

Not Applicable

Shell32.dll

6.1.7600.20641

12,868,096

11-Feb-2010

06:54

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Cscapi.dll

6.1.7600.20641

46,080

11-Feb-2010

07:35

x64

Cscdll.dll

6.1.7600.20641

30,208

11-Feb-2010

07:35

x64

Cscobj.dll

6.1.7600.20641

240,128

11-Feb-2010

07:35

x64

Offlinefileswmiprovider.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Offlinefileswmiprovider_uninstall.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Csc.sys

6.1.7600.20641

514,048

11-Feb-2010

03:29

x64

Cscmig.dll

6.1.7600.20641

137,216

11-Feb-2010

07:35

x64

Microsoft-windows-offlinefiles-core-ppdlic.xrm-ms

Not Applicable

3,144

11-Feb-2010

07:49

Not Applicable

Cscsvc.dll

6.1.7600.20641

692,224

11-Feb-2010

07:35

x64

Microsoft-windows-offlinefiles.mof

Not Applicable

1,776

13-Jul-2009

20:20

Not Applicable

Apps.inf

Not Applicable

62,334

11-Feb-2010

03:20

Not Applicable

Shell32.dll

6.1.7600.20641

14,164,992

11-Feb-2010

07:41

x64

Cscobj.dll

6.1.7600.20641

138,752

11-Feb-2010

06:54

x86

Offlinefileswmiprovider.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Offlinefileswmiprovider_uninstall.mof

Not Applicable

14,568

10-Feb-2010

23:45

Not Applicable

Shell32.dll

6.1.7600.20641

12,868,096

11-Feb-2010

06:54

x86

Cscapi.dll

6.1.7600.20641

34,816

11-Feb-2010

06:54

x86

Cscdll.dll

6.1.7600.20641

23,040

11-Feb-2010

06:54

x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Cscapi.dll

6.1.7600.20636

91,136

05-Feb-2010

06:18

IA-64

Cscdll.dll

6.1.7600.20636

68,608

05-Feb-2010

06:18

IA-64

Apps.inf

Not Applicable

62,334

05-Feb-2010

02:45

Not Applicable

Shell32.dll

6.1.7600.20636

21,173,760

05-Feb-2010

06:24

IA-64

Shell32.dll

6.1.7600.20636

12,868,096

05-Feb-2010

07:04

x86

Cscapi.dll

6.1.7600.20636

34,816

05-Feb-2010

07:04

x86

Cscdll.dll

6.1.7600.20636

23,040

05-Feb-2010

07:04

x86

Status

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

More Information

For more information about how to configure the computer after you install the hotfix, follow these steps to achieve the desired behavior described above by scenario 1:

  1. Set the registry key that is described in the "Registry information" part of the Resolution section.


    Note This registry entry is set per user, therefore if multiple users use a given client computer, this registry setting should be set for any user whose cached content is going to be moved.

  2. Log off the computers that access the share folder that is going to be moved or remove the share folder from the source server. This ensures that the share folder cannot be accessed. This step also ensures that the content on the server can be successfully moved without an error message that the files are in use.

  3. Backup the content from the source server and restore the content to the target server. The data must be moved in a manner that will preserve file attributes, timestamps and security access. If possible, the old target shared folder should be unshared on the server to prevent the user from synchronizing data changes back to the old location after the data has been moved to the new file server.

    Note Moving the data by using a backup application should be sufficient to preserve this file state. However, using a simple copy utility, such as xcopy, will not preserve the file state correctly.

  4. Update the Folder Redirection configuration to reflect the target server. For example, if you redirecting to the user’s home directory, the target server should be of the format %HOMESHARE%%HOMEPATH%. Make sure to have the "Move the contents of Documents to the new location" option checked in the Folder Redirection configuration.


    Note You can perform the configuration of the Folder Redirection Group Policy setting through the following path:


    User Configuration\Policies\Windows Settings\Folder Redirection\Documents\Properties

  5. Log on to the computer to receive the updated Group Policy settings. This may require the you to log on, log off, and then log on again because the Group Policy settings can be applied asynchronously to the user’s logon.

When the user’s updated Folder Redirection group policy settings are applied, the appropriate content will also have been renamed in the Offline Files cache. Any modifications that were only in the client’s cache will be preserved and synchronized to the new server location when the client performs the first synchronization.

For more information about how to configure the computer after you install the hotfix, follow these steps to achieve the desired behavior described above by scenario 2:

  1. Log off the computers that access the share folder that is going to be moved or remove the share folder from the source server. This ensures that the shared folder cannot be accessed. This step also ensures that the content on the server can be successfully moved without an error message that the files are in use.

  2. Backup the content from the source server and restore the content to the target server. The data must be moved in a manner that will preserve file attributes, timestamps and security access. If possible, the old target shared folder should be unshared on the server to prevent the user from synchronizing data changes back to the old location after the data has been moved to the new file server.

    Note Moving the data by using a backup application should be sufficient to preserve this file state. However, using a simple copy utility, such as xcopy, will not preserve the file state correctly.

  3. Run a script that calls the RenameItemEx method of the Win32_OfflineFilesCache Class to rename the cached content from the old name to the new name. If this call fails, some content is in use in the cache so it cannot be renamed at this time. The script can then call the RenameItem method of the Win32_OfflineFilesCache Class to schedule a rename of this content in the cache on the next restart.

If a user’s home directory is being moved in this way, please see the following sample script provided to ensure all content is renamed correctly: '
' THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF
' ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO
' THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
' PARTICULAR PURPOSE.
'
' Copyright (c) Microsoft Corporation. All rights reserved.
'
'
' Usage: CscRename.vbs /OldItemPath:<path> /NewItemPath:<path> [/Machine:value] [/User:value] [/Password:value]
'
'
' Demonstrates how to rename an item in the Ofline Files cache.
'
' OldItemPath - UNC path of the current path to be renamed.
'
' NewItemPath - UNC path of the new path to replace the old path.
'
' If NewItemPath already exists, the operation is not performed.
' This operation simply schedules a rename to be performed on the next restart
' of the system.
'
const cComputerName = "LocalHost"
const cWMINamespace = "root\cimv2"
const cWMIClass = "Win32_OfflineFilesCache"
Const wbemFlagReturnImmediately = &h10

nRenameItemExFailureCount = 0
nRenameItemFailureCount = 0

'
' Process commandline arguments
'
strOldItemPath = WScript.Arguments.Named("OldItemPath")'
if Len(strOldItemPath) = 0 Then
Wscript.Echo "OldItemPath parameter required"
Err.Raise 449 ' "argument not optional" error
End if

strNewItemPath = WScript.Arguments.Named("NewItemPath")
if Len(strNewItemPath) = 0 Then
Wscript.Echo "NewItemPath parameter required"
Err.Raise 449 ' "argument not optional" error
End if

strComputerName = WScript.Arguments.Named("Machine")
If Len(strComputerName) = 0 Then strComputerName = cComputerName

strUserID = WScript.Arguments.Named("User")
If Len(strUserID) = 0 Then strUserID = ""

strPassword = WScript.Arguments.Named("Password")
If Len(strPassword) = 0 Then strPassword = ""

set objWMILocator = WScript.CreateObject("WbemScripting.SWbemLocator")

Set objWMIServices = objWMILocator.ConnectServer(strComputerName, _
cWMINameSpace, _
strUserID, _
strPassword)

'
' Note that Win32_OfflineFilesCache is a singleton.
'

strTempOldItemPath = Replace(strOldItemPath,"\","\\")

Set objWMIService = GetObject("winmgmts:\\" & cComputerName & "\root\CIMV2")
Set objCache = objWMIServices.Get("Win32_OfflineFilesCache=@")

'
'Find the path of the item to be renamed in the cache
'
Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_OfflineFilesItem WHERE ItemPath ='" &strTempOldItemPath&"'", "WQL", _
wbemFlagReturnImmediately + wbemFlagForwardOnly)

For Each objItem In colItems

'
'If folder is pinned we need to rename all the directory items underneath this
'
If (objItem.PinInfo.Pinned = True) Then
'
'Find all the directories underneath the folder in the cache
'
Set childItems = objWMIService.ExecQuery("SELECT * FROM Win32_OfflineFilesItem WHERE ParentItemPath = '" &strTempOldItemPath&"'", "WQL", _
wbemFlagForwardOnly + wbemFlagReturnImmediately )

For Each childItem In childItems

strOldPath = childItem.ItemPath
'
'Item to be renamed in the cache
'
strTempNewItemPath = strNewItemPath & "\" & childItem.ItemName

On Error Resume Next
'
' Note that while we pass "False" for the bReplace parameter, that
' parameter is ignored. Existing destinations are never replaced, regardless
' of what we pass for the 3rd parameter.
'
objCache.RenameItemEx strOldPath, strTempNewItemPath, False
hr = Hex(Err.Number)
If Err.Number <> 0 Then
WScript.Echo "RenameItem Failed with error:" &hr
WScript.Echo "While renaming:" & strOldPath & " to:" &strTempNewItemPath
Err.Clear
nRenameItemExFailureCount = nRenameItemExFailureCount + 1
On Error Resume Next
'
'We got the error in renaming this may happen due to item in use, try to renaname after reboot
'
objCache.RenameItem strOldPath, strNewItemPath, False
hr = Hex(Err.Number)
If Err.Number <> 0 Then
WScript.Echo "RenameItem Failed with error:" &hr
WScript.Echo " While renaming:" & strOldPath & " to:" &strTempNewItemPath
Err.Clear
nRenameItemFailureCount = nRenameItemFailureCount + 1
Else
WScript.Echo "item rename scheduled. A restart of the system is necessary to apply the change."
End If
Else
WScript.Echo "Renamed:" &strOldPath & " to:" &strTempNewItemPath & " SUCCESSFULLY"

End If
Next
Else
'
'Find all the directory items underneath the folder in the cache
'
Set childItems = objWMIService.ExecQuery("SELECT * FROM Win32_OfflineFilesItem WHERE ParentItemPath = '" &strTempOldItemPath&"'", "WQL", _
wbemFlagForwardOnly + wbemFlagReturnImmediately )

For Each childItem In childItems

'
'If this item is pinned and a directory, rename it
'
If (childItem.PinInfo.Pinned = True) Then
strOldPath = childItem.ItemPath
strTempNewItemPath = strNewItemPath & "\" &childItem.ItemName
On Error Resume Next
' Note that while we pass "False" for the bReplace parameter, that
' parameter is ignored. Existing destinations are never replaced, regardless
' of what we pass for the 3rd parameter.
'
objCache.RenameItemEx strOldPath, strTempNewItemPath, False
hr = Hex(Err.Number)
If Err.Number <> 0 Then
On Error Resume Next

WScript.Echo "RenameItemEx Failed with error:" &hr
WScript.Echo "While renaming:" & strOldPath & " to:" &strTempNewItemPath
Err.Clear
nRenameItemExFailureCount = nRenameItemExFailureCount + 1
On Error Resume Next
'
'We got the error in renaming this may happen due to item in use, try to renaname after reboot
'
objCache.RenameItem strOldPath, strTempNewItemPath, False
hr = Hex(Err.Number)
If Err.Number <> 0 Then
On Error Resume Next
WScript.Echo "RenameItem Failed with error:" &hr
WScript.Echo "While renaming:" & strOldPath & " to:" &strTempNewItemPath
Err.Clear
nRenameItemFailureCount = nRenameItemExFailureCount + 1
Else
WScript.Echo "item rename scheduled. A restart of the system is necessary to apply the change."
End If

Else
WScript.Echo "Renamed:" &strOldPath & " to:" &strTempNewItemPath & " SUCCESSFULLY"
End If
End If
Next
End If
If (nRenameItemExFailureCount > 0 & (nRenameItemExFailureCount - nRenameItemFailureCount) > 0) Then
WScript.Echo "item rename scheduled. A restart of the system is necessary to apply the change."
ElseIf (nRenameItemExFailureCount = 0) Then
WScript.Echo "Items Renamed SUCCESSFULLY"
Else
WScript.Echo "ItemsRenamed FAILED"
End If
Next If a file or directory without nested pinned directories (like the user home directory) needs to be renamed, the following script can be used.'
' THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF
' ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO
' THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
' PARTICULAR PURPOSE.
'
' Copyright (c) Microsoft Corporation. All rights reserved.
'
'
' Usage: CscRenameItemEx.vbs /OldItemPath:<path> /NewItemPath:<path> [/Machine:value] [/User:value] [/Password:value]
'
'
' Demonstrates how to rename an item in the Ofline Files cache.
'
' OldItemPath - UNC path of the current path to be renamed.
'
' NewItemPath - UNC path of the new path to replace the old path.
'
' If NewItemPath already exists, the operation is not performed.
' If OldItemPath is currently in use,this operation simply schedules
' a rename to be performed on the next restart.
'
'
On Error Resume Next
const cComputerName = "LocalHost"
const cWMINamespace = "root\cimv2"
const cWMIClass = "Win32_OfflineFilesCache"

'
' Process commandline arguments
'
strOldItemPath = WScript.Arguments.Named("OldItemPath")'
if Len(strOldItemPath) = 0 Then
Wscript.Echo "OldItemPath parameter required"
Err.Raise 449 ' "argument not optional" error
End if

strNewItemPath = WScript.Arguments.Named("NewItemPath")'
if Len(strNewItemPath) = 0 Then
Wscript.Echo "NewItemPath parameter required"
Err.Raise 449 ' "argument not optional" error
End if

strComputerName = WScript.Arguments.Named("Machine")
If Len(strComputerName) = 0 Then strComputerName = cComputerName

strUserID = WScript.Arguments.Named("User")
If Len(strUserID) = 0 Then strUserID = ""

strPassword = WScript.Arguments.Named("Password")
If Len(strPassword) = 0 Then strPassword = ""

set objWMILocator = WScript.CreateObject("WbemScripting.SWbemLocator")

Set objWMIServices = objWMILocator.ConnectServer(strComputerName, _
cWMINameSpace, _
strUserID, _
strPassword)

'
' Note that Win32_OfflineFilesCache is a singleton.
'
' Also note that while we pass "False" for the bReplace parameter, that
' parameter is ignored. Existing destinations are never replaced, regardless
' of what we pass for the 3rd parameter.
'
Set objCache = objWMIServices.Get("Win32_OfflineFilesCache=@")
objCache.RenameItemEx strOldItemPath, strNewItemPath, False
If Err.Number <> 0 Then
WScript.Echo " RenameItemEx Failed:" &Err.Description
Err.Clear
On Error Resume Next
objCache.RenameItem strOldItemPath, strNewItemPath, False
If Err.Number <> 0 Then
WScript.Echo "RenameItem Failed:" &Err.Description
Err.Clear
Else
WScript.Echo "item rename scheduled. A restart of the system is necessary to apply the change."
End If

Else
WScript.Echo "item renamed."
End If

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

976698 You are unable to update the target location of offline file shares in the offline file client side cache without administrative permission

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 name

Update.mum

File version

Not Applicable

File size

17,111

Date (UTC)

12-Feb-2010

Time (UTC)

05:03

Platform

Not Applicable

File name

X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.1.7600.20641_none_abf22f1373799459.manifest

File version

Not Applicable

File size

3,017

Date (UTC)

11-Feb-2010

Time (UTC)

07:17

Platform

Not Applicable

File name

X86_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.1.7600.20641_none_8d79f279aea00fda.manifest

File version

Not Applicable

File size

60,347

Date (UTC)

11-Feb-2010

Time (UTC)

07:27

Platform

Not Applicable

File name

X86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7600.20641_none_9ecf7e29d63ba47f.manifest

File version

Not Applicable

File size

11,592

Date (UTC)

11-Feb-2010

Time (UTC)

07:17

Platform

Not Applicable

File name

X86_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.1.7600.20641_none_0a5ac74cdbb49ee3.manifest

File version

Not Applicable

File size

56,703

Date (UTC)

11-Feb-2010

Time (UTC)

07:24

Platform

Not Applicable

File name

X86_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20641_none_6cb060208c504828.manifest

File version

Not Applicable

File size

1,059,457

Date (UTC)

11-Feb-2010

Time (UTC)

07:16

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.1.7600.20641_none_0810ca972bd7058f.manifest

File version

Not Applicable

File size

3,019

Date (UTC)

11-Feb-2010

Time (UTC)

19:25

Platform

Not Applicable

File name

Amd64_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.1.7600.20641_none_e9988dfd66fd8110.manifest

File version

Not Applicable

File size

60,351

Date (UTC)

11-Feb-2010

Time (UTC)

19:32

Platform

Not Applicable

File name

Amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7600.20641_none_faee19ad8e9915b5.manifest

File version

Not Applicable

File size

11,596

Date (UTC)

11-Feb-2010

Time (UTC)

19:25

Platform

Not Applicable

File name

Amd64_microsoft-windows-offlinefiles-service_31bf3856ad364e35_6.1.7600.20641_none_667962d094121019.manifest

File version

Not Applicable

File size

56,710

Date (UTC)

11-Feb-2010

Time (UTC)

19:30

Platform

Not Applicable

File name

Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20641_none_c8cefba444adb95e.manifest

File version

Not Applicable

File size

1,058,443

Date (UTC)

11-Feb-2010

Time (UTC)

19:25

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

25,908

Date (UTC)

12-Feb-2010

Time (UTC)

05:03

Platform

Not Applicable

File name

Wow64_microsoft-windows-o..nefiles-extend-apis_31bf3856ad364e35_6.1.7600.20641_none_f3ed384f9b5e430b.manifest

File version

Not Applicable

File size

60,349

Date (UTC)

11-Feb-2010

Time (UTC)

07:10

Platform

Not Applicable

File name

Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20641_none_d323a5f6790e7b59.manifest

File version

Not Applicable

File size

1,054,916

Date (UTC)

11-Feb-2010

Time (UTC)

07:09

Platform

Not Applicable

File name

X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.1.7600.20641_none_abf22f1373799459.manifest

File version

Not Applicable

File size

3,017

Date (UTC)

11-Feb-2010

Time (UTC)

07:17

Platform

Not Applicable

File name

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.1.7600.20636_none_ac03a467736b0017.manifest

File version

Not Applicable

File size

3,018

Date (UTC)

05-Feb-2010

Time (UTC)

08:00

Platform

Not Applicable

File name

Ia64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20636_none_6cc1d5748c41b3e6.manifest

File version

Not Applicable

File size

1,058,441

Date (UTC)

05-Feb-2010

Time (UTC)

08:01

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

4,856

Date (UTC)

06-Feb-2010

Time (UTC)

01:13

Platform

Not Applicable

File name

Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20636_none_d33377547901de1b.manifest

File version

Not Applicable

File size

1,054,916

Date (UTC)

05-Feb-2010

Time (UTC)

07:19

Platform

Not Applicable

File name

X86_microsoft-windows-o..inefiles-win32-apis_31bf3856ad364e35_6.1.7600.20636_none_ac020071736cf71b.manifest

File version

Not Applicable

File size

3,017

Date (UTC)

05-Feb-2010

Time (UTC)

07:24

Platform

Not Applicable

File name

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×