That would be strange. If you have only a write-host this should work everytime.
How is you default agent settings configured?
I had only one systems with problems with plugin execution, there it was only the agent updater blocked by the anti virus software
I add my default config if i have no agent bakery only as reference if you want to compare.
Such config runs on some thousand hosts in my systems.
global:
only_from: MON-HOST-IP
async: yes
sections:
- check_mk
- spool
- plugins
- local
- winperf
- uptime
- systemtime
- df
- mem
- services
- msexch
- dotnet_clrmemory
- wmi_webservices
- wmi_cpuload
- ps
- fileinfo
- logwatch
ps:
enabled: yes
use_wmi: yes
# full_path: yes # only if needed
winperf:
enabled: yes
counters:
- 638: tcp_conn
- Terminal Services: ts_sessions
logwatch:
enabled: yes
logfile:
- 'Application': warm nocontext
- 'System': warn nocontext
- '*': off
plugins:
enabled: yes
execution:
- pattern : '$BUILTIN_PLUGINS_PATH$\windows_updates.vbs'
timeout : 3600
async : yes
cache_age : 90000
run : yes
- pattern : '$BUILTIN_PLUGINS_PATH$\mk_inventory.vbs'
async : yes
run : yes
- pattern : '$BUILTIN_PLUGINS_PATH$\windows_if.ps1'
async : yes
run : yes
- pattern : '$BUILTIN_PLUGINS_PATH$\windows_tasks.ps1'
async : yes
run : yes
- pattern : '$CUSTOM_PLUGINS_PATH$\*.*'
async : yes
timeout : 30
run : yes
- pattern : '$BUILTIN_PLUGINS_PATH$\*.*'
timeout : 30
run : no
- pattern : '*'
run : no
local:
enabled: yes
execution:
- pattern : '*.*'
run : yes