Thanks for the heads up here is as well. The vSphere 7.0 U3a it is just for vCenter, so this specific issue which affects ESXi it has not been addressed on any public build, might be hotfixes but I am not sure.
My advice will be, do not update to ESXi 7.0.3, vCenter is fine, just not the ESXi,l it seems it happens sometimes, when some big unmap blocks happen, etc. But still, better not to risk
Thanks Jorge and Wolfgang
There’s a second less discussed bug that is also doing the rounds, HA not working after installing u3a, vCenter is getting a 503 trying to log into the ESXi hosts and vpxa log on the hosts is showing messages about host changed and failed to diff ha-host:network.
So yeah, u3a is a bust 
VMware is still unlucky with their updates; it looks like every release in the last time contained some kind of certain bug. I'm missing the stability which ESXi used to have; instead we get new features with every minor release which used to be major versions in the past.
By the way, the KB already changed since Friday, as it contained much less information in that day.
Yeah saw this bug after doing vCenter but left my hosts at U2 cause of the USB NIC fling as they had not updated it for U3 yet. So stayed safe on this one as most my VMs are thin provisioned. 
Thx @vNote42 , it seems that Microsoft is not the only one putting customers and partners into problems with new updates 
VMware is still unlucky with their updates; it looks like every release in the last time contained some kind of certain bug. I'm missing the stability which ESXi used to have; instead we get new features with every minor release which used to be major versions in the past.
By the way, the KB already changed since Friday, as it contained much less information in that day.
Being unlucky with their updates is a nice way of saying they have a huge quality problem these days! 
VMware is still unlucky with their updates; it looks like every release in the last time contained some kind of certain bug. I'm missing the stability which ESXi used to have; instead we get new features with every minor release which used to be major versions in the past.
By the way, the KB already changed since Friday, as it contained much less information in that day.
Being unlucky with their updates is a nice way of saying they have a huge quality problem these days!
Let’s hope they don’t share the same QA department with Microsoft 
All these issues with U3 paired with now dropping our most widely used boot method in our customer environments (µSD-RAID1) is really giving me some headache. Reminds me of those times where they were destroying CBT several times within a single year...
Another reason why I love Veeam. QA is so much better. I would even run a beta productively with Veeam…
All these issues with U3 paired with now dropping our most widely used boot method in our customer environments (µSD-RAID1) is really giving me some headache. Reminds me of those times where they were destroying CBT several times within a single year...
Yes! But since than, CBT was quite stable and trustworthy. I was hoping, after all these bugs U1 and U2, we higher quality in U3. 
