You can choose each VM accordingly and register them with your new VMWare ESXi install. Then browse the old vmfs that your datastore was on and find your directory for each virtual machine. You choose the option to “Register a VM”, instead of creating a new one.

Then, it’s not too bad to get back to working. Other global settings will need to be reconfigured as well. Once you are booted up and you connect to your VM Host, you will need to recreate your vSwitch settings such as vlans, etc. ***That is key!*** Make sure not to overwrite your datastore partition if stored locally! That way your partition with your datastore is unaffected. Go ahead and configure things like a new VM Host while choosing this new flash drive as your install media. I booted to the new drive on my host and it was treating things like a new install. Important note is to make sure you use the same version you had before you received the error. I created a new usb flash drive with VMWare ESXi on it. In my case, this was a single, standalone host in a home environment. The Fix: Error loading /k.b00 Fatal error: 33 (Inconsistent data)Īfter searching the web I found people talking about modifying the image on the flash drive to replace corrupted files such as the one mentioned in the error (Error loading /k.b00) and other fixes that required a good bit of work. Of course, as I’m sure you guessed, I didn’t have a backup. Which brings me to my most important recommendation: I chose to use a cheap, bargain-bin flash drive because it’s what I had around when I built this host. Backgroundįor reference, I boot VMWare ESXi off of a usb flash drive for each of my hosts.

The error that I was getting was “Error loading /k.b00 Fatal error: 33 (Inconsistent data)”. I came across a bunch of ways to possibly resolve this issue and wanted to share the way that I used. If you have been following me on Twitter ( then you know I had an issue with a VMHost of mine. From time to time I mix it up a bit and go off topic from Cisco.

Esxi Installer Fatal Error 33