Symptoms

Consider the following scenario:

  • You have a Remote Desktop Session Host (RD Session Host) on a server that's running Windows Server 2012.

  • You start a remote desktop session to the server by using specific user credentials.

  • An unexpected restart occurs on the session host server while you're logged on.

  • After the server restarts, you try to start a remote desktop session to the server by using the same user credentials.


In this scenario, you find that you are logged on with a temporary profile. Additionally, you may experience any of the following symptoms:

  • NTFS errors and warnings such as event ID 140, event ID 50, and event ID 137

  • Delayed write fails for the user profile disk (UPD) virtual hard disk (VHDX) files

  • Lost data after you reconnect


Cause

This problem occurs because the remote desktop profile manager may work incorrectly after the host server restarts. This behavior may occur when the server restarts after losing power. It may also occur when the user logs on again after a Stop error.

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:

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 8 or Windows Server 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) 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 notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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.

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16 xxx

    Windows 8 and Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

  • 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 8 and Windows Server 2012" 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 8

File name

File version

File size

Date

Time

Platform

Rdvvmtransport.dll

6.2.9200.16384

66,048

26-Jul-12

3:19

x86

Sessenv.dll

6.2.9200.16731

249,344

5-Oct-13

4:04

x86

Rdvvmtransport.dll

6.2.9200.16384

66,048

26-Jul-12

3:19

x86

Sessenv.dll

6.2.9200.20842

249,344

5-Oct-13

3:57

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Rdvvmtransport.dll

6.2.9200.16384

81,920

26-Jul-12

3:07

x64

Sessenv.dll

6.2.9200.16731

291,328

5-Oct-13

5:42

x64

Rdvvmtransport.dll

6.2.9200.16384

81,920

26-Jul-12

3:07

x64

Sessenv.dll

6.2.9200.20842

291,328

5-Oct-13

4:20

x64

Rdvvmtransport.dll

6.2.9200.16384

66,048

26-Jul-12

3:19

x86

Sessenv.dll

6.2.9200.16731

249,344

5-Oct-13

4:04

x86

Rdvvmtransport.dll

6.2.9200.16384

66,048

26-Jul-12

3:19

x86

Sessenv.dll

6.2.9200.20842

249,344

5-Oct-13

3:57

x86

For all supported ARM-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Rdvvmtransport.dll

6.2.9200.16384

65,024

26-Jul-12

1:30

Not Applicable

Sessenv.dll

6.2.9200.16731

232,960

5-Oct-13

2:47

Not Applicable


Status

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

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8

File name

X86_5d9b66b705c560954f19639805e28b32_31bf3856ad364e35_6.2.9200.20842_none_a1f8fc6cd283ed35.manifest

File version

Not Applicable

File size

722

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

X86_8af6c589663ddf4b1aa57f926c8ea919_31bf3856ad364e35_6.2.9200.16731_none_3b8ae9ec181c4c61.manifest

File version

Not Applicable

File size

722

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

X86_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.16731_none_dbbc77c4b8e7ea60.manifest

File version

Not Applicable

File size

8,375

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

X86_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.20842_none_dc3c44edd20cbf72.manifest

File version

Not Applicable

File size

8,375

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

Amd64_0be51b492c81c05eec730f9695e46cc8_31bf3856ad364e35_6.2.9200.20842_none_cee5e4a83ac14ccd.manifest

File version

Not Applicable

File size

726

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_0c11c39b08f0d219a4760d9055551a38_31bf3856ad364e35_6.2.9200.20842_none_31de99ae9cfcd1d6.manifest

File version

Not Applicable

File size

726

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_2ddbc80549379e756cca2af4157267e6_31bf3856ad364e35_6.2.9200.16731_none_de8ef75d23e433d4.manifest

File version

Not Applicable

File size

726

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_519af937f07cc3972c1f29698009a751_31bf3856ad364e35_6.2.9200.20842_none_c7836bda48c924ce.manifest

File version

Not Applicable

File size

1,094

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_65e21c39aa889f874f1f8a204ddca520_31bf3856ad364e35_6.2.9200.16731_none_10c5022cd0e2a9d7.manifest

File version

Not Applicable

File size

1,094

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_dc1f1cad080808274a20dbd41de90d15_31bf3856ad364e35_6.2.9200.16731_none_37e9af56fd36d5d6.manifest

File version

Not Applicable

File size

726

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.16731_none_37db134871455b96.manifest

File version

Not Applicable

File size

8,379

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Amd64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.20842_none_385ae0718a6a30a8.manifest

File version

Not Applicable

File size

8,379

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Wow64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.16731_none_422fbd9aa5a61d91.manifest

File version

Not Applicable

File size

5,655

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

File name

Wow64_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.20842_none_42af8ac3becaf2a3.manifest

File version

Not Applicable

File size

5,655

Date (UTC)

05-Oct-2013

Time (UTC)

14:45

Platform

Not Applicable

Additional files for all supported ARM-based versions of Windows 8

File name

Arm_42540d348d85177f5efbb1bad3d99691_31bf3856ad364e35_6.2.9200.16731_none_0bdbc97f3e0f9f23.manifest

File version

Not Applicable

File size

722

Date (UTC)

05-Oct-2013

Time (UTC)

14:44

Platform

Not Applicable

File name

Arm_microsoft-windows-t..s-sessionenvservice_31bf3856ad364e35_6.2.9200.16731_none_dbbeea1cb8e50926.manifest

File version

Not Applicable

File size

8,375

Date (UTC)

05-Oct-2013

Time (UTC)

14:44

Platform

Not Applicable


References

See the terminology Microsoft uses to describe software updates for more information.

Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×