Following 10 alarms introduced in vCenter 8.0 Update 3g can't be modified with vSphere Client in non English environment due to an error.
In vpxd.log, we see the vmodl.fault.InvalidArgument being logged.
2025-10-29T00:39:31.490Z error vpxd[19900] [Originator@6876 sub=Default opID=mhb7oo32-967-auto-qw-h5:70000413-64] [VpxLRO] -- ERROR task-215 -- 52f83b1d-2d00-b7f7-d868-3809fef94705(52f2cfd3-2591-d7e7-a4aa-183b85ad5b43) -- alarm-180 -- vim.alarm.Alarm.reconfigure: :vmodl.fault.InvalidArgument
--> Result:
--> (vmodl.fault.InvalidArgument) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> invalidProperty = "name"
--> msg = ""
--> }
--> Args:
vCenter Server 8.0 U3g or later
This issue occurs because the alarm in question have only English name.
This will be resolved in a future release of vCenter.
To work around this issue, change vSphere Client language from local language to english.
Please refer here for how to change language.