Glad we've got this sorted 
I try to summarize what we did during the length of this thread.
We configured your FB to distribute 192.168.178.46 as local DNS server to its DHCP clients via Heimnetz | Netzwerk | Netzwerkeinstellungen | IPv4-Adressen
We also got rid of a possible DNS loop by ensuring your FB is configured to use its default ISP-provided DNS servers as upstream DNS servers via Internet | Zugangsdaten | DNS-Server. Specifically, we removed Pi-hole from these settings, as to avoid closing the loop with your Pi-hole using your FB as one of its upstream servers.
We verified that your Pi-hole is up and running at 192.168.178.46, it is correctly configured to listen on its wlan0 interface and showing no signs of port conflicts.
However, Pi-hole still didn't register any incoming DNS requests from your Windows PC in pihole.log.
Monitoring DNS a the network level did prove that your RPi running Pi-hole received DNS packets, suggesting that something dropped these packets before they would reach Pi-hole, most likely a firewall.
Indeed, your firewall wasn't configured to allow correct handling of DNS requests.
(Thanks go to @deHakkelaar for jumping in at the late hours when I was grabbing some sleep 
)
Adding corresponding rules finally made your Pi-hole operational.
As a firewall on your RPi was blocking DNS traffic per se, it seems unlikely that your phone was using Pi-hole as its DNS server when it was able to resolve hostnames while your PC wasn't.
Hence, I'd suspect your phone to still bypass Pi-hole.
You might want to check your IPv6 settings in your FB.
Unfortunately, even with a correct router IPv6 configuration, it is not uncommon for phones to use your ISP-provided DNS directly.
This can be attributed to IPv6 auto configuration which allows and in fact encourages a device's network integration at the complete discretion of the device, rather than leaving it to the central authority of a DHCP server.
The amount of ads that is getting blocked will depend entirely on the blocklists and reg ex filters you chose to employ. The default lists shipping with Pi-hole already do a decent job.
If you want to expand on that, go for quality and content, not for sheer volume.
WaLLy3k’s Blocklist collection is a good starting point, and Steven Black’s hosts files do a good job in grouping blocking lists by topics.
Focus your attention on the sites you visit regularly - if they still show ads, go tune your blacklists until satisfied. After all, it’s of little use having a domain on your block list that you never visit.
If you are still seeing ads in places you visit regularly, How do I determine what domain an ad is coming from? has good insights on how to decide what sites to block.
Personally, I use a browser extension (uBO Scope ) to help me determine what sites a web page contacts and tries to contact in the background.
As for Youtube, blocking embedded ads is almost impossible, as the bulk of them is getting served by the same domain as the content.