Index was outside the bounds of the array

Hello!

This is my first post, so first of all let me say hello to everybody out here. Guys, I came here with unusual problem which I can't solve. Here is some background info:

- OS Type: Windows 7 Pro 32bit (EN)
- Windows with local accounts, no AD or whatsoever
- vSphere 4.1.0 build 799345 (VMware-viclient-all-4.1.0-799345.exe)

Now, what is happening? I can login to VC using my account that I always use and when I try to access Host to add New VM or edit settings of existing VM I got following error: "Index was outside the bounds of the array."

Here is most relevant stack trace:

[...]
[viclient:SoapTran:M: 6] 2012-10-02 14:29:11.868  Invoke 77 Start GetAlarmActionsEnabled on AlarmManager:AlarmManager [ip_address]. [operationID:2B2186EB-0000004D][Caller: VpxClient.InventoryContextMenus.SetAlarmContextMenuItems]
[viclient:SrvMsg  :M: 6] 2012-10-02 14:29:11.868  RMI Request Vmomi.Alarm.AlarmManager.GetAlarmActionsEnabled - 77
<entity type="ManagedObject">HostSystem:host-258 [ip_address]</entity>
[viclient:SoapTran:P:14] 2012-10-02 14:29:11.868  Invoke 77 Finish GetAlarmActionsEnabled on AlarmManager:AlarmManager [ip_address] - Serial:0.000, Server:000.009
[        :ShowExcp:M: 6] 2012-10-02 14:29:19.746  Error: An internal error occurred in the vSphere Client.
Details: Index was outside the bounds of the array.

Contact VMware support if necessary.
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at VMware.CustomControls.NumericUpdownEx..ctor()
   at VMware.CustomControls.DiskCapControl.InitializeComponent()
   at VMware.CustomControls.DiskCapControl..ctor()
   at VpxClient.VMConfig.BWzVDiskCapPage.InitializeComponent()
   at VpxClient.VMConfig.BWzVDiskCapPage..ctor(TocWizard myBoss)
   at VpxClient.VMConfig.NWz..ctor(NWzModes m)
   at VpxClient.Common.UiCommands.VirtualMachine.NewOrImportVM(ManagedEntity entity, Boolean import, Boolean forceVmtn, Service iService)

Now steps which I took to solve issue:

- uninstall all versions of vSphere, reinstall recent one (VMware-viclient-all-4.1.0-799345.exe)
- clean up registry using CCleaner and following PowerShell script (Thanks Greg!):

Get-ChildItem HKCU:\ -rec -ea SilentlyContinue | foreach {
   $CurrentKey = (Get-ItemProperty -Path $_.PsPath);
   if (($CurrentKey -like "*vmware*") -or ($CurrentKey -like "*vpxclient*") -or ($CurrentKey -like "*viclient*")) {
      $CurrentKey >> reg_HKCU.txt;
   };
};

Get-ChildItem HKLM:\ -rec -ea SilentlyContinue | foreach {
   $CurrentKey = (Get-ItemProperty -Path $_.PsPath);
   if (($CurrentKey -like "*vmware*") -or ($CurrentKey -like "*vpxclient*") -or ($CurrentKey -like "*viclient*")) {
      $CurrentKey >> reg_HKLM.txt;
   };
};

- remove all temp files from following locations: Users, Windows/Temp, Program Files/VMware
- remove all remaining files on hdd that contains one of following: *vmware*, *vpxclient*, *viclient*
- read carefuly post regarding desktop size/resolution here: http://communities.vmware.com/thread/337640
- read and follow instructions provided by VMWare Support Team here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1308
- tried to debug vpxClient.exe with OllyDBG/IDA PRO/dotPeek without luck

- reinstall .NET 4.0 + all patches and security fixes provided by Microsoft

and guess what? Nothing have helped! What helped though was to create another local windows user account and logging in there. From this newly created account vSphere Client is working fine = I can login to VC and create new VM/edit settings of existing one. I am not giving up here, but this seems to me to be only resolution I found so far. But let's be honest here - it's not a fix but lame workaround which I can't accept.

Do you have any other option/idea I can use?