Squid by default only does http sites. The majority of stuff these days is https. As such you are not configured for that. I will also suggest that it isn't the easiest thing in the world for a new user to do. I've been working on a docker squid for awhile as a transparent https proxy. I had it working for awhile, then it stopped. Now I can't get it working again. I lost interest. Even when it was working there was a fair number of sites that just wouldn't work with it. Windows global proxy setting is both http & https. So naturally if the proxy can't do the https then you are stuck.
What you are trying to do is a Man in the Middle attack so to speak. Requires certificates on the squid proxy & on machines you want to use it. Even with the certs when it was working Windows Updates never cached, among other things.
There are countless guides around the internet. Go to the source as far as I'm concerned.
https://wiki.squid-cache.org/
I'm interested to know if you succeed. Getting it working the first time was a long trial and error thing for me.
*EDIT*
Here is my working (at the time) configuration for it. Feel free to examine. I'm hoping it can help you.
https://gitlab.com/jmgibson1981/home...ssl/squid.conf
In the squid ssl folder you can also find the scripts for the Docker, and the startup script that auto creates the certs.