It all depends on your use-case scenario, obviously there is no clear answer until we know more about your specific purposes, the environment the machine will be used in and what you plan on doing with it down the road. But I will share with you my experience doing a major office upgrade from Windows XP on a bunch of old computers (circa 2009) and that used a bunch of proprietary imaging gear drivers that were made by companies who have since disappeared and no longer update or support the equipment (which cost me tens-of-thousands of dollars to buy!!!).
WIN-XP CATASTROPHE:I was running WinXP in a networked office environment on at least 6 machines tied to a Windows Server. Keep in mind all this was installed back in 2008-2009 or so, I can't remember the exact year, but it has been a decade for sure or perhaps more. I decided to keep with this system up until now because things worked and I did not want to face any issues upgrading, as there were a lot of proprietary specialized imaging systems attached that use special USB drivers that were made only for WinXP.
Obviously WinXP support ended years ago, so I always had that annoying RED popup in the corner about End-Of-Support. Windows Defender wouldn't run, blah blah blah.... I was taking things into my own hands, living dangerously! And so I dreaded the upgrade process and procrastinated because of the cost and down-time involved. But I knew ONE DAY I would have to upgrade.
ARMAGEDDON:So the DAY finally came crashing down on me at the end of June when there was an update in a critical piece of software that my office needed to communicate with insurance-related servers (to check certain things). The old communications protocol for that software was being shuttered and you had NO CHOICE but to use a newer version that needed to communicate using the new protocol, and that new version DID NOT RUN on WIN XP, PERIOD! It also had a few .NET dependencies and so on, all of which were not able to run on WIN XP. This was a *critical* need for my office to run and would have been a major pain if we didn't have it available to customer service. Therefore, it was time to upgrade!
First thing I did was buy a Win10 Pro machine (refurbed) and set it to run on SMB1 for the time being, because it needed to be able to communicate with the server and all the other WinXP machines in the office network. That Win10 machine received the critical software (for insurance) update and WHAM BAM I was able to at least install the new protocol software on there to keep functioning.
That took me out of critical situation for the moment.
Next, I started migrating my WinXP machines to Win10 Pro. Yes! THE SAME MACHINES that I bought over 10 years ago, nothing special, I pulled out the hard drives (just in case I didn't want to write over my stuff if I had to revert) and bought some cheap SSD's. I installed Win10 64-bit on most of my computers, from a Win10 USB-key I made a while back, and it boots and runs smoothly! At least for the software I use in the office, it does not require "gaming" level graphics or anything like that. I'm much happier being on Win10. I used my Win7 sticker info either from some other computers I have and lo-and-behold, it installed and activated and did not complain a bit!
The machines that plugged into the special imaging proprietary hardware gear (that used WinXP-era drivers) had to have Win10 32-bit installed on them. So I made myself another USB key with Win10 32-bit (downloaded the ISO from Microsoft) and proceeded to install it no problem. The drivers also installed and it took me a few tries and some hair-pulling to get them to work, because at first Win10 recognized the device based on the generic controller chip that was in it. I had to keep going into Device Manager and finding a way to delete or inactivate it quickly and letting my driver install get in first, otherwise it would keep trying to re-register it using a Win10 driver. Anyways, it worked!
THE AFTERMATH:Now the entire office is upgraded to Win10, it still runs all the software that I had running on my WinXP machines... the same proprietary WinXP-era software (of which there is no good upgrade and that I need) is running fine. I also installed my old Microsoft Office PRO that I was using back on my WinXP machines... I know these can be vulnerable but I prefer not to buy MS Office again, and anyways I will probably migrate over to LibreOffice. I also will need to flip over to SMB2 now that the entire office is Win10... that will patch up another possible security hole.
One piece of software that I could NOT find an update to that works on Win10 has to do with managing the VOIP system (TalkSwitch) that runs the telephones in the office. The software that lets me configure the VOIP box is no longer available, the old version does not run on Win10 and it was using a ton of Java code, and the Java runtime it depends on cannot be installed on Win10. I tried whatever I could, even registering on Java as a tested to be able to grab older Java runtimes and no matter what I did, the software gave an error. So the solution? I keep one WinXP machine still available but OFF in the backroom, so that if I ever need to configure the TalkSwitch (now Fortinet) VOIP box I plug it into the network and bring up the software and can make changes. Otherwise, that machine is unplugged/dormant.
MORAL OF THE STORY...Win10 is not so bad as people think. I dreaded the upgrade, but it turns out even on my 10+ year old machines I was able to migrate and make old WinXP-era software work, even drivers that would have been impossible to update (and the equipment costs tens-of-thousands of dollars)... there was no way I was going to upgrade my hardware because of some stupid drivers. The solution was to use Win10 32-bit! I had a few issues with configuring 2-screen set ups but that was my fault because I didn't know about the Windows-Logo-key-P option to configure and switch screens. Also there was a delay in Windows 10 recognizing the NVidia graphics so it took 5 minutes after boot for it to actually install and let me configure it once and for all, and that was confusing because in those first 5 minutes I was scrambling to try to figure out why my video card is buggered up.
NOW WHAT DO I USE AT HOME?I'm using Linux for all my private use computers, laptops, etc. One of my kids has a Win7 machine that he plays lots of games on, like Roblox for example.... try as I might, I can't get that to work on Linux/WINE. I did get many of his games to work on my Linux machine (WINE) but Roblox and a few others just don't work. So he stays with Win7 to play games, but it is a dual-boot so it has Linux on it as well, and everybody else in the house is using Linux (some flavour of Ubuntu although I've got many distros that I play around with).
IN CONCLUSION...I think you should go to Win10 Pro and register it using a Win7 sticker, which Microsoft still appears to be honouring. If you are not ready to drop Microsoft altogether (and enter Linux-land) then that will be your best option. Unless you plan on being disconnected from the internet, you will face the same issues I had with WinXP in a few years. At some point you *WILL* need to move on with your life.
I would use the PRO version, and when I installed Win10 I chose "NO" to all of their extra features like Cortana, customized ads, blah blah blah. Everything was "NO" and also I did NOT register with a Microsoft account. Just set it up with a local account and don't forget your password. That way the machine is not tied to any online account. That can be harder later with regards to licensing and so on, migrating, etc. As you saw in my case, I was able to use my old computers (which I thought for sure would choke) to run Win10 smoothly, no problem, and I managed to save myself from upgrading 5-figure $$$ equipment because 32-bit Win10 still could handle WinXP-era drivers. So I see no good reason to stick to Win7 if you are just careful at how you install and properly version your Win10 installation. And the updates can be throttled down and controlled somewhat if you know what you are doing. Meanwhile, try to see if you can function in Linux and prepare yourself a machine or dual-booted install, so if Microsoft does anything crazy in the future you have a lifeboat to jump into.