Setting the No_managed_code option to true causes the pool resource to execute on each Chef run

[larry-herz]

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

Pool resource runs on every Chef run when no_managed_code is set to true.

🥞 Cookbook version

8.2.8

👩‍🍳 Chef-Infra Version

18.x

🎩 Platform details

Windows Server 2019, 2022, 2025 in Azure

Steps To Reproduce

Steps to reproduce the behavior:

Create an iis_pool resource with the following:

iis_pool "rc-#{node['cust_env']}" do
no_managed_code true
pipeline_mode :Integrated
start_mode :AlwaysRunning
queue_length 1000
identity_type :SpecificUser
username service_user
password service_pwd
logon_type :LogonService
manual_group_membership true
idle_timeout '00:00:00'
idle_timeout_action :Terminate
shutdown_time_limit '00:01:00'
startup_time_limit '00:01:30'
periodic_restart_schedule ["#{reset_time}:00:00"]
action [ :add, :config, :start ]
end

Note that the user and password are for a domain service account with the proper permissions.

Let the Chef client run or kick off a client run manually.
Note that the config action executes on the iis_pool resource.
Verify that the app pool has been properly configured with 'No Managed Code'.
Run Chef again.
Note that the config action again executes (without actually changing anything).

🚓 Expected behavior

The second and subsequent Chef runs should not execute 'config' on the iis_pool resource.

➕ Additional context

The chef log shows these messages on each run:
WARN: ran into no managed runtime |
WARN: ran into no managed runtime C:\Windows\System32\inetsrv\appcmd.exe set config /section:applicationPools "/[name='<REDACTED>'].managedRuntimeVersion:"
- Configured Application Pool "iis_pool[<REDACTED>]"