"os.release()" returns wrong / unexpected value on windows 11

Premiere Pro
,
1

I am testing on Windows 11, Premiere Beta (26.1.0 Beta build 8)
One of the function log the system info (to help with support / troubleshooting once shipped).

However when dumping the os info, some data seems wrong.

const os = require(‘os’);
os.platform() // OK (set to “win32”);
os.arch() // OK (set to “x64“);
os.release() // _NOT_ OK (set to “6.2.9200”. Using cmd on that same box, the "ver" command return “Microsoft Windows [Version 10.0.26200.7462]“)

This release (6.2.9200) seems to map to an older Windows 8 based release (RT).

image
image654×240 9.63 KB

Docs also report it should be “10.x.y.z” as one would expected.
Looks like a bug to me.

image
image615×196 8.89 KB

https://developer.adobe.com/premiere-pro/uxp/uxp-api/reference-js/Modules/os/OS/#release

1 Like
2

[This seems like an issue with UXP, and not specifically with PPro’s UXP APIs…]

I’ll ask the UXP team; we’re reporting what the OS provides. :slight_smile:

Any chance you’re running Windows within a VM?

3

Thanks Bruce.

No, it is NOT running inside a VM (with 96Gb of RAM available & 24 cores shown above, it would be a very big VM and defying most usecase for a VM :slight_smile: )

BTW, I came across the following - which may explain the problem (if not part of manifest, will return 6.2.9200)
I would guess that the app hosting UXP / the running NodeJs code may not have the proper manifest (if it is the case it would easily repro for you as well, on any window system).

image
image1318×1241 63.4 KB

image
image655×143 8.14 KB

image
image996×122 17.5 KB

4

Hi,

Any chance this will get fixed before RTM / releasing the new Premiere ?

For troubleshooting the plugin, it would be very helpful to know if customer are running on Win10 or win 11 (and what exact version).
As of now os.release() returns version “6.2.9200” on windows 11 - this is obviously wrong (and useless since all windows version will probably return that version).

image
image552×358 43.7 KB

Thx !

5

Relevant:

6

Right - but that link was last updated 5 years ago.
Which means Adobe dotNet app is still build with a version of .Net < 5 (maybe for backward compatibility on old windows box ?).

5+ years after that dotNet release, it’s Probably time to upgrade your build to target .Net 5+
If you are still building on an old .Net, we may need need Adobe to update the dotnet manifest so it may return the proper value (or maybe update the code to PInvoke in Win32 go get the actual value instead of the default value - but not sure if there are win32 API that would do this anymore)

BTW, I checked on my side and windows 11 does indeed have dotnet 5.x by default installed (I don’t remember upgrading it)

# /* using powershell  */
Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release

> 533509