IT Solutions Technology Blog

After installing KB5040430 we are seeing issues on the Server 2019 Remote Desktop Gateway on RDS

Faulting application name: svchost.exe_TSGateway, version: 10.0.17763.3346, time stamp: 0xb6a0daab

Faulting module name: aaedge.dll, version: 10.0.17763.6054, time stamp: 0xce1c5805

Exception code: 0xc0000005

Fault offset: 0x000000000005abe2

Faulting process id: 0x1db0

Faulting application start time: 0x01dad38ae65f65ae

Faulting application path: C:\Windows\system32\svchost.exe

Faulting module path: c:\windows\system32\aaedge.dll

Report Id: bbb10a26-fc25-4bba-9ed8-45c2eff5f5ba

Faulting package full name:

Faulting package-relative application ID:
—

The system was operating normally before the Windows Update

This is now listed as a Known Issue in each relevant KB article:

Windows Server 2022 KB5040437

Windows Server 2019 KB5040430

Windows Server 2016 KB5040434

ldp.exe -H <ldap_server> -P <port> -Y

Let’s break it down:

* `-H` specifies the hostname or IP address of the LDAP server
* `-P` specifies the port number (default is 389, but you might need to specify a different port if your LDAP server is using a non-standard port)
* `-Y` tells `ldp.exe` to use SSL/TLS encryption

So if you want to test an LDAP connection over SSL/TLS to ‚example.com‘ on port `636` you would run

ldp.exe -H example.com -P 636 -Y

This command will prompt you for a username and password. Enter the credentials of a user with sufficient privileges to perform the query

If everything is set up correctly you should see some LDAP data returned in a human-readable format if not you might get an error message indicating what went wrong (e.g., invalid credentials, server not responding)

Remember to replace `example.com` and `636` with your actual LDAP server’s hostname or IP address and the port number you’re using for SSL/TLS connections

Keep in mind that this is just a basic example you can modify the command to perform more complex queries, such as searching for specific users or groups

Microsoft Windows [Version 10.0.20348.587]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator>reagentc /disable
REAGENTC.EXE: Operation Successful.

C:\Users\Administrator>diskpart

Microsoft DiskPart version 10.0.20348.1

Copyright (C) Microsoft Corporation.
On computer: WIN-38VTALKPTN6

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
——– ————- ——- ——- — —
Disk 0 Online 64 GB 1024 KB *

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
————- —————- ——- ——-
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 63 GB 117 MB
Partition 4 Recovery 524 MB 63 GB

DISKPART> sel part 3

Partition 3 is now the selected partition.

DISKPART> shrink desired=1536 minimum=1536

DiskPart successfully shrunk the volume by: 1536 MB

DISKPART> sel part 4

Partition 4 is now the selected partition.

DISKPART> delete partition override

DiskPart successfully deleted the selected partition.

DISKPART> create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

DiskPart succeeded in creating the specified partition.

DISKPART> gpt attributes =0x8000000000000001

DiskPart successfully assigned the attributes to the selected GPT partition.

DISKPART> exit

Leaving DiskPart…

C:\Users\Administrator>

C:\Users\Administrator>reagentc /enable
REAGENTC.EXE: Operation Successful.

C:\Users\Administrator>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 2f8e1600-b0c0-11ee-bcbe-b80c2e429d3d
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

C:\Users\Administrator>

License Requirements:
All physical cores in the Server must be licensed (Hyperthreading (SMT) does not count as actual physical cores)
A minimum of 8 cores must be licensed for each processor
A minimum of 16 cores must be licensed for each Server

Licensing Calculator:
Number of physical processors in the server 2 processor(s)
Number of physical cores per processor 32 physical cores per processor
Total of 64 cores need to be licensed

License Requirements:
Base License Required Windows Server Datacenter (16 core) 1
Additional Cores To Be Licensed 48
Additional Licenses Required for Compliance
Windows Server Datacenter Additional License (16 core) 3

After installing KB5031364 on virtual machines (VMs) running on VMware ESXi hosts Windows Server 2022 might fail to start up affected VMs will receive an error with a blue screen and Stop code ‚PNP DETECTED FATAL ERROR‘ this issue only affects guest VMs with the following configuration on VMware ESXi hosts only

• AMD Epyc physical processor
• Expose IOMMU to guest OS“ enabled in VMware settings for the VM
• Enable Virtualization Based Security” enabled in Windows Server 2022
• System Guard Secure Launch“ enabled in Windows Server 2022

Workaround: To mitigate this issue you can disable „Expose IOMMU to guest OS“ this workaround should only be used in environments which do not require „Expose IOMMU to guest OS“ to be enabled

Next steps: We are working on a resolution and estimate a solution will be available in mid-November 2023

Geekbench – CPU benchmark measures performance in new application areas including Augmented Reality and Machine Learning so you’ll know how close your system is to the cutting-edge

with 4 CPU Cores 4 Sockets 1 Core/Socket

with 4 CPU Cores 1 Socket 4 Cores/Socket

with 4 CPU Cores 2 Sockets 2 Cores/Socket

with 1 CPU Core 1 Socket 1 Core/Socket

with 2 CPU Cores 1 Socket 2 Cores/Socket