Hello,
I wanted to report a problem we're experiencing (tested on 3 PCs, the issue is identical).
When the WAPT console is open, we have trouble switching between windows (when I click on an application in my taskbar, I often have to click a second time for it to open).
The problem only occurs when the WAPT console is open.
Do you have any ideas? Are
any of you experiencing the same issue?
Navigation problems between different Windows windows when the console is open
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
-
Guillaume_ccfd
- Messages: 24
- Registration: June 11, 2020 - 4:42 PM
Hello,
that's very strange indeed.
I've tested it on several PCs, including a brand new one (without a master image and with the factory version of Windows), and I have the same problem.
Sometimes I have to click four times on one of the open applications for it to move to the front of the other windows.
that's very strange indeed.
I've tested it on several PCs, including a brand new one (without a master image and with the factory version of Windows), and I have the same problem.
Sometimes I have to click four times on one of the open applications for it to move to the front of the other windows.
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Guillaume_ccfd,
we've already encountered this problem on a Lenovo machine, but we haven't been able to figure out the cause... Is it a Lazarus bug (the console development environment), a bug in our use of focus in the WAPT code (we're a bit too heavy-handed with it when importing packages), or a bug in certain mouse drivers or something else? We haven't been able to determine the cause.
In any case, having a management VM with the console configured in it is quite convenient, and the focus issue doesn't occur with an RDP connection. We'll see if that's a suitable solution.
Best regards,
Denis
we've already encountered this problem on a Lenovo machine, but we haven't been able to figure out the cause... Is it a Lazarus bug (the console development environment), a bug in our use of focus in the WAPT code (we're a bit too heavy-handed with it when importing packages), or a bug in certain mouse drivers or something else? We haven't been able to determine the cause.
In any case, having a management VM with the console configured in it is quite convenient, and the focus issue doesn't occur with an RDP connection. We'll see if that's a suitable solution.
Best regards,
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
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
-
Guillaume_ccfd
- Messages: 24
- Registration: June 11, 2020 - 4:42 PM
Hi Denis,
We're experiencing the bug at any time. It might be related to our docking station (D6000 / WD19), but I don't think so (my techs have the same issue on desktop PCs). I'm not sure what to tell you; the only thing we have in common is possibly that we're using DisplayPort.
I've tried quite a few things:
- Updating graphics drivers
- Updating all PC drivers
- Updating the docking station firmware
- Updating the BIOS.
I should record the console's behavior (it would be clearer), especially since we've tried isolating several elements (testing with a manual Windows installer, testing with a brand new MDT master image, testing with an older version of Windows 10).
I'm going to see if it would be possible to virtualize the console using APP-V (maybe that would work around the problem).
We're experiencing the bug at any time. It might be related to our docking station (D6000 / WD19), but I don't think so (my techs have the same issue on desktop PCs). I'm not sure what to tell you; the only thing we have in common is possibly that we're using DisplayPort.
I've tried quite a few things:
- Updating graphics drivers
- Updating all PC drivers
- Updating the docking station firmware
- Updating the BIOS.
I should record the console's behavior (it would be clearer), especially since we've tried isolating several elements (testing with a manual Windows installer, testing with a brand new MDT master image, testing with an older version of Windows 10).
I'm going to see if it would be possible to virtualize the console using APP-V (maybe that would work around the problem).
