Error with Host Update Utility when I scan for patches

Similar Questions

• Patching host with Host Update Utility

  I have a clean install of ESXi 171294 (VMware image) and I ran the Host Update Utility for the first time. Three plots have shown (see image) and my question is whether it is necessary to install the two patches firmware (2009-07-09 and 2009-08-06) or just the latter list (2009-08-06)?

  Is not a firmware patch a full picture of replacement, so the 2009-08-06 firmware would include the 2009-07-09 bugs?

  Thank you

  The host update utility will show all patches available for VMware and that apply to the selected host, as users will like to choose what patches they want to take. It is just this flexibility of selection. The utility will scan against selected patches and will tell you that can be consumed by the host that you are running.

  If you are at the level of GA 4.0 then it will show the two patches published so far if necessary, you can choose which you want to apply based on the identified patches in the respective articles of the patches. Each released hotfix will have an article explaining how fix it, so let say < X > patch fixes issue A and B and < Y > corrective patch question A, B and c. is released after x, but the user may not want the extra difficulty C so he can always go to patch < X >.

  Thank you

  Samir

  PS: If you think the answer is useful please consider rewarding points.

• What happens to the cleaning after upgrade with Host Update Utility?

  Hello

  I've just updated my esx 3.5 to 4.0 using the host update utility.

  I noticed that in the data store, it is now the iso esx4.0 and an esxconsole-* folder.

  These 2 are always required? or is it safe to remove them after the upgrade? They take a part of the review of the space on the local data store.

  Thanks in advance!

  The .iso file may be deleted.

  But the esxconsole-* file is the COS for COS vmdk.

  If you are unable to delete this folder and you cannot delete the related VMFS data store.

  André

• When I scan for Windows Vista Service Pack update (published 4/2009) comes in,

  I redid my computer a few months ago restore to factory settings and restore my files from a backup disk. Everything seemed to work properly.  A few weeks ago a full scan found a worm & some virus which I removed. Now, I have a problem with the updates. When I scan for Windows Vista Service Pack update (published 4/2009) arrives.  When I click to install it, it is saying it is correctly installed (in 30 seconds) and yet he continues to come when I'm scanning for updates.    Should I restore settings again?  After looking for info on the forums of windows, I did the System File Checker to check corrupt files.  Several corrupted files appear in the details of the SFC.  But their fixation is "over my head".   I glued the SFC details below. Any help would be appreciated.  Thank you

  2012-09-04 11:51:44, info CSI 00000006 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:51:44, transaction Info CSI 00000007 [SR] beginning verify and repair
  2012-09-04 11:51:47, info CSI 00000009 [SR] full audit
  2012-09-04 11:51:48, CSI of information 0000000 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:51:48, CSI Info 0000000b transaction [SR] beginning verify and repair
  2012-09-04 11:51:53, CSI to 0000000 d [SR] full audit information
  2012-09-04 11:51:53, CSI 0000000e Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:51:53, CSI Info 0000000f transaction [SR] beginning verify and repair
  2012-09-04 11:51:55, info CSI 00000011 [SR] full audit
  2012-09-04 11:51:56, info CSI 00000012 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:51:56, transaction Info CSI 00000013 [SR] beginning verify and repair
  2012-09-04 11:51:57, info CSI 00000015 [SR] full audit
  2012-09-04 11:51:57, info CSI 00000016 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:51:57, Info CSI 00000017 [SR] beginning verify and repair
  2012-09-04 11:51:59, info CSI 00000019 [SR] full audit
  2012-09-04 11:51:59, CSI Info 0000001 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:51:59, CSI Info 0000001 b transaction [SR] beginning verify and repair
  2012-09-04 11:52:01, CSI Info 0000001 d [SR] full audit
  2012-09-04 11:52:01, 0000001e Info [SR] CSI components check 100 (0 x 00000064)
  2012-09-04 11:52:01, CSI Info 0000001f transaction [SR] beginning verify and repair
  2012-09-04 11:52:03, info CSI 00000021 [SR] full audit
  2012-09-04 11:52:03, info CSI 00000022 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:03, transaction Info CSI 00000023 [SR] beginning verify and repair
  2012-09-04 11:52:04, info CSI 00000025 [SR] full audit
  2012-09-04 11:52:05, info CSI 00000026 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:05, the transaction Info CSI 00000027 [SR] beginning verify and repair
  2012-09-04 11:52:06, info CSI 00000029 [SR] full audit
  2012-09-04 11:52:07, CSI Info 0000002 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:52:07, CSI Info 0000002b transaction [SR] beginning verify and repair
  2012-09-04 11:52:09, info CSI 0000002d [SR] full audit
  2012-09-04 11:52:09, CSI [SR] 0000002e Info components check 100 (0 x 00000064)
  2012-09-04 11:52:09, CSI Info 0000002f transaction [SR] beginning verify and repair
  2012-09-04 11:52:11, info CSI 00000031 [SR] full audit
  2012-09-04 11:52:12, info CSI 00000032 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:12, transaction Info CSI 00000033 [SR] beginning verify and repair
  2012-09-04 11:52:13, info CSI 00000035 [SR] full audit
  2012-09-04 11:52:14, info CSI 00000036 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:14, transaction Info CSI 00000037 [SR] beginning verify and repair
  2012-09-04 11:52:15, Info CSI 00000039 [SR] check complete
  2012-09-04 11:52:16, CSI Info 0000003 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:52:16, CSI Info 0000003b transaction [SR] beginning verify and repair
  2012-09-04 11:52:19, info CSI 0000003d [SR] full audit
  2012-09-04 11:52:19, CSI 0000003e [SR] Info components check 100 (0 x 00000064)
  2012-09-04 11:52:19, CSI Info 0000003f transaction [SR] beginning verify and repair
  2012-09-04 11:52:24, info CSI 00000041 [SR] full audit
  2012-09-04 11:52:24, info CSI 00000042 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:24, transaction Info CSI 00000043 [SR] beginning verify and repair
  2012-09-04 11:52:29, info CSI 00000046 [SR] full audit
  2012-09-04 11:52:29, info CSI 00000047 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:29, transaction Info CSI 00000048 [SR] beginning verify and repair
  2012-09-04 11:52:33, CSI Info 0000004a Verify [SR] full
  2012-09-04 11:52:34, CSI Info 0000004 components [SR] b check 100 (0 x 00000064)
  2012-09-04 11:52:34, CSI Info 0000004 c [SR] beginning verify and repair operation
  2012-09-04 11:52:37, CSI 0000004f [SR] Verify Info full
  2012-09-04 11:52:38, info CSI 00000050 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:38, Info CSI 00000051 [SR] beginning verify and repair
  2012-09-04 11:52:43, info CSI 00000053 [SR] full audit
  2012-09-04 11:52:43, info CSI 00000054 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:43, transaction Info CSI 00000055 [SR] beginning verify and repair
  2012-09-04 11:52:51, CSI 0000005f [SR] Verify Info full
  2012-09-04 11:52:51, info CSI 00000060 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:51, transaction Info CSI 00000061 [SR] beginning verify and repair
  2012-09-04 11:52:55, info CSI 00000063 [SR] full audit
  2012-09-04 11:52:56, info CSI 00000064 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:52:56, transaction Info CSI 00000065 [SR] beginning verify and repair
  2012-09-04 11:53, info CSI 00000067 [SR] full audit
  2012-09-04 11:53, info CSI 00000068 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53, transaction Info CSI 00000069 [SR] beginning verify and repair
  2012-09-04 11:53:05, CSI Info 0000006b Verify [SR] full
  2012-09-04 11:53:06, components of CSI Info 0000006 c [SR] 100 audit (0 x 00000064)
  2012-09-04 11:53:06, CSI Info 0000006 d [SR] beginning verify and repair transaction
  2012-09-04 11:53:14, CSI Info 0000006f Verify [SR] full
  2012-09-04 11:53:15, info CSI 00000070 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53:15, transaction Info CSI 00000071 [SR] beginning verify and repair
  2012-09-04 11:53:24, Info CSI 00000075 [SR] check complete
  2012-09-04 11:53:24, info CSI 00000076 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53:24, transaction Info CSI 00000077 [SR] beginning verify and repair
  2012-09-04 11:53:38, info CSI 00000079 [SR] full audit
  2012-09-04 11:53:38, CSI Info 0000007 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:53:38, CSI Info 0000007 b transaction [SR] beginning verify and repair
  2012-09-04 11:53:52, CSI Info 0000007 d [SR] full audit
  2012-09-04 11:53:52, CSI 0000007e Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53:52, CSI Info 0000007f transaction [SR] beginning verify and repair
  2012-09-04 11:53:55, info CSI 00000081 [SR] full audit
  2012-09-04 11:53:55, info CSI 00000082 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53:55, transaction Info CSI 00000083 [SR] beginning verify and repair
  2012-09-04 11:53:57, info CSI 00000085 [SR] full audit
  2012-09-04 11:53:57, info CSI 00000086 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:53:57, Info CSI 00000087 [SR] beginning verify and repair
  2012-09-04 11:53:59, info CSI 00000089 [SR] full audit
  2012-09-04 11:53:59, CSI Info 0000008 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:53:59, CSI Info 0000008b transaction [SR] beginning verify and repair
  2012-09-04 11:54:09, 000000 a 9 CSI Info [SR] verification complete
  2012-09-04 11:54:10, 000000aa CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:10, CSI Info 000000ab transaction [SR] beginning verify and repair
  2012-09-04 11:54:11, 000000ad CSI Info [SR] verification complete
  2012-09-04 11:54:11, 000000ae CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:11, 000000af CSI Info transaction [SR] beginning verify and repair
  2012-09-04 11:54:14, 000000 b 1 CSI Info [SR] verification complete
  2012-09-04 11:54:15, 000000 b 2 CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:15, 000000 b 3 CSI Info transaction [SR] beginning verify and repair
  2012-09-04 11:54:19, 000000 b 5 CSI Info [SR] verification complete
  2012-09-04 11:54:19, 000000 b 6 CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:19, 000000 b 7 CSI Info transaction [SR] beginning verify and repair
  2012-09-04 11:54:26, 000000 b 9 CSI Info [SR] verification complete
  2012-09-04 11:54:27, 000000ba CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:27, 000000bb CSI Info transaction [SR] beginning verify and repair
  2012-09-04 11:54:32, 000000bd CSI Info [SR] verification complete
  2012-09-04 11:54:32, 000000be CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:32, CSI Info 000000bf transaction [SR] beginning verify and repair
  2012-09-04 11:54:38, CSI Info 000000 c 1 [SR] full check
  2012-09-04 11:54:38, CSI Info 000000 c 2 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:54:38, CSI Info 000000 c 3 [SR] beginning operation check and repair
  2012-09-04 11:54:42, CSI Info 000000 c 5 [SR] full check
  2012-09-04 11:54:42, CSI 000000C6 [SR] components Info check 100 (0 x 00000064)
  2012-09-04 11:54:42, CSI Info 000000 c 7 [SR] beginning operation check and repair
  2012-09-04 11:54:46, CSI Info 000000 c 9 [SR] full check
  2012-09-04 11:54:47, 000000 CSI Info [SR] this component check 100 (0 x 00000064)
  2012-09-04 11:54:47, CSI Info 000000cb transaction [SR] beginning verify and repair
  2012-09-04 11:54:57, CSI Info 000000dc Verify [SR] full
  2012-09-04 11:54:57, Info CSI [SR] 000000dd components check 100 (0 x 00000064)
  2012-09-04 11:54:57, CSI Info 000000de transaction [SR] beginning verify and repair
  2012-09-04 11:55:08, 000000f4 CSI Info [SR] verification complete
  2012-09-04 11:55:09, 000000f5 CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:55:09, CSI Info 000000f6 transaction [SR] beginning verify and repair
  2012-09-04 11:55:30, 000000f8 CSI Info [SR] verification complete
  2012-09-04 11:55:31, 000000f9 CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:55:31, 000000fa CSI Info transaction [SR] beginning verify and repair
  2012-09-04 11:55:42, CSI Info 000000 fc [SR] full audit
  2012-09-04 11:55:42, 000000fd CSI Info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:55:42, CSI Info 000000fe transaction [SR] beginning verify and repair
  2012-09-04 11:55:55, info CSI 00000100 [SR] full audit
  2012-09-04 11:55:55, info CSI 00000101 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:55:55, transaction Info CSI 00000102 [SR] beginning verify and repair
  2012-09-04 11:55:57, info CSI 00000104 [SR] cannot repair the military record [l:20 {10}] "tcpmon.ini" Microsoft-Windows-printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:56:01, info CSI 00000106 [SR] cannot repair the military record [l:20 {10}] "tcpmon.ini" Microsoft-Windows-printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:56:01, info CSI 00000107 [SR] this element is referenced by [ml:38 {19}, l:36 {18}] "Windows Foundation.
  2012-09-04 11:56:01, CSI Info 0000010a [SR] could not reproject corrupted file [ml:520 {260}, l:46 {23}] '------? \C:\Windows\System32"\[l:20{10}]"TCPMon.ini '; source file in the store is also corrupted
  2012-09-04 11:56:01, CSI Info 0000010 c [SR] full audit
  2012-09-04 11:56:01, components of CSI Info 0000010 d [SR] 100 audit (0 x 00000064)
  2012-09-04 11:56:01, Info CSI 0000010e transaction [SR] beginning verify and repair
  2012-09-04 11:56:06, info CSI 00000110 [SR] full audit
  2012-09-04 11:56:06, info CSI 00000111 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:56:06, transaction Info CSI 00000112 [SR] beginning verify and repair
  2012-09-04 11:56:11, info CSI 00000115 [SR] full audit
  2012-09-04 11:56:11, info CSI 00000116 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:56:11, transaction Info CSI 00000117 [SR] beginning verify and repair
  2012-09-04 11:56:24, Info CSI 00000119 [SR] check complete
  2012-09-04 11:56:24, CSI Info 0000011 components [SR] a check 100 (0 x 00000064)
  2012-09-04 11:56:24, CSI Info 0000011b transaction [SR] beginning verify and repair
  2012-09-04 11:56:31, CSI Info 0000011 d [SR] full audit
  2012-09-04 11:56:31, CSI 0000011e [SR] Info components check 100 (0 x 00000064)
  2012-09-04 11:56:31, CSI Info 0000011f transaction [SR] beginning verify and repair
  2012-09-04 11:56:38, info CSI 00000121 [SR] full audit
  2012-09-04 11:56:39, 00000122 CSI info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:56:39, transaction Info CSI 00000123 [SR] beginning verify and repair
  2012-09-04 11:56:45, info CSI 00000125 [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6000.16615, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:56:49, info CSI 00000127 [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6000.16615, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:56:49, info CSI 00000128 [SR] this element is referenced by [l:160 {80}] "' Package_37_for_KB943411 ~ 31bf3856ad364e35 ~ x 86 ~ ~ 6.0.1.5.943411 - 110_RTM_neutral_GDR" "
  2012-09-04 11:56:49, CSI Info 0000012b [SR] could not reproject corrupted file [ml:520 {260}, l:72 {36}] '------? "\C:\Program Files\Windows Sidebar"------[l:24 {12}] "settings.ini"; source file in the store is also corrupted
  2012-09-04 11:56:50, info CSI 0000012d [SR] full audit
  2012-09-04 11:56:50, CSI 0000012e [SR] Info components check 100 (0 x 00000064)
  2012-09-04 11:56:50, CSI Info 0000012f transaction [SR] beginning verify and repair
  2012-09-04 11:56:56, info CSI 00000131 [SR] full audit
  2012-09-04 11:56:56, info CSI 00000132 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:56:56, transaction Info CSI 00000133 [SR] beginning verify and repair
  2012-09-04 11:57:05, info CSI 00000135 [SR] full audit
  2012-09-04 11:57:06, info CSI 00000136 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:57:06, transaction Info CSI 00000137 [SR] beginning verify and repair
  2012-09-04 11:57:18, CSI Info 0000013a Verify [SR] full
  2012-09-04 11:57:18, CSI Info 0000013 components [SR] b check 100 (0 x 00000064)
  2012-09-04 11:57:18, CSI Info 0000013 c [SR] beginning verify and repair operation
  2012-09-04 11:57:22, Info CSI 0000013e [SR] full Verify
  2012-09-04 11:57:23, CSI 0000013f [SR] components Info check 100 (0 x 00000064)
  2012-09-04 11:57:23, transaction Info 00000140 CSI [SR] beginning verify and repair
  2012-09-04 11:57:29, info CSI 00000142 [SR] full audit
  2012-09-04 11:57:29, info CSI 00000143 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:57:29, transaction Info CSI 00000144 [SR] beginning verify and repair
  2012-09-04 11:57:34, Info CSI 00000146 [SR] full check
  2012-09-04 11:57:34, Info CSI 00000147 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:57:34, transaction Info CSI 00000148 [SR] beginning verify and repair
  2012-09-04 11:57:42, CSI Info 0000014a Verify [SR] full
  2012-09-04 11:57:42, CSI Info 0000014 components [SR] b check 100 (0 x 00000064)
  2012-09-04 11:57:42, CSI Info 0000014 c [SR] beginning verify and repair operation
  2012-09-04 11:57:51, Info CSI 0000014e [SR] full Verify
  2012-09-04 11:57:51, CSI 0000014f [SR] components Info check 100 (0 x 00000064)
  2012-09-04 11:57:51, transaction Info CSI 00000150 [SR] beginning verify and repair
  2012-09-04 11:57:55, info CSI 00000152 [SR] full audit
  2012-09-04 11:57:55, info CSI 00000153 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:57:55, transaction Info CSI 00000154 [SR] beginning verify and repair
  2012-09-04 11:58, info CSI 00000156 [SR] full audit
  2012-09-04 11:58:01, info CSI 00000157 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:58:01, Info CSI 00000158 [SR] beginning verify and repair
  2012-09-04 11:58:05, CSI Info 0000015a Verify [SR] full
  2012-09-04 11:58:05, CSI Info 0000015 components [SR] b check 100 (0 x 00000064)
  2012-09-04 11:58:05, CSI Info 0000015 c [SR] beginning verify and repair operation
  2012-09-04 11:58:10, Info CSI 0000015e [SR] full Verify
  2012-09-04 11:58:11, CSI 0000015f [SR] components Info check 100 (0 x 00000064)
  2012-09-04 11:58:11, transaction Info CSI 00000160 [SR] beginning verify and repair
  2012-09-04 11:58:16, Info CSI 00000162 [SR] check complete
  2012-09-04 11:58:17, info CSI 00000163 [SR] components check 100 (0 x 00000064)
  2012-09-04 11:58:17, transaction Info CSI 00000164 [SR] beginning verify and repair
  2012-09-04 11:58:20, Info CSI 00000166 [SR] check complete
  2012-09-04 11:58:20, 00000167 CSI info [SR] components check 100 (0 x 00000064)
  2012-09-04 11:58:20, transaction Info CSI 00000168 [SR] beginning verify and repair
  2012-09-04 11:58:24, CSI Info 0000016a Verify [SR] full
  2012-09-04 11:58:25, CSI Info 0000016b [SR] audit 92 (0x0000005c) components
  2012-09-04 11:58:25, CSI Info 0000016 c [SR] beginning verify and repair operation
  2012-09-04 11:58:31, Info CSI 0000016e [SR] full Verify
  2012-09-04 11:58:31, CSI 0000016f [SR] repair 2 Info components
  2012-09-04 11:58:31, transaction Info CSI 00000170 [SR] beginning verify and repair
  2012-09-04 11:58:31, info CSI 00000172 [SR] cannot repair the military record [l:20 {10}] "tcpmon.ini" Microsoft-Windows-printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:58:31, info CSI 00000174 [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6000.16615, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:58:31, info CSI 00000176 [SR] cannot repair the military record [l:20 {10}] "tcpmon.ini" Microsoft-Windows-printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:58:31, Info CSI 00000177 [SR] this element is referenced by [ml:38 {19}, l:36 {18}] "Windows Foundation.
  2012-09-04 11:58:31, CSI Info 0000017a [SR] could not reproject corrupted file [ml:520 {260}, l:46 {23}] '------? \C:\Windows\System32"\[l:20{10}]"TCPMon.ini '; source file in the store is also corrupted
  2012-09-04 11:58:31, CSI Info 0000017 c [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6000.16615, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
  2012-09-04 11:58:31, CSI Info 0000017 d [SR] this element is referenced by [l:160 {80}] "' Package_37_for_KB943411 ~ 31bf3856ad364e35 ~ x 86 ~ ~ 6.0.1.5.943411 - 110_RTM_neutral_GDR" "
  2012-09-04 11:58:31, info CSI 00000180 [SR] could not reproject corrupted file [ml:520 {260}, l:72 {36}] '------? "\C:\Program Files\Windows Sidebar"------[l:24 {12}] "settings.ini"; source file in the store is also corrupted
  2012-09-04 11:58:32, info CSI 00000182 [SR] full repair
  2012-09-04 11:58:32, info CSI 00000183 [SR] validation of transaction
  2012-09-04 11:58:32, info CSI 00000187 [SR] check and complete repair operation. All of the files and registry keys listed in this operation were repaired successfully

  Hi Mzvern,

  ·         If she invites only to install Vista Service Pack?

  That Factory Restore is the last step in resolving this issue.

  Follow these steps to see what Windows Update is originally the question or any error message/code:

  a. click Start, type Update in the start search box.

  b. in the list of results, click Windows Update.

  (c) in the left pane, click view update history.

  In the meantime, follow the suggestions below for a possible solution:

  Method 1: I suggest you follow the article and then check if it solves the problem.

  Windows Update or Microsoft Update repeatedly offers the same update

  http://support.Microsoft.com/kb/910339

   

  Registry warning

  To do: Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems can occur if you modify the registry incorrectly. Therefore, make sure that you proceed with caution. For added protection, back up the registry before you edit it. Then you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click on the number below to view the article in the Microsoft article:

  Back up the registry

  http://Windows.Microsoft.com/en-us/Windows-Vista/back-up-the-registry

  Important: During the scan of the hard drive if bad sectors are found, the scanner tries to repair this sector, all available on which data may be lost.

  Method 2: For cause of CFS, it wasn't able to repair files of Member, you can follow these steps.

  If the System File Checker tool cannot repair a file, follow these steps:1.At a command prompt, type the following command and press ENTER:

  takeown /f Path_And_File_Name

  For example, type takeown /f E:\windows\system32\jscript.dll.

  2. type the following command and press ENTER to grant administrators full access to the file:

  ICACLS Path_And_File_Name/grant ADMINISTRATORS: F

  For example, type icacls E:\windows\system32\jscript.dll/grant administrators: F.

  3. type the following command to replace the file with a known good copy of the file:

  Copy Path_And_File_Name_Of_Source_File Path_And_File_Name_Of_Destination

  For example, type copy E:\temp\jscript.dll E:\windows\system32\jscript.dll.

  For more information, see the following articles:

  How to analyze the entries in the log file generating the program Checker (SFC.exe) resources of Microsoft Windows in Windows Vista

  http://support.Microsoft.com/kb/928228

   

  Problems with installing updates

  http://Windows.Microsoft.com/en-us/Windows-Vista/troubleshoot-problems-with-installing-updates

   

  Let us know the results.

• How to patch/update ESXi 4.1 (free) now Host Update Utility went

  Hello

  If I understand right now, I need to use vihostupdate (from vsphere CLI) or esxupdate (running in a terminal on the server) to install the new updates/patches on the ESXi 4.1 server.

  The "Host Update Utility" would also find new patches online, this is not possible with vihostupdate or esxupdate? and if no, then how and where can I download new patches/updates?

  -David

  I hope this will help you: http://blog.peacon.co.uk/how-to-patch-esxi-4-1/

  http://blog.peacon.co.UK

  Please give points for any helpful answer.

  Unofficial list of transfer USB devices work

• ESXi 3.5 Update 4 2 esxi: Error Host Update Utility

  Hello world

  I have a free esxi 3.5 server running that I want to spend to esxi 4 u2 (recorded vsphere foundation).

  I want to use the host update utility to perform this task, but I get the folowwing error when the package is checked:

  The upgrade package validation failed, α upgrade metadata reading failure; the incorrect input string format.

  I use the utility version 4.0.0 build 258672 with the updated package upgrade - to - esxi3.5 - 4.0_update02 - 261974.zip.

  I downloaded several times in the event of corruption of file without success.

  Any help welcome!

  Check this post http://communities.vmware.com/thread/265635 . It could be the same problem with the language settings.

  Kind regards.

• How to install vSphere Host Update Utility with vSphere Client 4.1?

  Hi all

  When I install vSphere Client 4.1, I didn't see option to install vSphere Host Update Utility.

  (With vSphere 4.0 Client is OK, option vSphere Host Update Utility is ready)

  so, how to install vSphere Host Update Utility 4.1?

  Thank you

  -

  ---

  Blog to the Viet Nam virtualization technology

  http://congngheaohoa.blogspot.com

  Right.

  See the upgrade guide (http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf)

  André

• vSphere Host Update Utility - ERROR: not enough space on the boot partition

  I get the following error when I run the host update utility

  ERROR: Not enough space on the boot partition

  The boot partition doesn't have enough space to store initrd.img.

  Expected free space (MB): 50, found: 44

  I can free until you reach the required amount?

  Send the output of this command:

  DF h

  And the version of ESX 3.x

  See also this KB (there are a few tips on where space can be lost):

  http://KB.VMware.com/kb/1016511

  André

• vSphere Host Update Utility Scan Failed

  Hello world

  I recently updated my Dell PE2950iii ESXi 3.5 Embedded 4.0. After the upgrade, I was unable to patch the host after scanning and download the 2 patches available with success. So I decided (after reading the post of the user) to perform the repair on the CD of ESXi 4 option. The repair went through fine without any visible error. Now that I tried to scan and patch my host, I get an error that referred me to a viu - 3 log file. I'm not not to clear on how to read but I managed to find this piece of info that may be useful to determine what is at fault in my setup.

  2009-11-18 17:10:15.328 msg: cache location: / tmp/updatecache cache size: 260408 MB

  2009-11-18 17:10:15.328 msg: wrapper scan Host: scanning (all) started.

  2009-11-18 17:10:15.328 inf: managed fix manager using metadata URL:

  2009-11-18 17:10:15.328 inf: begin to download files to the host

  2009-11-18 17:10:15.328 inf: event posted: begin to download files to the host

  2009-11-18 17:10:15.328 inf: file: C:\Documents and Settings\All Users\Application Data\VMware\VMware VI Update/vmw/metadata/vmw-ESXi-4.0.0-metadata.zip to: /tmp/updatecache/vmw-ESXi-4.0.0-metadata.zip

  2009-11-18 17:10:15.328 inf: managed Manager patch file download, CBC: C:\Documents and Settings\All Users\Application Data\VMware\VMware VI Update/vmw/metadata/vmw-ESXi-4.0.0-metadata.zip, dst: /tmp/updatecache/vmw-ESXi-4.0.0-metadata.zip

  2009-11-18 17:10:15.328 msg: host scanner scanning (all) wrapper has no : I/o error has occurred. Failure details: System.IO.IOException: I/o error has occurred.

  Can someone advise me please on how to proceed?

  I'm sorry, I worked 10 hours and my eyes start to fail. I thought you had 0 space free not 0% used.

  Forget it. Try to run from the console:

   esxupdate -m https://hostupdate.vmware.com/software/VUM/PRODUCTION/vmw/vmw-ESXi-4.0.0-metadata.zip scan
  

  and

   esxupdate -m https://hostupdate.vmware.com/software/VUM/PRODUCTION/vmw/vmw-ESXi-4.0.0-metadata.zip update
  

  and paste the results.

• Where to download the file ZIP ESXi 4.0 for inplaceupgrade with vSphere Host Update Utility

  I'm updating my ESXi ESXi 4 3.5U4 with the Host Update Utility vSpheer.

  But where can I find the ZIP file that is required for the upgrade?

  Can this ZIP file created from the ISO?

  There are only ISO in downloads...

  Kind regards

  Daniel

  It is available here:

  https://www.VMware.com/tryvmware/p/activate.php?p=free-ESXi

• VMware Host Update Utility 4.1 VI does not settle with the VI Client?

  I installed the VI Client 4.1 and noticed that it is not seeking to install the VI host update utility.  After installation, it is not installed.  I don't see a separate download for VI host updated.  Does anyone know how to install it now?  Thank you.

  As far as I can tell the vSphere Host Update Utility has been abandoned and you must use the vihostupdate through the CLI.  Good luck, thank you.

• Cannot upgrade to ESXi 4 Update 1 via vSphere Host Update Utility 4.0

  Hello

  can someone tell me why I can't update ESXi 4.0.0 build 219382 to ESXi 4 Update 1 via vSphere Host Update Utility 4.0? The doesn´t utility see the update.

  The problem is, I can't download the update on http://downloads.VMware.com/d/info/datacenter_downloads/vmware_vsphere_4/4 because I always get the error

  "I'm sorry, at the moment you are not allowed to download VMware ESXi 4.

  Update 1 Installable.

  You have the following options:

  "

  How can I get the update or the update with the host update utility?

  I already have an activated ESXi 4.0 license!

  219382 is the latest version. You already update 1.

• Help: update/fixes Essentials, no SAN no host Update Util

  As very probably know VMware in their infinite wisdom have discontinued support and development of Host Update Utility in v4.1.  I currently manage an Essentials environment with DAS only (without SAN), and VCenter installed as a virtual machine on a host.  In the past, I have always used the Util to update host patch and update of my hosts.  Instead of this change, it seems that the only options are manually fixes using vihostupdate or install or use Update Manager.  The latter is useless for us since we do not have a HOLY and cannot update the host who would be Manager update as a virtual machine (no both VMotion etc).  In the past, I would just run host Util update, do check it out for the latest patches of VMware, and then run the patch install - he took care to locate the patches and apply them in the correct order.  What is the best game plan now that this util is gone?  Where can you easily check the patch repository, download the correct patches and apply them in the correct order?  Maybe I missed something, but would appreciate anyone entry on the correction of strategies in this scenario.

  Yes, you can apply all the patches together and atlast you can go to restart ESXi

  Nithin

• ESXi 4.1 - host update utility

  Hello

  I installed customer vshpere 4.1, and it doesn't install the host update utility.

  How can we check updates for ESXi 4.1 now? Only with vCenter?

  Or you can use the vCLI

  Here's an example - http://technodrone.blogspot.com/2010/07/updating-your-vmware-hypervisor-server.html

  Maish

  VMware communities user moderator

  http://technodrone.blogspot.com - @maishsk

  

• Where vSphere Host Update Utility?

  I installed ESX 4.1.0 (build 260247, free) and the vSphere Client. I searched for hours, but can't find the vSphere Host Update Utility 4.0. I don't have a chance to add it in the vSphere Client Installer.

  Thank you

  Hello

  According to this blogupdate utility host that installed with the vSphere Client is now gone in 4.1.

  HTH

  Marek.Z