Fail installing updates event log
Why there is no event log error for fail installing Windows updates in clients? SCCM push updates using ADR that create new software Update group each time. I noticed that some updates are failed to install in some servers because of maximum run time (it seems some servers take much time to install the update), however there is no event log shows this in windows event log. I checked Systems logs and filtered based on source of WindowsUpdateClient. the only log i got is event ID 43 (Installation Started: Windows has started installing the following update: ). and this keep repeating every time the update agent try to re-install the same update and it failed. I can see this in Updates History in Windows Updates settings window. Any idea how to catch this failure in event log in client machines? Regards Bachar
Windows 11 22H2 cumulative update fails 0x8007066A from Software Center
I've had a couple Windows 11 22H2 computers fail to install the cumulative update for last month and this month. The error code description is: The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade. Last month, I was able to download the CU and install the update manually with no issue. We have less than 10 W11 computers in our environment, but I would like to resolve this issue when installing updates from the Software Center. Any ideas what may be causing this?
Windows 10 1809 - Feature on Demand but prevent users from using WindowsUpdate
We use a SCCM 1810 environment. Beginning with Windows 10 1709, you can’t use WSUS to host Features on Demand and language packs for Windows 10 clients. Since we use Windows 10 1809 I noticed also RSAT and Language.Handwriting packages are not available anymore in WSUS/SCCM environment. Instead, you need to download them directly from Windows Update. So just used Get-WindowsCapability commandline and tried to install missing features and ran into 0x800f0954 error.After changing the GPO “Download repair content and optional…” we now receive a different error: 0x8024002e.Changing Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DisableWindowsUpdateAccess from “1” to “0” prevents error 0x8024002e and commandline: ”Get-WindowsCapability -Online | where name -like *.....* | Add-WindowsCapability -Online” works now. But now, our users are able to use “Windows Update – Check online for updates from Microsoft Windows” directly. I have something to consider that our users are now able to download and install Windows Feature Updates (f.e. 1809) over here. Is there any best practice how to prevent users from installing updates from WindowsUpdate directly?
WUAHandler.log reporting "Scan failed with error = 0x8024000f"
Hi, I'm using SCCM CB 1902 on Windows 2016. WUAHandler.log in all clients is reporting error since almost a month back. Following is the last few lines from log; Its a WSUS Update Source type ({7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A}), adding it. WUAHandler 13/07/2019 03:04:13 17304 (0x4398) This device is not enrolled into Intune. WUAHandler 13/07/2019 03:04:13 18876 (0x49BC) Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 13/07/2019 03:04:13 18876 (0x49BC) SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 13/07/2019 03:04:13 18876 (0x49BC) Existing WUA Managed server was already set (https://mycompany.contoso.com:8531), skipping Group Policy registration. WUAHandler 13/07/2019 03:04:13 17304 (0x4398) Added Update Source ({7BDC6D42-1BB8-4DBD-AD96-E288D3E2E79A}) of content type: 2 WUAHandler 13/07/2019 03:04:13 17304 (0x4398) Scan results will include all superseded updates. WUAHandler 13/07/2019 03:04:13 17304 (0x4398) Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 13/07/2019 03:04:13 17304 (0x4398) Async searching of updates using WUAgent started. WUAHandler 13/07/2019 03:04:13 17304 (0x4398) Async searching completed. WUAHandler 13/07/2019 03:13:16 22532 (0x5804) OnSearchComplete - Failed to end search job. Error = 0x8024000f. WUAHandler 13/07/2019 03:13:16 1880 (0x0758) Scan failed with error = 0x8024000f. WUAHandler 13/07/2019 03:13:16 1880 (0x0758) Tried googling about this error and found that it's about "Circular update relationships were detected in the metadata". I followed below thread and did exactly as suggested (yes, I had installed SUP around 3 months back for the sake of Dell driver and software updates) SCCM 2012 (1606) - OnSearchComplete - Failed to end search job. Error = 0x8024000f But above effort didn't help me. Error still appears and as a result, I'm not able to apply latest Microsoft updates. Any help to fix this issue?
WSUS Sync Failing
Within the last hour or so I have carried up a cleanup of our WSUS and reindexed the database as per this article https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/ Once complete I re-enable the SUP schedule and WSUS has not been able to Sync since. Our SCCM Version is 1702 with the hotfix, hosted on a Server 2012r2 system. WSUS content is within a SQL database. WCM.log; "System.Net.WebException: The request failed with HTTP status 403: Target service not allowed.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)" WsusCtrl.log does not seem to indicate any proxy related errors; "No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name ####### and Proxy Port ##"OFFICE 365 UPDATES ERROR 0X87D00668 & BITS ERRORS
Hello to all; I have been trying to figure out the cause to my problem for a couple of days now but I cannot seem to find what the issue is. So I am trying to push the Office 365 current channel update to our users (this works through an adr and previous updates where working as expected); however since this particular update (current channel update 2302 16130.20218) a number of workstations are reporting error 0X87D00668 and some are also reporting BITS errors: I am not sure if these errors might be related; and why is this happening? The update does not seem to get transfered to the client workstation; I can confirm that other updates are working fine (windows defender definition updates are being installed and windows 10 /11 updates) I have checked wuahandler logs and could not find any errors, the same with cas logs. I have also deleted the adr (including the downloaded office updates) and created the adr from scratch just to make sure I am getting a fresh start but the errors still crop up. I am at quite a loss at what else I can troubleshoot to get this update to actually install properly. Can anyone help me out please? Thanks in advance.Office 365 Pro Plus - Office Update "This product will not be updated."
Office 365 Pro Plus has started saying "This product will not be updated." on my managed PCs. I'm on Current Branch 1710 (first hotfix) and Office 365 Pro Plus Version 1711 (Build 8730.2127 Click-to-Run). Office 365 Pro Plus updates through ConfigMgrwere working fine as of... November? And I just never noticed that it broke? Might have been 1710 that broke it. Other updates work great. Has anyone ran into this issue? And have a good way to fix it?
