This article describes an issue that occurs when you pass a URL to the ShellExecuteEx API by using the lpFile parameter in Windows Embedded Compact 7. An update is available to resolve this issue. Before you install this update, all previously issued updates for this product must be installed.
Symptoms
Assume that you use the ShellExecuteEx API on a Windows Embedded Compact 7-based device. When you pass a URL to the API by using the lpFile parameter, the API fails and returns the error code 2(ERROR_FILE_NOT_FOUND).
Resolution
Software update information
Download information
The Windows Embedded Compact 7 Monthly Update (September 2014) is now available from Microsoft. To download this Windows Embedded Compact 7 monthly update, go to the following Microsoft Download Center website:
Windows Embedded Compact 7 updates
The kind of processor that each file applies to is visible in the name of each file in the "File information" section.
More Information
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
|
File name |
File size |
Date |
Time |
Path |
|---|---|---|---|---|
|
Shlexec.cpp |
44,030 |
17-Sep-2014 |
01:10 |
Premium\Private\Winceos\Osshell\Shellapi\Shexec |
|
Shexec.lib |
49,798 |
17-Sep-2014 |
09:12 |
Public\Common\Oak\Lib\X86\Retail |
|
Shexec.lib |
87,138 |
17-Sep-2014 |
11:15 |
Public\Common\Oak\Lib\X86\Debug |
|
Shexec.lib |
73,286 |
17-Sep-2014 |
09:12 |
Public\Common\Oak\Lib\X86\Checked |
|
Shexec.lib |
57,438 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Armv5\Retail |
|
Shexec.lib |
107,864 |
17-Sep-2014 |
11:09 |
Public\Common\Oak\Lib\Armv5\Debug |
|
Shexec.lib |
86,920 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Lib\Armv5\Checked |
|
Shexec.lib |
57,442 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Armv6\Retail |
|
Shexec.lib |
107,864 |
17-Sep-2014 |
11:10 |
Public\Common\Oak\Lib\Armv6\Debug |
|
Shexec.lib |
86,924 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Lib\Armv6\Checked |
|
Shexec.lib |
56,798 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Armv7\Retail |
|
Shexec.lib |
106,964 |
17-Sep-2014 |
11:10 |
Public\Common\Oak\Lib\Armv7\Debug |
|
Shexec.lib |
86,070 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Lib\Armv7\Checked |
|
Shexec.lib |
54,186 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Mipsii\Retail |
|
Shexec.lib |
97,954 |
17-Sep-2014 |
11:12 |
Public\Common\Oak\Lib\Mipsii\Debug |
|
Shexec.lib |
81,520 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Mipsii\Checked |
|
Shexec.lib |
54,244 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Mipsii_fp\Retail |
|
Shexec.lib |
98,012 |
17-Sep-2014 |
11:13 |
Public\Common\Oak\Lib\Mipsii_fp\Debug |
|
Shexec.lib |
81,582 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Mipsii_fp\Checked |
|
Shexec.lib |
50,832 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Sh4\Retail |
|
Shexec.lib |
91,300 |
17-Sep-2014 |
11:13 |
Public\Common\Oak\Lib\Sh4\Debug |
|
Shexec.lib |
77,500 |
17-Sep-2014 |
09:13 |
Public\Common\Oak\Lib\Sh4\Checked |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.
