No worries. It's fairly common (twice a month at least), but not easy to search out. Honestly, as you mentioned, this really needs to be baked into the certbot Windows deployment. It's a small price to pay in overhead to ensure IIS functionality right out of the box.
As far as I know, there isn't really a "Windows package", that's just regular certbot stuffed in a Windows installer (so it includes Python et c.). Also, certbot doesn't include code to detect webservers on Windows, so while it might sound simple ("Just add a XML to the challenge"), I'm not sure if it actually is so simple. That said, one might think what the harm is to add that XML file temporarily to the challenge dir even when the webserver is Apache or nginx..?
@Osiris pointed out that it's not the job of the certbot to detect or adjust the result based on the underlying server, and I can understand this.
Although I've asked that certbot handles this itself, this is really an implementation issue, and could be addressed in the Windows Installation Procedure. There's a hint of the problem in the "Important Note:", but this needs to be expanded.
For me, I tested that my server could serve files in the .well-known/acme-challenge directory. No problem there, and I naively used a test.html file. The problem wasn't serving files, the problem is serving files with no extension. The Important Note makes no mention of this.
The last part of the Important Note needs to read....
You will need to modify the IIS configuration to ensure that files without an extension inside /.well-known/acme-challenge are served by the webserver. This typically requires you to set a mime type for these files using a web.config file (provide link to example). To localise the configuration to the challenge directory, you can create the /.well-known/acme-challenge directory structure and create the web.config file there. Certbot won't remove the directory structure and web.config file if it already exists.
It worth also noting that variations in the parent application config (particularly auth, but also things like ISAPI filter order) and different versions of IIS actually mean you can't use one config file to rule them all. By far the best solution is to skip IIS and use http.sys to register a listener for challenges (in front of IIS in the http pipeline). This is what Certify The Web and win-acme do by default.