Windows Update Failing

-

csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_892c2d8a36efaaf2 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_7.1.7601.16492_7580f27ddc7aff34 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_57e48d10363cbc88 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_e7ce2a28541cb9e1 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7601.17514_dc6339fd519cf2de hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7601.17514_c305d15c066149b4 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..lientcore-d_31bf3856ad364e35_6.1.7601.17514_7d05977d5ecc9e24 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_a9fe5b2edbaefae5 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7601.17514_fe09def7fdd625df hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_91f3fd4e10c6ac3a hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514_040700ec1dd9c5e1 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_0fb7137c829dbc53 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w...deployment_31bf3856ad364e35_7.6.7600.256_5322733520e3f1b9 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_69db321fe056be03 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_f3923e58a429acde hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7601.17514_c20546edc43a4369 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_a4f5e9a711ce7e7c hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_7.1.7601.16492_f8bf5441c2b17814 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_faecf381fef94b91 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_78a180e57a46bd8d hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_65763e1a973d511e hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7601.17514_6068a1ed8245f8b1 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_f47113c54d2350e6 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_9e50a90843128fe2 hklm\components\canonicaldata\deployments
(f) csi missing deployment key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_8.0.7601.17514_6a890089ee4f1956 hklm\components\canonicaldata\deployments

summary:
seconds executed: 431
 found 517 errors
  csi manifest , s256h not match total count: 2
  csi missing deployment key total count: 514
  csi missing identity total count: 1
  csi located replacement: invalid (s256h) total count: 32

unavailable repair files:
winsxs\manifests\x86_microsoft-windows-mountvol.resources_31bf3856ad364e35_6.1.7600.16385_en-us_8348d3f2266ebcda.manifest
winsxs\manifests\x86_microsoft-windows-localizeddrivers_31bf3856ad364e35_6.1.7600.16385_en-us_7ea3332a260be531.manifest

i'd try removing unused language packs rid of "csi missing deployment key"

 

 


regards, dave patrick ....
microsoft certified professional
microsoft mvp [windows server] datacenter management

disclaimer: posting provided "as is" no warranties or guarantees, , confers no rights.



Windows Server  >  Windows Server General Forum



Comments

Post a Comment

Popular posts from this blog

After enabling Windows Server 2012 R2 DHCP Failover Getting Packet dropped because of Client ID hash mismatch

-
we have 2 dhcp servers @ our site (they each located on different subnets).  these dhcp servers running windows server 2012 r2.  dedicated dhcp servers.  yesterday afternoon, reconfigured several scopes such become members of single dhcp failover relationship have configured load balance 50% of load placed on each dhcp failover relationship member (dhcp server). however, morning, users reported unable renew dhcp addresses.  looking dhcp logs on both dhcp servers, there several entries follow: "36,mm/dd/yyyy,hh:mm:ss,packet dropped because of client id hash mismatch or standby server.,ip subnet,,mac address,,0,6,,,,,,,,,0" i performed manual synchronization of failover relationship , scopes on both dhcp servers.  restarted dhcp service on both dhcp servers still getting same error. a bing/google search did not bring light issue encountering.  has encountered , if so, solution. i should add when attempted perform ipconfig/renew on workst...
Read more

WMI Repository 4GB limit - Win 2003 Ent Question

-
Image
hi there, i've question size limit on wmi repository (being 4gb). if isn't correct place post this, apologies , can let me know wheere post this? i've come across few servers running citrix have reached limit on wmi repository size , need install ibm director agent hw monitoring. during install getting 'out of disk space' errors entered in mofcomp.log: "(mon apr 02 04:10:36 2012.172843) : error occurred while processing item 4: (mon apr 02 04:10:36 2012.172843) : error number: 0x8004103b, facility: wmi description: out of disk space" when error number http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx i see this: wbem_e_out_of_disk_space 2147749947 (0x8004103b) disk out of space or 4 gb limit on wmi repository (cim repository) size reached. windows xp , windows 2000/nt:   disk out of space. i'm wondering if there reason why limit set 4gb or can increase needs be? can't seem find reas...
Read more

Change home folder default permission?

-
i have searched on , can't seem find similar trying do. using windows server 2003 active directory. when create new user account on domain, use profile tab specify home directory user. when user logs in first time, active directory creates folder in specified path. working correctly. problem gives user full control on folder. has caused lot of problems because "clever" users have discovered thay can change permission on folder or subfolders beneath it. because don't want staff looking @ "sensitive" files. of course doesn't work since can take ownership of file , give myself permissions. causes trouble failed backups, inability scan these folders viruses, migration new storage etc. on occasion 1 of these users call me , ask file or folder restored, , @ point discover not have backup of files , cannot restore them. give them lecture, have on 2500 users, , can't talk them all. right have create account , login teh folder created, go take away full contr...
Read more