none
WEPOS 7 Cannot Update RRS feed

  • Question

  • WEPOS 7 SP 1 (v 6.1.7601)

    Last successful update was at 6.16.16.

    Since then an Update (automatic or manual) does not discover any updates. When starting manually, it's checking for updates and the routine can run for days without discovering any and NOT generating an error.  I did try most of the solutions from here: https://support.microsoft.com/en-us/help/2509997/you-can-t-install-updates-on-a-windows-based-computer

    I cannot install an update to clean winsxs folder since it is a WEPOS

    It is not a firewall/network issue, since other operating systems on the same network are updating with no problem.

    Here is a partial log covering the time when I started an update yesterday (still running). Please note the last line. If I leave it running for days, a new line (about timeout) would be added at the same time. Could someone look at it and let me know what might be wrong there. Appreciate the response.

    2017-03-16 14:20:39:013 4176 105c Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false 2017-03-16 14:20:39:013 4176 105c Handler ::::::::: 2017-03-16 14:20:39:013 4176 105c Handler :: END :: Handler: Command Line Install 2017-03-16 14:20:39:013 4176 105c Handler ::::::::::::: 2017-03-16 14:20:39:013 952 104c Agent LogHistory called. idUpdate={142396A9-E97C-42D3-A01B-53313694669D}.501, resultMapped=0, resultUnMapped=0 2017-03-16 14:20:39:013 952 8e0 AU Piggybacking on an AU detection already in progress 2017-03-16 14:20:39:013 952 104c Agent ********* 2017-03-16 14:20:39:013 940 16c0 COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = wusa] 2017-03-16 14:20:39:013 952 104c Agent ** END ** Agent: Installing updates [CallerId = wusa] 2017-03-16 14:20:39:013 952 104c Agent ************* 2017-03-16 14:20:39:013 940 16c0 COMAPI - Install call complete (succeeded = 1, succeeded with errors = 0, failed = 0, unaccounted = 0) 2017-03-16 14:20:39:013 940 16c0 COMAPI - Reboot required = No 2017-03-16 14:20:39:013 940 16c0 COMAPI --------- 2017-03-16 14:20:39:013 940 16c0 COMAPI -- END -- COMAPI: Install [ClientId = wusa] 2017-03-16 14:20:39:013 940 16c0 COMAPI ------------- 2017-03-16 14:23:04:858 940 4f0 COMAPI ----------- COMAPI: IUpdateServiceManager::RemoveService ----------- 2017-03-16 14:23:04:858 940 4f0 COMAPI - ServiceId = {5b10d430-96c6-4c31-8306-8f210a010d74} 2017-03-16 14:23:04:889 940 4f0 COMAPI IUpdateService removing volatile scan package service, serviceID = {5B10D430-96C6-4C31-8306-8F210A010D74} 2017-03-16 14:23:04:889 952 3c8 Agent WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014 2017-03-16 14:23:04:889 940 4f0 COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014 2017-03-16 14:23:26:302 952 8e0 AU Initiating Install-at-shutdown 2017-03-16 14:23:26:302 952 8e0 Shutdwn user declined update at shutdown 2017-03-16 14:23:26:302 952 8e0 AU Successfully wrote event for AU health state:0 2017-03-16 14:23:26:302 952 8e0 AU AU initiates service shutdown 2017-03-16 14:23:26:302 952 8e0 AU ########### AU: Uninitializing Automatic Updates ########### 2017-03-16 14:23:26:302 952 1028 Agent * WARNING: Failed to filter search results, error = 0x8024000B 2017-03-16 14:23:26:302 952 1028 Agent ********* 2017-03-16 14:23:26:302 952 1028 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2017-03-16 14:23:26:302 952 1028 Agent ************* 2017-03-16 14:23:26:302 952 1028 Report REPORT EVENT: {26A9538E-F787-4BCE-A896-C34A28904565} 2017-03-16 14:20:39:013-0400 1 183 101 {142396A9-E97C-42D3-A01B-53313694669D} 501 0 wusa Success Content Install Installation Successful: Windows successfully installed the following update: Hotfix for Windows (KB947821) 2017-03-16 14:23:27:082 952 8e0 Service ********* 2017-03-16 14:23:27:082 952 8e0 Service ** END ** Service: Service exit [Exit code = 0x240001] 2017-03-16 14:23:27:082 952 8e0 Service ************* 2017-03-16 14:25:20:714 956 fc4 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0400) =========== 2017-03-16 14:25:20:730 956 fc4 Misc = Process: C:\Windows\system32\svchost.exe 2017-03-16 14:25:20:730 956 fc4 Misc = Module: c:\windows\system32\wuaueng.dll 2017-03-16 14:25:20:714 956 fc4 Service ************* 2017-03-16 14:25:20:730 956 fc4 Service ** START ** Service: Service startup 2017-03-16 14:25:20:730 956 fc4 Service ********* 2017-03-16 14:25:20:808 956 fc4 Agent * WU client version 7.6.7601.19161 2017-03-16 14:25:20:808 956 fc4 Agent * Base directory: C:\Windows\SoftwareDistribution 2017-03-16 14:25:20:808 956 fc4 Agent * Access type: No proxy 2017-03-16 14:25:20:808 956 fc4 Agent * Network state: Connected 2017-03-16 14:25:21:120 956 f90 Report CWERReporter::Init succeeded 2017-03-16 14:25:21:120 956 f90 Agent *********** Agent: Initializing Windows Update Agent *********** 2017-03-16 14:25:21:120 956 f90 Agent * Prerequisite roots succeeded. 2017-03-16 14:25:21:120 956 f90 Agent *********** Agent: Initializing global settings cache *********** 2017-03-16 14:25:21:120 956 f90 Agent * WSUS server: <NULL> 2017-03-16 14:25:21:120 956 f90 Agent * WSUS status server: <NULL> 2017-03-16 14:25:21:120 956 f90 Agent * Target group: (Unassigned Computers) 2017-03-16 14:25:21:120 956 f90 Agent * Windows Update access disabled: No 2017-03-16 14:25:21:135 956 f90 DnldMgr Download manager restoring 0 downloads 2017-03-16 14:25:21:151 956 f90 AU ########### AU: Initializing Automatic Updates ########### 2017-03-16 14:25:21:151 956 f90 AU AU setting next detection timeout to 2017-03-16 18:25:21 2017-03-16 14:25:21:151 956 f90 AU # Approval type: Pre-install notify (User preference) 2017-03-16 14:25:21:151 956 f90 AU # Auto-install minor updates: No (User preference) 2017-03-16 14:25:21:494 956 fc4 Report *********** Report: Initializing static reporting data *********** 2017-03-16 14:25:21:494 956 fc4 Report * OS Version = 6.1.7601.1.0.65856 2017-03-16 14:25:21:494 956 fc4 Report * OS Product Type = 0x00000041 2017-03-16 14:25:21:510 956 fc4 Report * Computer Brand = Hewlett-Packard 2017-03-16 14:25:21:510 956 fc4 Report * Computer Model = HP RP5800 Base Model Retail System 2017-03-16 14:25:21:510 956 fc4 Report * Bios Revision = J20 v02.18 2017-03-16 14:25:21:510 956 fc4 Report * Bios Name = Default System BIOS 2017-03-16 14:25:21:510 956 fc4 Report * Bios Release Date = 2014-08-23T00:00:00 2017-03-16 14:25:21:510 956 fc4 Report * Locale ID = 1033 2017-03-16 14:25:23:616 956 f90 AU Successfully wrote event for AU health state:0 2017-03-16 14:25:23:616 956 f90 AU Initializing featured updates 2017-03-16 14:25:23:616 956 f90 AU Found 0 cached featured updates 2017-03-16 14:25:23:616 956 f90 AU Successfully wrote event for AU health state:0 2017-03-16 14:25:23:616 956 f90 AU Successfully wrote event for AU health state:0 2017-03-16 14:25:23:616 956 f90 AU AU finished delayed initialization 2017-03-16 14:25:23:616 956 fc4 AU ############# 2017-03-16 14:25:23:616 956 fc4 AU ## START ## AU: Search for updates 2017-03-16 14:25:23:616 956 fc4 AU ######### 2017-03-16 14:25:23:631 956 fc4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {32D01818-B04E-4766-9BFE-F10782C2A0A6}] 2017-03-16 14:25:23:772 956 6b0 Agent ************* 2017-03-16 14:25:23:772 956 6b0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2017-03-16 14:25:23:772 956 6b0 Agent ********* 2017-03-16 14:25:23:772 956 6b0 Agent * Online = No; Ignore download priority = No 2017-03-16 14:25:23:772 956 6b0 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1" 2017-03-16 14:25:23:772 956 6b0 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service 2017-03-16 14:25:23:772 956 6b0 Agent * Search Scope = {Machine} 2017-03-16 14:25:26:377 956 f90 AU Triggering AU detection through DetectNow API 2017-03-16 14:25:26:377 956 f90 AU Will do the detection after current detection completes

    2017-03-17 09:39:09:005 956 fc4 AU AU setting next sqm report timeout to 2017-03-18 13:39:09


    Friday, March 17, 2017 2:18 PM

All replies

  • You mean Windows Embedded POSReady 7. Sometimes the Windows update cache gets corrupted. I forget the exact steps to clean this up, but this site looks like it has the answer:

    http://www.incrediblelab.com/failure-configuring-windows-updates-fixed/

    Step 3 discusses deleting the data cache

    As a check if you did a clean install of POSReady 7, does the same issue happen? If you still cannot get this to work, you might want to raise this question directly to Microsoft.


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Friday, March 17, 2017 3:13 PM
    Moderator
  • Thank you Sean for replying. I did clear cache before and it did not help. But I have not tried a fresh install. It's on a freshly loaded ghost image though, which was fine in past June. I'll try fresh install next week, but I think it would work. But again I have number of computers running with the same image loaded (none of them are updating). Not sure what might have happened.

    Thanks again

    Friday, March 17, 2017 7:48 PM
  • Clearing the cache is what worked for me in the past. Why this is happening is a bit concerning. This might be a question to be elevated to Microsoft.

    Update: just a thought if this is on a business network, check to see if there is a router issues. You might want to try a different Windows OS (7, 8.1 or 10) to see if Windows Update is working on these too.


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com


    Saturday, March 18, 2017 3:17 AM
    Moderator
  • There is no problem updating other operating systems. Something might have happened after the last update in June. I do update one computer and then distribute an image of it as needed. I also had the same problem with image for other hardware platform (same OS), which I finally resolved. But this one is quite stubborn. I would try a fresh install some time next week and post the results.

    Thank you.

    Saturday, March 18, 2017 5:37 AM