This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
On Windows 7 pro x64 with SP1, I've been getting this message when rebooting after installing KB2685811 ("Update for Kernel-Mode Driver Framework version 1.11 for Windows 7 for x64-based Systems"): "Failure configuring Windows update". All updates from last Tuesday (13/Nov/2012) were installed correctly, only this one fails.
I tried...
Rebooting, F8 and then using repair. It detected no errors.
Installing the patch with the antivirus (Avira free) disabled, which changed nothing.
Downloading the update manually and installing it. Made no difference.
Installing KB947821, found here: https://www.microsoft.com/en-us/download/details.aspx?id=20858
I then found a file I had downloaded yesterday (can't remember where from) called windowsupdate.diagcab
I ran it and it detected 2 errors:
[a] Potential Windows update database error detected (0x80070002)
[b] Problem with Background Intelligent Transfer Service (BITS)
I eventually solved [a] and [b] with MicrosoftFixit50202.msi, but not the original problem. I still get the "Failure configuring Windows update" message after rebooting, once the installation reaches 61%.
There were a couple of other things I did, but I can't remember exactly what they were...
Any help is appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I had the same problem and found a solution.
For this update, TEMP file location should be set to default C:.
I changed Temp file location from RAM disk to C:\ for this update and it worked. Thereafter I changed the Temp file location back to RAM disk.
Hi all!
So based on two recent cases with KB2685811 not installing.
As pointed by Wei Mao you need to inspect cbs.log (i use Notepad ++ for the job)
In the first case I had error with 5 files in C:\windows\winsxs\temp that couldn't be deleted so I booted with Ubuntu CD and deleted all content of C:\windows\winsxs\temp which then allowed for the update to install fine.
Second case - with Wei Mao help who pointed to error:
Error 80 in Function CMofLexer::CMofLexer line 615 C:\Windows\system32
\wbem\Wdf01000.mof (1): error in my cbs.log
I again booted with Ubuntu CD, renamed the following files C:\Windows\system32
\wbem\Wdf01000.mof and C:\Windows\system32
\wbem\Wdf01000uninstall.mof (i didn't delete them just in case)
then the problematic update installed fine.
So inspect your cbs.log and hope for the best :)
Peter
Tried these along with the moving the temp folder. Still doesn't work. I am no expert and this is very frustrating.
Bill
My problem was solved by changing back the Temp folder to the Windows partition (I had placed it in a Ramdisk), so I can't reproduce it.
I did check cbs.log though. The first entry is from the 21st of November (the problem happened on the 13th and the solution on the 16th).
Hi,
I am still having problems to install KB2685811 and KB2592687 on my Windows 7 HP (32-Bit). Both fail with 8007007E. After several threads pointed to the CBS.log file and in some thread I found a hint for the WMIDiag tool (http://www.microsoft.com/en-us/download/details.aspx?id=7684) I used both to try to find something new on this issue.
And indeed, the CBS log file indicates problems related to invalid packages. There are very much log lines like those:
=====================================
2012-11-24 23:13:13, Info CBS Session: 30263952_3850414288 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-11-24 23:13:13, Info CBS Session: 30263952_3850414289 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-11-24 23:13:13, Info CBS Session: 30263952_3850414290 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-11-24 23:13:13, Info CBS Session: 30263952_3850514432 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-11-24 23:13:13, Info CBS Session: 30263952_3850514433 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-11-24 23:13:13, Info CBS Session: 30263952_3850514434 initialized by client WindowsUpdateAgent.
2012-11-24 23:13:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
=====================================
(I can send the full logfile If someone likes to see it - as attaching is not possible here :-( )
As said, I also ran the WMIDiag tool and it pointed to the same problems as seen in the CBS logile. Here is the report. It points out the specific problems, but how to solve it?
=====================================
.2026 23:02:50 (0) ** WMIDiag v2.1 started on Donnerstag, 22. November 2012 at 23:02.
.2027 23:02:50 (0) **
.2028 23:02:50 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.2029 23:02:50 (0) **
.2030 23:02:50 (0) ** This script is not supported under any Microsoft standard support program or service.
.2031 23:02:50 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.2032 23:02:50 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.2033 23:02:50 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.2034 23:02:50 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.2035 23:02:50 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.2036 23:02:50 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.2037 23:02:50 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.2038 23:02:50 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.2039 23:02:50 (0) ** of the possibility of such damages.
.2040 23:02:50 (0) **
.2041 23:02:50 (0) **
.2042 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2043 23:02:50 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.2044 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2045 23:02:50 (0) **
.2046 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2047 23:02:50 (0) ** Windows 7 - Service Pack 1 - 32-bit (7601) - User 'ICARUS\ROBERT_NEU' on computer 'ICARUS'.
.2048 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2049 23:02:50 (0) ** Environment: ........................................................................................................ OK.
.2050 23:02:50 (0) ** There are no missing WMI system files: .............................................................................. OK.
.2051 23:02:50 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.2052 23:02:50 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
.2053 23:02:50 (0) ** AFTER running WMIDiag:
.2054 23:02:50 (0) ** The WMI repository has a size of: ................................................................................... 16 MB.
.2055 23:02:50 (0) ** - Disk free space on 'C:': .......................................................................................... 10920 MB.
.2056 23:02:50 (0) ** - INDEX.BTR, 2367488 bytes, 20.11.2012 18:46:00
.2057 23:02:50 (0) ** - MAPPING1.MAP, 47288 bytes, 20.11.2012 18:46:00
.2058 23:02:50 (0) ** - MAPPING2.MAP, 47288 bytes, 22.11.2012 22:32:44
.2059 23:02:50 (0) ** - OBJECTS.DATA, 14557184 bytes, 20.11.2012 18:46:00
.2060 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2061 23:02:50 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.2062 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2063 23:02:50 (0) ** DCOM Status: ........................................................................................................ OK.
.2064 23:02:50 (0) ** WMI registry setup: ................................................................................................. OK.
.2065 23:02:50 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.2066 23:02:50 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.2067 23:02:50 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.2068 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2069 23:02:50 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.2070 23:02:50 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.2071 23:02:50 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.2072 23:02:50 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.2073 23:02:50 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.2074 23:02:50 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.2075 23:02:50 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.2076 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2077 23:02:50 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.2078 23:02:50 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.2079 23:02:50 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
.2080 23:02:50 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.2081 23:02:50 (0) ** selecting 'Run as Administrator'.
.2082 23:02:50 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
.2083 23:02:50 (0) ** in the Task Scheduler within the right security context.
.2084 23:02:50 (0) **
.2085 23:02:50 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.2086 23:02:50 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.2087 23:02:50 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.2088 23:02:50 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
.2089 23:02:50 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.2090 23:02:50 (0) **
.2091 23:02:50 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.2092 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
.2093 23:02:50 (0) ** - REMOVED ACE:
.2094 23:02:50 (0) ** ACEType: &h0
.2095 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2096 23:02:50 (0) ** ACEFlags: &h0
.2097 23:02:50 (0) ** ACEMask: &h3
.2098 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2099 23:02:50 (0) ** DCOM_RIGHT_ACCESS_LOCAL
.2100 23:02:50 (0) **
.2101 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2102 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2103 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2104 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2105 23:02:50 (0) **
.2106 23:02:50 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.2107 23:02:50 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.2108 23:02:50 (0) ** - REMOVED ACE:
.2109 23:02:50 (0) ** ACEType: &h0
.2110 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2111 23:02:50 (0) ** ACEFlags: &h0
.2112 23:02:50 (0) ** ACEMask: &h7
.2113 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2114 23:02:50 (0) ** DCOM_RIGHT_ACCESS_LOCAL
.2115 23:02:50 (0) ** DCOM_RIGHT_ACCESS_REMOTE
.2116 23:02:50 (0) **
.2117 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2118 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2119 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2120 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2121 23:02:50 (0) **
.2122 23:02:50 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.2123 23:02:50 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.2124 23:02:50 (0) ** - REMOVED ACE:
.2125 23:02:50 (0) ** ACEType: &h0
.2126 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2127 23:02:50 (0) ** ACEFlags: &h0
.2128 23:02:50 (0) ** ACEMask: &h7
.2129 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2130 23:02:50 (0) ** DCOM_RIGHT_ACCESS_LOCAL
.2131 23:02:50 (0) ** DCOM_RIGHT_ACCESS_REMOTE
.2132 23:02:50 (0) **
.2133 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2134 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2135 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2136 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2137 23:02:50 (0) **
.2138 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.2139 23:02:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.2140 23:02:50 (0) ** - REMOVED ACE:
.2141 23:02:50 (0) ** ACEType: &h0
.2142 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2143 23:02:50 (0) ** ACEFlags: &h0
.2144 23:02:50 (0) ** ACEMask: &h1F
.2145 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2146 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2147 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2148 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2149 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2150 23:02:50 (0) **
.2151 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2152 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2153 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2154 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2155 23:02:50 (0) **
.2156 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.2157 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.2158 23:02:50 (0) ** - REMOVED ACE:
.2159 23:02:50 (0) ** ACEType: &h0
.2160 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2161 23:02:50 (0) ** ACEFlags: &h0
.2162 23:02:50 (0) ** ACEMask: &h1F
.2163 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2164 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2165 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2166 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2167 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2168 23:02:50 (0) **
.2169 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2170 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2171 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2172 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2173 23:02:50 (0) **
.2174 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
.2175 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.2176 23:02:50 (0) ** - REMOVED ACE:
.2177 23:02:50 (0) ** ACEType: &h0
.2178 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2179 23:02:50 (0) ** ACEFlags: &h0
.2180 23:02:50 (0) ** ACEMask: &h1F
.2181 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2182 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2183 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2184 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2185 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2186 23:02:50 (0) **
.2187 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2188 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2189 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2190 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2191 23:02:50 (0) **
.2192 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.2193 23:02:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.2194 23:02:50 (0) ** - REMOVED ACE:
.2195 23:02:50 (0) ** ACEType: &h0
.2196 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2197 23:02:50 (0) ** ACEFlags: &h0
.2198 23:02:50 (0) ** ACEMask: &h1F
.2199 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2200 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2201 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2202 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2203 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2204 23:02:50 (0) **
.2205 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2206 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2207 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2208 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2209 23:02:50 (0) **
.2210 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.2211 23:02:50 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
.2212 23:02:50 (0) ** - REMOVED ACE:
.2213 23:02:50 (0) ** ACEType: &h0
.2214 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2215 23:02:50 (0) ** ACEFlags: &h0
.2216 23:02:50 (0) ** ACEMask: &h1F
.2217 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2218 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2219 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2220 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2221 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2222 23:02:50 (0) **
.2223 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2224 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2225 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2226 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2227 23:02:50 (0) **
.2228 23:02:50 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
.2229 23:02:50 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
.2230 23:02:50 (0) ** - REMOVED ACE:
.2231 23:02:50 (0) ** ACEType: &h0
.2232 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2233 23:02:50 (0) ** ACEFlags: &h0
.2234 23:02:50 (0) ** ACEMask: &hB
.2235 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2236 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2237 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2238 23:02:50 (0) **
.2239 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2240 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2241 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2242 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2243 23:02:50 (0) **
.2244 23:02:50 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2245 23:02:50 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.2246 23:02:50 (0) ** - REMOVED ACE:
.2247 23:02:50 (0) ** ACEType: &h0
.2248 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2249 23:02:50 (0) ** ACEFlags: &h0
.2250 23:02:50 (0) ** ACEMask: &h1F
.2251 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2252 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2253 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2254 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2255 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2256 23:02:50 (0) **
.2257 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2258 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2259 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2260 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2261 23:02:50 (0) **
.2262 23:02:50 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2263 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.2264 23:02:50 (0) ** - REMOVED ACE:
.2265 23:02:50 (0) ** ACEType: &h0
.2266 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2267 23:02:50 (0) ** ACEFlags: &h0
.2268 23:02:50 (0) ** ACEMask: &h1F
.2269 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2270 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2271 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2272 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2273 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2274 23:02:50 (0) **
.2275 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2276 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2277 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2278 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2279 23:02:50 (0) **
.2280 23:02:50 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2281 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.2282 23:02:50 (0) ** - REMOVED ACE:
.2283 23:02:50 (0) ** ACEType: &h0
.2284 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2285 23:02:50 (0) ** ACEFlags: &h0
.2286 23:02:50 (0) ** ACEMask: &h1F
.2287 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2288 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2289 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2290 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2291 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2292 23:02:50 (0) **
.2293 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2294 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2295 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2296 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2297 23:02:50 (0) **
.2298 23:02:50 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2299 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
.2300 23:02:50 (0) ** - REMOVED ACE:
.2301 23:02:50 (0) ** ACEType: &h0
.2302 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2303 23:02:50 (0) ** ACEFlags: &h0
.2304 23:02:50 (0) ** ACEMask: &h1F
.2305 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2306 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2307 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2308 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2309 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2310 23:02:50 (0) **
.2311 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2312 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2313 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2314 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2315 23:02:50 (0) **
.2316 23:02:50 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.2317 23:02:50 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
.2318 23:02:50 (0) ** - REMOVED ACE:
.2319 23:02:50 (0) ** ACEType: &h0
.2320 23:02:50 (0) ** ACCESS_ALLOWED_ACE_TYPE
.2321 23:02:50 (0) ** ACEFlags: &h0
.2322 23:02:50 (0) ** ACEMask: &h1F
.2323 23:02:50 (0) ** DCOM_RIGHT_EXECUTE
.2324 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
.2325 23:02:50 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
.2326 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
.2327 23:02:50 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
.2328 23:02:50 (0) **
.2329 23:02:50 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.2330 23:02:50 (0) ** Removing default security will cause some operations to fail!
.2331 23:02:50 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.2332 23:02:50 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.2333 23:02:50 (0) **
.2334 23:02:50 (0) **
.2335 23:02:50 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.2336 23:02:50 (0) ** DCOM security error(s) detected: .................................................................................... 14.
.2337 23:02:50 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.2338 23:02:50 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.2339 23:02:50 (0) **
.2340 23:02:50 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.2341 23:02:50 (0) ** Overall WMI security status: ........................................................................................ OK.
.2342 23:02:50 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.2343 23:02:50 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.2344 23:02:50 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.2345 23:02:50 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.2346 23:02:50 (0) ** - Root, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2347 23:02:50 (0) **
.2348 23:02:50 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
.2349 23:02:50 (0) ** - Root, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2350 23:02:50 (0) ** - Root, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2351 23:02:50 (0) ** - Root/subscription, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2352 23:02:50 (0) ** - Root/DEFAULT, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2353 23:02:50 (0) ** - Root/CIMV2, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2354 23:02:50 (0) ** - Root/CIMV2/Security, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2355 23:02:50 (0) ** - Root/CIMV2/Applications, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2356 23:02:50 (0) ** - Root/nap, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2357 23:02:50 (0) ** - Root/SECURITY, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2358 23:02:50 (0) ** - Root/WMI, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2359 23:02:50 (0) ** - Root/directory, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2360 23:02:50 (0) ** - Root/directory/LDAP, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2361 23:02:50 (0) ** - Root/SecurityCenter, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2362 23:02:50 (0) ** - Root/Microsoft, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2363 23:02:50 (0) ** - Root/Microsoft/HomeNet, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2364 23:02:50 (0) ** - Root/aspnet, 0x8007007E - Das angegebene Modul wurde nicht gefunden..
.2365 23:02:50 (0) **
.2366 23:02:50 (0) ** WMI GET operations: ................................................................................................. OK.
.2367 23:02:50 (0) ** WMI MOF representations: ............................................................................................ OK.
.2368 23:02:50 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.2369 23:02:50 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.2370 23:02:50 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.2371 23:02:50 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.2372 23:02:50 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.2373 23:02:50 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.2374 23:02:50 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.2375 23:02:50 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.2376 23:02:50 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.2377 23:02:50 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.2378 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2379 23:02:50 (0) **
.2380 23:02:50 (0) ** 17 error(s) 0x8007007E - (WBEM_UNKNOWN) This error code is external to WMI.
.2381 23:02:50 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
.2382 23:02:50 (0) ** with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x007E)
.2383 23:02:50 (0) ** converted in decimal (126).
.2384 23:02:50 (0) ** - NET HELPMSG 126
.2385 23:02:50 (0) **
.2386 23:02:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.2387 23:02:50 (0) ** WMI Registry k
Hi all!
So based on two recent cases with KB2685811 not installing.
As pointed by Wei Mao you need to inspect cbs.log (i use Notepad ++ for the job)
In the first case I had error with 5 files in C:\windows\winsxs\temp that couldn't be deleted so I booted with Ubuntu CD and deleted all content of C:\windows\winsxs\temp which then allowed for the update to install fine.
Second case - with Wei Mao help who pointed to error:
Error 80 in Function CMofLexer::CMofLexer line 615 C:\Windows\system32
\wbem\Wdf01000.mof (1): error in my cbs.log
I again booted with Ubuntu CD, renamed the following files C:\Windows\system32
\wbem\Wdf01000.mof and C:\Windows\system32
\wbem\Wdf01000uninstall.mof (i didn't delete them just in case)
then the problematic update installed fine.
So inspect your cbs.log and hope for the best :)
Peter
