Explorer.exe error - Update 2.6.016881

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Answer
pmuniv
Messages: 2
Registration: February 4, 2025 - 1:27 PM

February 4, 2025 - 2:55 PM

Hello, :)

Following the 2.6.016881 update (but is it really related?), in the console (under Windows), when I try to open any package folder, I get the error message:

"Failed to execute "C:\users\profilename\windows\explorer.exe" followed by the directory containing the package files.

I should mention that the environment variables are correct.

Is there any way to fix this problem?

Good afternoon everyone :)
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

February 7, 2025 - 11:28

Hello Patrice,

In WAPT, we use the standard Win32 API SHGetFolderPathW with the correct CLSID to retrieve the c:\windows directory. However, the Win32 API is apparently trying to perform filesystem virtualization even when we tell it not to (in certain cases...). For your information, filesystem virtualization is a Windows feature that adapts the directory structure to allow older programs to run on modern versions of Windows. This can be very useful for backward compatibility, but sometimes it creates more bugs than it solves.

We've changed the call to avoid this problem. This change will be included in the next version.

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
pmuniv
Messages: 2
Registration: February 4, 2025 - 1:27 PM

February 10, 2025 - 1:14 PM

Hello, :)

First of all, a big thank you for the prompt reply :)!

While waiting for the update, there's a simple, albeit conventional, way to avoid being in a "blocked" situation: simply copy the explorer.exe file to c:\users\yourusername\windows.

This might be a very temporary (and admittedly not very elegant) solution, but it's somewhat effective.

Thanks again.

Best regards.
Answer