Hello,
According to this document it does appear to support S4
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/system-sleeping-states

Hello
The bugcheck code is 0xE6, indicating a DMA issue.

Hello,
Here is some documentation for Windows Subsystem for Android, with links to additional documentation. See if this helps

Hello,
You can use the Windows Performance Analyzer to get detailed information on the boot process and time spent on each Process.
There are a number of blogs on how to use the tool and to interpret the data
Windows Performance Analyzer

Thanks
Darrell

Hello,
If you are using KMS, you can view the KMS Event log on the KMS host, which will display the names of the computers attempting to activate and whether or not they are successful.
In event viewer, look for the KMS Management Service log under Application and Service logs.

Hello,
The only messages are informational, I do not see any Error or Warning messages.
Your system looks fine at least from this portion of the CBS.log.
Are you have any problems with installing updates from Windows update?

Hello,
Is this intended for a single machine or for multiple machines?
MAK keys do require an administrator, however normally companies may assign someone to track the usage of the key and to limit who has exposure to the actual key.

Where was this purchased and with how many licenses/

Thanks
Darrell

Hello,
Once the machine is activated the hardware retailer of the MAK or the OEM channel cannot deactivate the OS.

Hello,

The KMS host will only take KMS keys it will not take MAK keys
If they want to use MAK keys then they do not need a KMS host, the MAK keys will activate online with the Microsoft Servers.

If they want to use KMS to activate, they will need a KMS host with the appropriate Windows Server KMS host key. This will allow the Windows 10 clients to activate.
The Windows 10 clients will need to use the default KMS client keys
See this document which lists the default client keys:
https://docs.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys

Use this document that shows which KMS host key is needed to Activate Windows 10 clients. ( Not on Windows server 2016 it has to be a Windows Server kMS host key
https://docs.microsoft.com/en-us/windows-server/get-started/kms-activation-planning#activation-versions

The error message you are getting is because you are trying to install a Windows 10 key on a Windows Server machine. Windows Server machine only take Windows Server Keys.

IT also sounds like you are trying to mix both KMS and MAK scenarios. You shold go with one or the other.
I would think that KMS would be the way to go, but you would not be using WIndows 10 MAK keys then.
The Windows 10 clients would need to be using the default KMS keys, see link above.
The KMS host ( Windows server 2016 machine) would need a Windows server 2019 KMS host key.

Hello,
You may want to try using AppAssure to assist you with this issue.
They offer free App compatibility for Corporate customers or for ISVs.
https://www.microsoft.com/en-us/fasttrack/microsoft-365/app-assure

Thanks,
Darrell

Hello,
There are supposed to be more correct ways of getting the OS Version, than using the registry key.

Hello,
You can run Winver or MSInfo32 from the run line or from a cmd prompt you can run systeminfo.

Hello,
Let me repeat my above message to be sure it's seen.

This is a known issue, which should ship in a Windows Update in early Q2.

Notes in KB will read something similar to this:
Addressed an issue with DHCP Option 119 - Domain Search Option which prevented the use of Connection-specific DNS Suffix Search List.

Thanks
Darrell

Hello,
This is a known issue, which should ship in a Windows Update in early Q2.

Notes in KB will read something similar to this:
Addressed an issue with DHCP Option 119 - Domain Search Option which prevented the use of Connection-specific DNS Suffix Search List.

Thanks

Darrell

Hello,
The Windows 10 machine is running IPV6 and the Windows 11 Machine is running IPV4.
What happens if they are running the same.
Thanks

Darrell