It sounds like you installed a CA certificate on your Windows 10 device, for Chrome to access a website. It also sounds that you used this cert to access a Google property, and now you're wondering if the certificate was indeed issued by Google.
Unless you've severely messed up your Windows/Chrome installation, you shouldn't need to install any additional certificates on Chrome to access Google properties. Hence, I'd be very very suspicious. (very!)
Fortunately, thanks to certificate transparency there's an easy way to see if the certificate is valid. Go to crt.sh and enter the SHA-256 or SHA-1 fingerprint of your cert. If the cert is valid:
- It'll be in the logs; and
- You can check the OCSP status to see if it's revoked
Then you might want to check the cert of the actual site you're visiting in the browser using the same methodology. The 'leaf' certificate issued to Google has to be on the logs, if it isn't -- run!
It's unlikely that a rogue certificate issued to Google, that was in the logs wouldn't have been revoked by now.
Just to be extra safe, you can check against other certificate logs as well (Facebook have a wonderful API) and censys provide one as well.