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. Profile attributes are not copied to UPD at logon in Windows Server 2012

Profile attributes are not copied to UPD at logon in Windows Server 2012

View products that this article applies to.

Symptoms

When you use User Profile Disks (UPD) to log on to the system, your user profile experiences issues. For example, the AppData folder is not hidden, and Internet Explorer does not contain any history data.

↑ Back to the top

Cause

This issue occurs because these attributes are not set correctly for the profile folders in UDP. Additionally, the low integrity process is prevented from writing to the Virtual Hard Disk (VHD) file.

↑ Back to the top

Resolution

To resolve this issue, we have released a hotfix.

Notes
  • Even though this issue has been observed only in Windows Server 2012, the hotfix also applies to Windows 8.
  • This hotfix does not resolve if the UPD VHD file already exists. For already existing VHD files, you must delete it, and then create a new VHD file after you apply the hotfix. Or, you can set the attributes manually.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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 this specific problem.

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, submit a request to 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

There are no prerequisites to apply this hotfix.

Registry information

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

Restart requirement

You may 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 8 and Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" 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, 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.2.920 0.21 xxxWindows 8 and Windows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 8
File nameFile versionFile sizeDateTimePlatform
Vmrdvcore.dll6.2.9200.21456293,88810-Apr-201501:33x86
Fsdepends.sys6.2.9200.2145649,49612-Apr-201523:00x86
Rdvvmtransport.dll6.2.9200.2145666,04812-Apr-201522:34x86
Sessenv.dll6.2.9200.21456249,34412-Apr-201522:34x86
For all supported x64-based versions of Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Vmrdvcore.dll6.2.9200.21456354,81609-Apr-201522:21x64
Fsdepends.sys6.2.9200.2145657,68812-Apr-201522:53x64
Rdvvmtransport.dll6.2.9200.2144281,92012-Apr-201522:30x64
Sessenv.dll6.2.9200.21456291,84012-Apr-201522:30x64
Rdvvmtransport.dll6.2.9200.2145666,04812-Apr-201522:34x86
Sessenv.dll6.2.9200.21456249,34412-Apr-201522:34x86

Additional file information

Additional file information for Windows 8 and Windows Server 2012
Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_7abae09017de98062502af2052c42995_31bf3856ad364e35_6.2.9200.21457_none_14d6a92117a759db.manifest
File versionNot applicable
File size708
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameX86_d0cf16aab4aa0bcf040a410d90398ed2_31bf3856ad364e35_6.2.9200.21457_none_1c81da0e09d220d4.manifest
File versionNot applicable
File size722
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameX86_e64dee22a94925b2c486261c2efba77a_31bf3856ad364e35_6.2.9200.21457_none_e0b14eb6ca2acd3e.manifest
File versionNot applicable
File size718
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameX86_microsoft-hyper-v-integration-rdv-core_31bf3856ad364e35_6.2.9200.21457_none_54b89da5e4e1350f.manifest
File versionNot applicable
File size1,841
Date (UTC)12-Apr-2015
Time (UTC)23:18
PlatformNot applicable
File nameX86_microsoft-windows-f..ependencyminifilter_31bf3856ad364e35_6.2.9200.21457_none_27aafc7171e47665.manifest
File versionNot applicable
File size5,917
Date (UTC)12-Apr-2015
Time (UTC)23:13
PlatformNot applicable
File nameX86_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.21457_none_dc365813d2107f1b.manifest
File versionNot applicable
File size8,228
Date (UTC)12-Apr-2015
Time (UTC)23:17
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012
File propertyValue
File nameAmd64_7df2e1c897df3e0a4eaed32f2b579e1d_31bf3856ad364e35_6.2.9200.21457_none_c7d46315fd1def7d.manifest
File versionNot applicable
File size712
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameAmd64_b7e51c74fa35ed7b8ae978e40ce7cf6d_31bf3856ad364e35_6.2.9200.21457_none_5126719a550c6e5d.manifest
File versionNot applicable
File size1,094
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameAmd64_d2ef33a913f0fb2f3eb87aff37f2a033_31bf3856ad364e35_6.2.9200.21457_none_3ee91d30378c1395.manifest
File versionNot applicable
File size722
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameAmd64_e5e970bc70280598c1edf5854824a50c_31bf3856ad364e35_6.2.9200.21457_none_db0718c7268b67ea.manifest
File versionNot applicable
File size726
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameAmd64_e80ce71cfd7feea753227bf55abcc6a4_31bf3856ad364e35_6.2.9200.21457_none_ddb95fcabce75393.manifest
File versionNot applicable
File size726
Date (UTC)01-May-2015
Time (UTC)22:19
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-integration-rdv-core_31bf3856ad364e35_6.2.9200.21457_none_b0d739299d3ea645.manifest
File versionNot applicable
File size1,843
Date (UTC)13-Apr-2015
Time (UTC)01:00
PlatformNot applicable
File nameAmd64_microsoft-windows-f..ependencyminifilter_31bf3856ad364e35_6.2.9200.21457_none_83c997f52a41e79b.manifest
File versionNot applicable
File size5,919
Date (UTC)13-Apr-2015
Time (UTC)01:06
PlatformNot applicable
File nameAmd64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.21457_none_3854f3978a6df051.manifest
File versionNot applicable
File size8,232
Date (UTC)13-Apr-2015
Time (UTC)00:58
PlatformNot applicable
File nameWow64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.21457_none_42a99de9beceb24c.manifest
File versionNot applicable
File size5,628
Date (UTC)12-Apr-2015
Time (UTC)23:17
PlatformNot applicable

↑ 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

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3044757
Revision : 1
Created on : 1/7/2017
Published on : 5/14/2015
Exists online : False
Views : 168