For anyone who comes to this page with the same issue, and also finds that the information lacking clarity:
M$, in its infinite wisdom, changed one small-but-important aspect of manually configuring TCP/IP settings for IPv4 in Settings in Windows 10 from the way everyone everywhere has been doing it since Windows 3.1 (AFAIK). Instead of setting the "netmask" or "subnet mask" (e.g., 255.255.255.0), in its place you need to enter the "subnet prefix length." As the OP essentially asks, since most everyone who communicates TCP/IP settings to consumers provides the subnet mask, why, in the name of all that is holy, is Windows 10 now asking for something for which the general population has to search the Internet for the translation? Thankfully, things haven't changed when looking at TCP/IP configuration in Adapter Settings, but you have to dig to get to that anymore.
[OFF SOAPBOX]
So, to help those in need of finding the translation, here's a page I found that helped me just now. From the table about 1/3 of the way down the page, just look for your subnet mask in the "Subnet Mask" column, then use as your "subnet prefix length" the number in the "CIDR Prefix" column, but without the leading "/" (e.g., 255.255.255.0 would translate to 24, not /24).
Cheers and good luck!
EDIT 6/25/21: I guess the link I included in my original post got wiped out, and I don't have a record of it. Here (hopefully) is a link to an IPv4 CIDR chart; same concept: use the CIDR notation (without the "/" in front) that corresponds with your subnet mask:
https://www.meridianoutpost.com/resources/articles/IPv4-CIDR-reference-sheet.php