|
This topic lists Errata found in [MS-RDPBCGR] since
it was last published. Since this topic is updated frequently, we recommend
that you subscribe to this RSS feed to receive update notifications.
Errata are subject to the same terms as the
Open Specifications documentation referenced.
|
 RSS
|
To view a PDF file of the errata for the previous versions
of this document, see the following ERRATA Archives:
October 16, 2015 - Download
June 30, 2015 - Download
July 18, 2016 - Download
March 20, 2017 - Download
June 1, 2017 - Download
December 1, 2017 - Download
March 16, 2018 - Download
September 12, 2018 - Download
March 13, 2019 - Download
September 23, 2019 - Download
March 4, 2020 - Download
August 24, 2020 – Download
April 7, 2021 - Download
Errata below are for Protocol Document Version V55.0
– 2021/06/25.
|
Errata Published*
|
Description
|
|
2023/08/16
|
Please see the diff
document.
Section 2.2.1.3.1 User Data Header (TS_UD_HEADER):
Added data block type CS_UNUSED1.
Changed from:
|
Value
|
Meaning
|
|
. . .
|
|
|
CS_MULTITRANSPORT
0xC00A
|
The data block that follows contains Client
Multitransport Channel Data (section 2.2.1.3.8).
|
|
SC_CORE
0x0C01
|
The data block that follows contains Server Core
Data (section 2.2.1.4.2).
|
|
. . .
|
|
Changed to:
|
Value
|
Meaning
|
|
. . .
|
|
|
CS_MULTITRANSPORT
0xC00A
|
The data block that follows contains Client
Multitransport Channel Data (section 2.2.1.3.8).
|
|
CS_UNUSED1
0xC00C
|
The data block that follows contains Client Unused1
Data (section 2.2.1.3.9).
|
|
SC_CORE
0x0C01
|
The data block that follows contains Server Core
Data (section 2.2.1.4.2).
|
|
. . .
|
|
Section 2.2.1.3.9 Client Unused1 Data
(TS_UD_CS_UNUSED1): Added section.
Added TS_UD_CS_UNUSED1 packet that has a GCC user data
block header (4 bytes) with a pad2Octets (2 bytes) for padding. Please see
the diff
document.
|
|
2022/01/04
|
In section 2.2.1.3.2, Client Core Data
(TS_UD_CS_CORE), added the client version number for RDP 10.10:
Changed from:
|
Value
|
Meaning
|
|
0x00080001
|
RDP 4.0 clients
|
|
0x00080004
|
RDP 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, 7.1, 8.0, and 8.1
clients
|
|
0x00080005
|
RDP 10.0 clients
|
|
0x00080006
|
RDP 10.1 clients
|
|
0x00080007
|
RDP 10.2 clients
|
|
0x00080008
|
RDP 10.3 clients
|
|
0x00080009
|
RDP 10.4 clients
|
|
0x0008000A
|
RDP 10.5 clients
|
|
0x0008000B
|
RDP 10.6 clients
|
|
0x0008000C
|
RDP 10.7 clients
|
|
0x0008000D
|
RDP 10.8 clients
|
|
0x0008000E
|
RDP 10.9 clients
|
Changed to:
|
Value
|
Meaning
|
|
0x00080001
|
RDP 4.0 clients
|
|
0x00080004
|
RDP 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, 7.1, 8.0, and 8.1
clients
|
|
0x00080005
|
RDP 10.0 clients
|
|
0x00080006
|
RDP 10.1 clients
|
|
0x00080007
|
RDP 10.2 clients
|
|
0x00080008
|
RDP 10.3 clients
|
|
0x00080009
|
RDP 10.4 clients
|
|
0x0008000A
|
RDP 10.5 clients
|
|
0x0008000B
|
RDP 10.6 clients
|
|
0x0008000C
|
RDP 10.7 clients
|
|
0x0008000D
|
RDP 10.8 clients
|
|
0x0008000E
|
RDP 10.9 clients
|
|
0x0008000F
|
RDP 10.10 clients
|
In section 2.2.1.4.2, Server Core Data
(TS_UD_SC_CORE), added the server version number for RDP 10.10:
Changed from:
|
Value
|
Meaning
|
|
0x00080001
|
RDP 4.0 servers
|
|
0x00080004
|
RDP 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, 7.1, 8.0, and 8.1
servers
|
|
0x00080005
|
RDP 10.0 servers
|
|
0x00080006
|
RDP 10.1 servers
|
|
0x00080007
|
RDP 10.2 servers
|
|
0x00080008
|
RDP 10.3 servers
|
|
0x00080009
|
RDP 10.4 servers
|
|
0x0008000A
|
RDP 10.5 servers
|
|
0x0008000B
|
RDP 10.6 servers
|
|
0x0008000C
|
RDP 10.7 servers
|
|
0x0008000D
|
RDP 10.8 servers
|
|
0x0008000E
|
RDP 10.9 servers
|
Changed to:
|
Value
|
Meaning
|
|
0x00080001
|
RDP 4.0 servers
|
|
0x00080004
|
RDP 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, 7.1, 8.0, and 8.1
servers
|
|
0x00080005
|
RDP 10.0 servers
|
|
0x00080006
|
RDP 10.1 servers
|
|
0x00080007
|
RDP 10.2 servers
|
|
0x00080008
|
RDP 10.3 servers
|
|
0x00080009
|
RDP 10.4 servers
|
|
0x0008000A
|
RDP 10.5 servers
|
|
0x0008000B
|
RDP 10.6 servers
|
|
0x0008000C
|
RDP 10.7 servers
|
|
0x0008000D
|
RDP 10.8 servers
|
|
0x0008000E
|
RDP 10.9 servers
|
|
0x0008000F
|
RDP 10.10 servers
|
|
*Date format: YYYY/MM/DD