First, quit requesting new certificates. That isn't solving the problem. You have gotten 4 3 certs today and once you reach 5 you will be rate limited for at least 34 hours. See: Rate Limits - Let's Encrypt
Second, do not use Certbot for new setups on Windows. The EFF dropped support for Windows about a year and a half ago. Switch to an ACME Client designed for Windows. The easiest to use is Certify the Web (has a gui) but posh-acme (Powershell) and simple-acme (cli) are both popular too.
As for the specific error that looks like a file permissions kind of problem. Someone else may wish to help with that but I don't think debugging an unsupported product on a new install is fruitful.
Note this announcement mentions win-acme but simple-acme is a drop-in replacement for that and has ongoing support. The principal maintainer of win-acme no longer works on that project and instead offers simple-acme.