Renewal stopped working, upgraded to last version, still the same.

[wildlud]

[VERB] Connection OK!
[DBUG] Running as administrator
[DBUG] IIS not detected
[DBUG] Scheduled task looks healthy
[INFO] Check the manual at https://simple-acme.com

this causes error on renewal : Source plugin IIS bindings is disabled. Unsupported version of IIS detected.

Root cause
[VERB] IIS ServerManager exception: Filename: \?\C:\Windows\system32\inetsrv\config\applicationHost.config
Error: Cannot read configuration file

Thank you for help !

[WouterTinus]

I can't offer much more than AI answers for this:

The error "Filename: \?\C:\Windows\system32\inetsrv\config\applicationHost.config Error: Cannot read configuration file" indicates that IIS (Internet Information Services) is unable to access or read the applicationHost.config file, which is crucial for configuring IIS settings. This problem often arises due to permission issues, file corruption, or incorrect file paths. To resolve this, ensure the IIS user account has the necessary read permissions to the applicationHost.config file, and verify the file's integrity and location.

Here's a breakdown of the problem and solutions:

1. Understanding the Error:
   applicationHost.config:
   This file is the main configuration file for IIS, containing settings for websites, applications, application pools, and more.
   \\?\ prefix:
   The \\?\ prefix indicates that the path is a "raw" path, which can sometimes be related to issues with long or complex file paths.
   Cannot read configuration file:
   This means IIS cannot access or parse the content of the applicationHost.config file, preventing it from starting or properly configuring the server.

2. Common Causes:
   Insufficient Permissions:
   The user account running IIS (often IIS AppPool{ApplicationPoolName}) might not have the necessary read permissions on the applicationHost.config file or the C:\Windows\System32\inetsrv\config directory.
   File Corruption:
   The applicationHost.config file could be corrupted due to various reasons, including improper editing or system errors.
   Incorrect File Path:
   While less common, there might be an issue with how IIS is resolving the file path, potentially due to incorrect environment variables or symbolic links.
   File Locking:
   In rare cases, another process might be holding an exclusive lock on the file, preventing IIS from accessing it.

3. Solutions:
   Granting Permissions:
   Locate the C:\Windows\System32\inetsrv\config directory.
   Right-click the directory and select "Properties".
   Go to the "Security" tab.
   Click "Edit" then "Add".
   Enter the IIS user account (e.g., IIS AppPool{ApplicationPoolName}) or the IIS_IUSRS group.
   Check the "Read" permission box and click "OK".
   Ensure the changes are applied to the file by checking the "Inherit from parent the permission entries that apply to child objects" box in the Security tab.
   Repeat the process for the applicationHost.config file itself if necessary.
   Restoring from Backup (if available):
   If you have a backup of the applicationHost.config file, restore it to the C:\Windows\System32\inetsrv\config directory.
   IIS has a built-in history feature in the C:\inetpub\history directory that can be used to restore older versions of the configuration file, according to Plesk support.
   Verifying File Integrity:
   Open the applicationHost.config file with a text editor (like Notepad++) to check for any obvious errors or corruptions.
   If you suspect corruption, consider using a backup or a known good configuration from another server.
   Resetting IIS:
   Open an elevated command prompt (run as administrator).
   Run the command iisreset.
   Checking IIS Manager:
   Open IIS Manager (type inetmgr in the Run dialog).
   Expand the server node, then "Sites".
   Right-click on the site and select "Manage Web Site" -> "Advanced Settings".
   Verify the physical path and application pool settings.

[wildlud]

Well, i'm affraid the problem is from windows update because the file itself is not here.
When i try to restore it's last backup, either by hand or using the command appcmd restore backup "backupname" it fails. As if something was preventing the writting of such file. For now i didn't find the solution, tried to stop windows defender...

Bytw i't's under WINDOWS 2012.