Forum Discussion
Michael_Dieter
Neophyte
9 years ago
I forgot to post that I discovered this appears to be a known issue for multiple ESX releases; one that is only cosmetic.
Its interesting that a patch containing the fix was documented as of October 2015 for multiple pre-6.0 ESX releases, but while there have been 4 ESX updates to 6.0 since that time (including 3 so far in 2016) not one of them has included a fix.
Related Content
- 2 months ago
- 5 months ago
- 18 days ago