Since you're running the 64 bit version of win7 you're probably OK. I'm not sure the active attacks that Google spotted were all that massive to begin with. I Googled "windows 7 and chrome 0-day" [w/out quotes] and while there were loads of hits, every one seemed to be just rehashing the original Google blog post, with no added details. It didn't make the news at threatpost[.]com. Still, those running win7 32 bit should probably use the latest version of Chrome, because you know at least the vulnerability being exploited has been fixed. Google's security warnings usually go into greater detail, e.g. with the recent Apple OS bug they included proof of concept code -- without more info it probably wouldn't hurt to stick with Chrome in win7 64 bit either, but that's more a "just in case" sort of thing you may or may not want to bother with.
As far as getting folks to upgrade to win10, I'm starting to come around to the opinion that when it comes to individual consumers, Microsoft doesn't care that much any longer. The Windows teams that brought us Windows 7 & 8 no longer exist. The employees that used to check for & fix bugs are gone, replaced by Microsoft's reliance on Insiders as beta testers. The team responsible for Windows Kernel are now under the department handling their cloud services -- this very much core part of Windows is now being developed for their cloud servers, and reused by everyone else. IMHO, reflecting Microsoft's attitude towards individual consumers, while so far they've beta tested each version of win10 for 6 months, since they started focusing win10 development for their cloud servers, they've started beta testing more than a year before release.
While Microsoft does still make a huge portion of their revenue off win10 sales, PCs are a declining market, while Office 365 & their cloud services only grow. And they're making sure those last two work with everything, regardless the hardware or OS. Where in the past they were working on new versions of Windows for PCs, e.g. 7, 8, & 10, they've been trying to figure out how to compete against Chromebooks & Android phones -- they're working on at least the 3rd iteration of a much lighter weight OS.
So long story short, I'm not at all sure anyone's left at Microsoft who really cares what you or I run, Windows, MAC, Linux, Android etc. That IMHO also has a potential downside... a year from now when Microsoft has flipped the switch & win7 is no longer supported, I'm not expecting any kindness from their end. I still run XP in a VM, & thanks to a simple registry hack, still get updates, though they're for the POS [embedded] version. Unless you're a large biz paying lots of extra fees, I expect it'll be like Microsoft forgot win7 ever existed.
RE: upgrading from 7 to 10... it's both the best & worst upgrade I've experienced since 3.1. It's faster, easier, and more compatible with hardware than any prior version of Windows. Changing driver models & lack of bug squashing also makes every install & new version update a bit of a crap shoot -- the 2 new releases in 2018 were the worst ever in that respect, so much so that most PCs will probably still be running the spring rather than fall version when the next version appears in a couple of months.
The only way I know to sort of pre-qualify your hardware to see if & how well it'll run a version of win10, is using a Windows-To-Go drive, and it's not 100% reliable. You'll need a win10 ISO, which is easiest using the Windows ISO Downloader here: heidoc[.]net/joomla/ . You'll need a copy of Rufus: rufus[.]ie/ . And you'll want to use a SSD -- cheap ~120GB models are going for ~$20 -- & an external housing for it -- those start ~$5. When Rufus creates the Windows To Go drive it copies the win10 files to the drive & sets up the boot loader files. The 1st time you boot to the USB drive it'll search for & add any needed drivers -- it'll do that every time you boot to hardware it hasn't seen before. And then win10 will start, or not. I'm running a Ryzen 2 on a X470 board in this PC, and I got Not. I wound up having to use a working copy of win10 from a VM in a round-a-bout procedure I won't bore you with. The point I'd make is that if a Windows To Go drive works well, so should a regular win10 install -- if it doesn't go so well, installing win10 normally may or may not work.
