Hi.
It seems like the AWS AMI provided now on the AWS Marketplace:
“AWS NVIDIA CloudXR AMI Introductory Offer”
is a Windows Server 2016 and not a 2019.
This gives a lot of problems like : SetThreadDescription entry point issues,…etc…
Kind regards.
Tristan Salome from PresenZ.
Hello again.
To be complete.
The AMI is supposed to be 2019, the description and full name is clear about it: win2019-server-vWS-512.78-cloudxr-v3.2_ami5-c90c69dc-35e4-43e3-9f6e-f75d98ec1680
But when I create a fresh instance from it and pull out a System Information: It shows: Windows Server 2016 Datacenter.
Kind regards.
Not exactly sure how that’s possible.The image is based on Windows 2019, but the only thing I can figure is the information is coming from AWS’s hypervisor level which may build on something they don’t expose.
Hi wcannady.
Thank you for your answer.
I know it is weird.
But I doubt it is related to some misinformation from AWS hypervisor.
I’ve made some digging on google to have other ways to define the exact windows version, aside form "system information-> about’
For instance, after creating a fresh instance form the CloudXR AMI
- system information gives me: Windows server 2016
- and file properties about C:/Windows/system32/systray.exe shows File version: 10.0.14393.0
But If I take an another instance based on Windows Server 2019:
- system information gives me: Windows server 2019
- and file properties about C:/Windows/system32/systray.exe shows File version: 10.0.17763.1
So this is all coherent with the server version being indeed Server 2016 on the current CloudXR AMI in the marketplace.
Would you, or anyone else for that matter, be kind enough to create an instance from the current “AWS NVIDIA CloudXR AMI Introductory Offer” and checking the system information and file version of C:/Windows/system32/systray.exe ?
Kind regards.
Tristan