Issue with installing 5.7

[Christian Sweitzer]

I've been trying to install 5.7.36, although the same problem happens with 5.7.38 on a few different VMs. It appears that a remote file that is being accessed to set up the initial my.ini file is causing a problem with the install. Everything installs fine, but when it goes to configure the server, I get the following error:

Beginning configuration step: Writing configuration file

Saving my.ini configuration file...
Saved my.ini configuration file.
Ended configuration step: Writing configuration file

Beginning configuration step: Updating Windows Firewall rules

Adding a Windows Firewall rule for MySQL on port 3306.
Attempting to add a Windows Firewall rule with command: netsh.exe advfirewall firewall add rule name="Port 3306" protocol=TCP localport=3306 dir=in action=allow
Ok.


Successfully added the Windows Firewall rule.
Ended configuration step: Updating Windows Firewall rules

Beginning configuration step: Adjusting Windows service

Attempting to grant Network Service require filesystem permissions.
Granted permissions.
Adding new service
New service added
Ended configuration step: Adjusting Windows service

Beginning configuration step: Initializing database (may take a long time)

Deleting the data directory from a previous (failed) configuration...
Attempting to run MySQL Server with --initialize-insecure option...
Starting process for MySQL Server 5.7.36...
Starting process with command: C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.7\my.ini" --console --initialize-insecure=on --lower-case-table-names=1...
2022-05-26T17:46:46.550868Z 0 [ERROR] Invalid value for named_pipe_full_access_group.
2022-05-26T17:46:46.553792Z 0 [ERROR] Aborting
Process for mysqld, with ID 2576, was run successfully and exited with code 1.
Failed to start process for MySQL Server 5.7.36.
Database initialization failed.
Ended configuration step: Initializing database (may take a long time)

The reason it's throwing that error is because it's putting the following line in the my.ini when it attempts to start it:

# The access control granted to clients on the named pipe created by the MySQL Server.
named-pipe-full-access-group=0.0

I reproduced it on a fresh Windows Server 2019 standard install as well. I can see using wireshark that it's downloading something from an akamai server so what I did was disabled all outgoing connections to port 443 and that fixed the issue. The problem is I cannot turn on the firewall on the production system I'm trying to get this installed on. I'll be able to work around it, but someone should take a look at whatever remote configuration strings are being pushed to installs.