Page 1 of 1

Explorer.exe error - Update 2.6.016881

Published: February 4, 2025 - 2:55 PM
by pmuniv
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 :)

Re: Explorer.exe error - Update 2.6.016881

Published: February 7, 2025 - 11:28 AM
by dcardon
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

Re: Explorer.exe error - Update 2.6.016881

Published: February 10, 2025 - 1:14 PM
by pmuniv
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.