Timeout caused by wait for mutex (PE035) only on Windows Server 2008 R2
Modified on 2025-06-10 22:53:53 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Important: We no longer maintain this article. The information might be out of date.
Hello,
I use the Windows Update Status Sensor for my virtuel Windows Server 2008 R2 / 2012 R2. The sensors worked fine on both. Since few weeks the sensors on all Windows Server 2008 R2 throw the PE035 error: Timeout caused by wait for mutex.
Tested: Run the LastWindowsUpdateSensor.exe for a Windows Server 2008 R2 in a CommandLine. The executions are successful, but run between 15 and 30 minutes and the svchost.exe get up to 100% CPU.
In comparison to 2012 R2 the execution run only 30 seconds.
Does anybody has an idea?
Thanks.
Article Comments
Hello,
The mutex handling of the Windows Update Sensor will be improved in future versions of PRTG. This new version is integrated in the latest preview version of PRTG at the moment, so it should be available within the stable version 15.x.19.x
Aug, 2015 - Permalink
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Hello,
The mutex handling of the Windows Update Sensor will be improved in future versions of PRTG. This new version is integrated in the latest preview version of PRTG at the moment, so it should be available within the stable version 15.x.19.x
Aug, 2015 - Permalink