from my side, next week. just on a vacation trip 
.
and yes… thats right
Hi all,
can somebody reproduce this with an agent older than 2.4.0p3?
My current assumption is, that this bug was introduced with Werk #17543.
----EDIT----
linked the correct Werk. Sorry, it’s so hot…
Yes we‘re currently still using 2.4.0p2
downgrading the agent to 2.4.0p2 also fixes the problem for me
I just tested the fix for this bug and it works. I expect this to be available as of Checkmk 2.4.0p7.
(It was already too late for 2.4.0p6.)
The corresponding werk: Werk #17547: Fix Clean Installation in Windows Agent
Workaround for the time being
Install the agent without activating the option “Clean installation”.
If you need a “clean installation” nonetheless, simply delete the following folders before re-installing the agent:
C:\Program Files (x86)\checkmk\
C:\ProgramData\checkmk\
------EDIT------
Added Werk
4 Likes
check workaround = works, thx!
btw: how to mark it as solution?
Only the original poster and admins can mark the solution.
@RolandKL would that be ok if I mark @sebkir 's reply as a solution?
yes, it’s ok. thank you!
1 Like
Hi, only for a short follow up and info for me. Not fixed until now, right? 2.4.0p8 same behavior, option without “active cleas installation” also not seems to work anymore.
Tested on Win11, 24H2, 26100.4061
I posted the Werk, where this was fixed. After applying this, I could not reproduce the error anymore.
Reposting the link here: Werk #17547: Fix Clean Installation in Windows Agent
mmhhh i’m a little bit confused about this. thank you for your fast reply.
That is also the fix I used:
Agent 2.4 is not listening to Port 6556. I have installed an older Agent Version (2.3) and it works on Windows Server 2022 Datacenter .
did you allready test the standard installation process with agents of version 2.4p08?
where can we get agent 2.4p08 ?
we do have 2.4p08 and the problem still exist
1 Like
OK, good to hear from my point of view. @sebkir is this enough for you to give it a new try?
Before 2.4.0p8 the agent may clean installation too late thus unexpectedly destroying some files.
Since 2.4.0p8, agent executes cleaning immediately upon start and once. I could explain logic in details if you want
If something doesn’t work just check controller. If doesn’t help then ping me.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.