Posted By Windows Embedded Team
On Windows Embedded 8 Standard, if you attempt to use WEDU to search for updates and the scan fails with the following error in the log (wedu.log):
Application Version: 188.8.131.52
=== EXCEPTION ===System.Runtime.InteropServices.COMException (0x8024002E): Exception from HRESULT: 0x8024002E at WUApiLib.IUpdateSearcher.BeginSearch(String criteria, Object onCompleted, Object state) at Microsoft.Wedu.Mu.UpdateTarget.CreateScanJob(IAsyncResult ar, Func`1& IsCompleted, Func`1& AsyncState, Func`1& CompletedSynchronously) at Microsoft.Wedu.Mu.AsyncResultAdapter..ctor(AsyncCallback outerCallback, Object outerState, JobCreateDelegate innerResultFunc, AsyncCallback innerCallback) at Microsoft.Wedu.Mu.UpdateTarget.<DoScan>d__3.MoveNext()
The most common cause of this error is the presence of the following registry key with a value other than 0:
The workaround for this error is to either delete this registry key or set the value to 0.
Comments Product Updates
In Standard 8, if you use Create Media from Image Configuration Editor (ICE), then create an .ISO from that media, you will not be able to use that .ISO to install Standard 8 on a device. Instead, you will get an error stating "Windows Setup failed to open catalog". This is because the media created by ICE is not designed to create an .ISO and thus does not include the .LOCK file that is required to created "locked" copies of the catalog database files.As a workaround, before creating the .ISO from the media file created by ICE, copy the .LOCK file located in C:\Windows Embedded Catalog\.lock, then proceed to create or burn the .ISO. This .LOCK file can also be located on the Windows Embedded 8 Standard DVD in the *\Catalog\.lock directory.
If you are running Windows Embedded Standard 7 (Standard 7) on some devices, you may need to manually set the processor state to 100% to avoid slow performance problems if your processor is not correctly responding to an increase in processor state. This is a known issue on Intel Haswell boards but can happen on other boards as well.
A work-around for this issue is to manually set both the minimum and maximum CPU values for processor state to 100%.
To manually set the CPU values: