Waptexit display bug under Windows 10 1903

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
erickeke
Messages: 16
Registration: June 12, 2019 - 10:33

June 12, 2019 - 10:46

Good morning,

Since the 1903 update, waptexit.exe has a strange display. But this only happens when the machine is shut down. If you run it manually in Windows, there are no problems
IMG_20190612_100053.jpg
IMG_20190612_100053.jpg (53.98 KB) Viewed 10095 times
I tried it on a machine in Full HD with a dpi zoom, and one without HD or zoom: same result.

I'm looking for differences in Windows 1903, perhaps a graphics rendering service that stops and on which the form display depends?

In 1809 I had a different display bug, but only on the first restart after installation:
IMG_20190604_164449.jpg
IMG_20190604_164449.jpg (58.98 KB) Viewed 10095 times
Wapt version 1.7.4.6077 (client and server) same when installing nightly 1.7.4.6093.

Sincerely
erickeke
Messages: 16
Registration: June 12, 2019 - 10:33

June 13, 2019 - 08:58

Same problem following an update on another machine with an integrated Intel graphics card.
Christophe0110
Messages: 53
Registration: June 11, 2019 - 12:04

June 13, 2019 - 1:03 PM

I confirm, I have the same problem (tested on a virtual machine running an updated Windows 10).
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 14, 2019 - 5:19 PM

Hello Christophe0110,
Christophe0110 wrote: June 13, 2019 - 13:03 I confirm, I have the same problem (tested on a virtual machine in updated Windows 10).
The topic was also raised on the mailing list, and Alexandre responded here: https://lists.tranquil.it/pipermail/wap...03259.html
Basically, there's a bug in Windows 1903. WAPT isn't the only one affected; with this new version, the text doesn't appear in the graphical interfaces using the shutdown script once someone has logged into the machine...

If you've found a workaround, we'd love to hear it. For now, we'll open a bug report with Microsoft and look for a solution in the meantime.

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Christophe0110
Messages: 53
Registration: June 11, 2019 - 12:04

August 27, 2019 - 11:05

Hello,

Has a solution been found for this display problem that affects all our client workstations updated to W10 1903?

Best regards,
Christophe.
User avatar
vcardon
WAPT Expert
Messages: 278
Registration: Oct 06, 2017 - 10:55 p.m.
Location: Nantes, France

August 27, 2019 - 11:45

Christophe0110 wrote: August 27, 2019 - 11:05 Is there a solution found for this display problem which affects all our client workstations updated to W10 1903?
The bug is unfortunately in Windows, so a fix will almost certainly come with a future version of Windows.

Sincerely.

Vincent
Vincent CARDON
Tranquil IT
Christophe0110
Messages: 53
Registration: June 11, 2019 - 12:04

August 28, 2019 - 10:08

Well... if we have to wait for Microsoft, we'll probably have to wait for Windows 11 to be released... :lol:

I don't see many people talking about this problem online, so I'm not sure it's a priority for them, unfortunately... :?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 26, 2019 - 11:48

There's clearly something new:

https://answers.microsoft.com/en-us/win ... edc6b8b1b9
Looks like this issue is fixed in Windows 10 1909 Preview builds. I have tested on Windows 10 Insider Preview build 18990.1(vb_release). 190921-1704. Powershell now shows the text properly when shutdown scripts are being executed.
User avatar
Mathieu
Messages: 91
Registration: August 18, 2016 - 10:24

September 27, 2019 - 09:21

For me, WAPTEXIT doesn't even launch after rebooting the computer on a machine running Windows 10 version 1903
- WAPT 2.2.3.12463 Enterprise
- Debian 9.9
- Windows 10 21H2 & Windows 11 22h2
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 28, 2019 - 12:06

Can you tell us more?

No more launches?

We're all on version 1903 at the office and we don't have this problem.
Locked