[SOLVED] WaptExit Windows 7 Bug
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
That's exactly what I have.
Okay, so it's the retrieval of the current update state that's failing, not the subsequent event handling.
That's not the same issue I've encountered.
That's not the same issue I've encountered.
Tranquil IT
I made a change in waptexit to address a potential blocking scenario (a thread that might not be initialized even though another thread could try to start it).
Since I don't have an easily reproducible example here, could you test it on your problematic cases?
https://wapt.tranquil.it/wapt/nightly/w ... tsetup.exe
Since I don't have an easily reproducible example here, could you test it on your problematic cases?
https://wapt.tranquil.it/wapt/nightly/w ... tsetup.exe
Tranquil IT
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
With this version (1.7.4.6125), I'm definitely having fewer problems.
I've performed four shutdowns without any issues.
I then installed some software, again with four shutdowns without any problems.
Then I forgot to install a package, and the PC crashed again when I shut down.
I've noticed that with this version, the "WAPTService" takes longer to start when Windows boots.
When WaptExit crashes, Windows still shuts down after about three hours.
However, I've seen an improvement with this version (1.7.4.6125), because before, I was experiencing a crash about half the time.
I've performed four shutdowns without any issues.
I then installed some software, again with four shutdowns without any problems.
Then I forgot to install a package, and the PC crashed again when I shut down.
I've noticed that with this version, the "WAPTService" takes longer to start when Windows boots.
When WaptExit crashes, Windows still shuts down after about three hours.
However, I've seen an improvement with this version (1.7.4.6125), because before, I was experiencing a crash about half the time.
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
I can confirm that I've only experienced one crash so far.
This version fixes my problem.
Will there be a new version of WAPT for Windows servers very soon, or do I need to integrate this package into my current version (1.7.4.6077)?
This version fixes my problem.
Will there be a new version of WAPT for Windows servers very soon, or do I need to integrate this package into my current version (1.7.4.6077)?
We will release an official version tonight or tomorrow...
Tests on real infrastructure are still underway.
Tests on real infrastructure are still underway.
Tranquil IT
A quick question about this.
I'm also experiencing random, blocking crashes when shutting down.
My server is running version 1.7.4.6077.
Can I install a client running version 1.7.5.6190 without any issues, or will that cause compatibility problems?
I'd prefer not to modify the server for the time being.
(Community version)
Regards
I'm also experiencing random, blocking crashes when shutting down.
My server is running version 1.7.4.6077.
Can I install a client running version 1.7.5.6190 without any issues, or will that cause compatibility problems?
I'd prefer not to modify the server for the time being.
(Community version)
Regards
You can use the stable client version 1.7.4.6165, which includes the fix,
or try the nightly build 1.7.4.6178, which includes other fixes.
Version 1.7.5 is not stable... in fact, we don't have version 1.7.5.6190...
or try the nightly build 1.7.4.6178, which includes other fixes.
Version 1.7.5 is not stable... in fact, we don't have version 1.7.5.6190...
Tranquil IT
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hello,
I am currently using version 1.7.4.6165 which, for the moment, no longer gives me any shutdown problems on either Windows 7 or Windows 10.
I am currently using version 1.7.4.6165 which, for the moment, no longer gives me any shutdown problems on either Windows 7 or Windows 10.
