Ascii.jp I checked whether Windows 11 or 10 is moving from Windows, but the answer is different.

Fix issues in previewing and quality updates in Android app execution environment and Windows 11 topics continue

Previews and quality updates of Android application execution environment on Windows 11, and Windows 10 ver.News related to Windows, such as the release of 21H2.However, it is just after the release of Windows 11, and it will be a time to talk about various things.

By the way, the execution environment of the Android app of Windows 11 is currently only in the United States, and the Amazon app store seems to be checking the area with an IP address, and Amazon..I was rejected just by inserting the COM account.So, I would like you to forgive the screen that could not be accessed this time.

I decided to try the Android app in the beta version of Windows 11, but the important Amazon Appstore doesn't seem to work in Japan.

Also, on the 22nd (local time), Windows 10 ver.It is announced that 21H2 is completed, and the blog post is 19044.The 1288 is the finished version, and the ISO image has also been released.

One of my machines was also notified by Windows Update, so when I updated it, it was installed in 19044..It was 1319.Moreover, this build has started distribution on October 19.If the larger number is new, the latest version is build 19044.It should be 1319.Nevertheless, 19044 in the blog post.What does 1288 mean?Moreover, Windows 10 ver.From 2004 to 21H1, each has 19041.1288, 19042.1288, 19043.1288 is distributed on October 12 (https: // docs).Microsoft.Com/JA-JP/Windows/Release-Health/Release-Information).

For the time being, if you are joining Beta Channel in Windows Insider Program, you may want to update it via Windows Update without ISO.I feel like I downloaded the ISO image over time and lost it.

Is it moving now Windows 10 or 11?

Every time there is a Windows update, we are examining how to check the Windows version and name.I have multiple machines, each version is different and the edition is different.It is bad to make a mistake in the target machine to verify the version upgrade.However, how to find a Windows version is becoming increasingly troublesome.This is because the compatibility of software has increased, and it has become difficult to judge compatibility with version numbers.

One of the major reasons that Windows can notify his version via API is to make it possible to determine whether the application has the necessary functions for Windows.However, on the contrary, the version check became an ad, and the application sometimes stopped working after the update.For this reason, the old Windows was prepared for a setVer command to teach the lie version number to the MS-DOS app.

From Windows 95, the name of the Windows and the OS that look like users are different.At that time, there were two NT and 95 series in the environment where the 32 -bit application operated, and the "Windows version" began to be confused.At the level of the API (Application Programming Interface) that the application calls for the use of Windows, there was even more confusion.For example, the function to play videos depended on the version of the installed Windows Media Player, not just the Windows version.

So Microsoft has greatly changed the version check on Windows 8.The API that obtains the version number so far has been prepared as a non -recommended API called "Version Helper".This determines whether it is a version after Windows release (Windows XP or Windows 7).

If you use this, it will not be compatible with XP or Vista, but for Windows 7/8, it will be easier to judge, and the Windows 10 that appeared will not be mistaken for the version.The API for obtaining the conventional version number is returned by the appropriate version by the corresponding version specified at the time of development.

For example, if an application developed and compiled as Windows 8 is trying to get a version number, Windows 8 version number (ver).6.2) I came to teach.By doing this, Version ~ 6.Applications that only check the version in the form of 2 will work on Windows 10 (if Version is 10).2 is not established).

However, instead of the application developer, the version check from a system administrator's point of view is that "which version of Windows is installed on the machine?" I want you to.

Now, there are several ways to check the Windows version.First of all, if you look at the GUI, Winver.EXE and system information (msinfo32).There is EXE).

Winver, a standard version of Windows.exe.It reports that this is Windows 11

Also, C: \ Windows \ System32 \ NTOSKRNL.There is also a way to look at the EXE property.

NTOSKRNL.EXE is equivalent to a Windows kernel, but if you look at the property, 10.0.22000.Report the version 282

What you can see is that there are two main types of versions.One is Winver.As with EXE, the product name, version, build number, etc. are also written.The other is simply displaying only the version number including the build number.

Looking at this, the version of Windows 11 is "Ver.21H2 OS Build 2200.282 "or" 10.0.22000.282 ".While saying Windows 11, the top of the version number is the same as Windows 10.No, no.

Windows 10 ver.In 21H2, "ver.21H2 OS Build 19044.1319 "or" 10.0.19041.1319 ".If this is also a number notation, the lead is "10".Since the part corresponding to the build number in the second half is different from Windows 11, it is distinct, but in terms of version number, there is almost no difference between Windows 11 and Windows 10.

Windows 10 is Ver.From 2004 (the build number is 19041), the internal version remains 19041, and the 19042-19043 is probably a number, so the base build is the same as "19041".

So what about the version display on the command line?There are six ways to display possible versions from the command line.

Of these, "Get-Computerinfo" and "Registry" reported "Windows 10" as the name.

I looked at the Windows 11 version in six ways in the command line.Some report Windows 10, while others report Windows 11 correctly.

On the other hand, the CIM class "Win32_operationGSYSTEM" and "Systeminfo".The EXE command reports Windows 11.CMD.EXE Ver command,.Net Framework "System.Environment."OSVERSION" is "10.0.Report the version number "22000" and do not report whether it is Windows 10 or 11.

Looking at this, whether the machine is Windows 10 or 11 is "pros and cons."However, since this was upgraded from Windows 10, maybe a Windows 11 pre -installed machine might have had a different result (yes, I haven't bought it yet).

Currently, if you want to check with the GUI.EXE, but if you want to connect to another machine via the network and check the version while working on the command line, Systeminfo.If you want to use EXE and want to check from remotely, it seems good to use CIM Win32_ophoneGSYSTEM.

To 12th

What is ASCII Club?