Just a heads up, if you are considering the latest 10th Generation of the Intel NUC (formally known as Frost Canyon) which are now available on Amazon, Newegg & SimplyNUC, there is an issue to be aware of. The onboard Intel NIC is not detected by ESXi which prevents the installer from proceeding. This issue was reported by a fellow reader named Ben who reached out to me over the holiday and with his help, I was able to get access to the system. It looks like the these NUCs have a newer version of I219-V NIC which is currently not recognized by either the vmklinux e1000 or ne1000 driver.
UPDATE (09/21/20) - The required ne1000 driver has been incorporated into ESXi 7.0 Update 1
UPDATE (08/21/20) - To disable the TPM 2.0 connection cannot be established message in ESXi, please see this blog post for more details.
UPDATE (01/20/20) - As shared on Twitter last Friday, we now have an updated ne1000 driver that will detect the Intel NIC found in the new 10th Gen NUC. You will need to replace the existing ne1000 driver with the new offline bundle, which can be downloaded from here. I would like to remind folks that the Intel NUC is not an officially supported platform from VMware and although have have enable this new system for the community, it does not mean this system or previous generations are supported.
Happy Friday! Thanks to one of our amazing VMware Engineers in China, Songtao (you may know his work on USB NICs for ESXi), we now have built-in NIC working with ESXi on #NUC10 🥳
Details will be shared when ready, but for #Homelab folks, you’re good! pic.twitter.com/tqueIGn5xD
— William Lam (@lamw.bsky.social | @*protected email*) (@lamw) January 17, 2020
There are two options to author a new ESXi Image Profile containing the ne1000 driver, the easiest method is if you have an existing vCenter Server and using the vSphere H5 Client and Image Builder UI. For more details, please take a look at this blog post for detailed instructions.
I’ve done tests with a 10th gen NUC too, no chance to get a working network card. What are the odds that newer versions of ESXi will support these network cards?
Is it possible to install ESXi with only a USB adapter? Your USB Nic Fling can be installed only on a running ESXi system, or is there a way to use it already at installation time?
Thanks in advance and best regards, Ric.
Yes, you can install ESXi w/just a USB NIC. The way you do this is to create a custom ESXi ISO that contains the VIB, this way the USB NIC will be recognized. Check out virtuallyghetto.com/2017/02/update-on-intel-nuc-7th-gen-kaby-lake-esxi-6-x.html for various options of creating custom ISO
I am new to creating custom images I just got my nuc 10 along side ASIX AX88179. Where can I get the VIB that work with esxi 6.7?
I have a NUC10i7FNH.
I have created a custom ISO with the USB NIC VIB and managed to get a USB NIC to be recognised and installation proceeds further.
However at 85%, it fails, reporting 'Exception: No vmknic tagged or management was found.' and the installer stops.
I am using ESXi 6.7 Update 3b as the base for my custom ISO and the USB NIC I am using is a QNAP UC5G1T.
Any thoughts?
Thanks
David.
Thanks a lot William.
As a 6.5-ISO does not boot on a NUC 10 (boot into black screen only) I modified a 6.7 image as described in your link to virten.net. Additionally I added your NIC Fling instead of the ASIX driver.
Now the same thing happens as to Andrew Davis, the installer stops at 85% with error message: "Exception: No vmknic tagged for management was found". Same situation as Barry Rosenberg describes here on Dec 24 2019 (https://flings.vmware.com/usb-network-native-driver-for-esxi/comments).
I switched to the console (Alt-F1) and deleted the vmk0 interface (esxcli network ip interface remove --interface-name=vmk0). Switch back to the install screen (Alt-F2) and now the installer is running through.
I can reboot fine, but there is no network card detected. So I switched to the System Customization (F2) and go to Network Restore Options - Restore Network Settings. A few seconds later the USB-Nic seems to work and gets a address via DHCP.
On a reboot the USB-NIC does not get an ip address via DHCP. I set the address to static which survives a reboot but there is no network connection.
I had to restart the management network (System Customization - Restart Management Network) to get the adapter running.
Thanks Ric. I will give that a try as well and see if I get the same results.
It sounds like, once ESXi is installed and a switch has been created, the following may fix the loss of network information: https://flings.vmware.com/usb-network-native-driver-for-esxi#instructions
David
Seen this too late today, hit the send button earlier. Maybe this will help.
Noticed another weird thing when adding virtual machines: can add a network adapter to the machine as usual but the virtual machine does not get the network card. I've done a fast test with an Ubuntu 18 server installation. The VM does not identify the network adapter so only the loopback interface lo is available.
Have to do some more testing but it is over for today.
Can confirm the fix for local.sh at https://flings.vmware.com/usb-network-native-driver-for-esxi#instructions as working. Thanks David.
Unfortunately, it doesn't seem to be working for me. I took the code for the local.sh that relates to the standard switch binding and added it to the file. I added it exactly without any modifications so I'm not sure if I need to change anything or not and that could be why it hasn't worked for me.
At present, after a reboot, the ESXi host shows the static IP etc. but has not connection.
More worrying is that I left the NUC up for about 2.5 days and at some point in the last 12 hours, it lost network connection. As far as I know, it didn't reboot.
On a plus side, I started to build a VCSA VM and that appeared to get its network connection OK, without any manual intervention. I used the OVA appliance and once it had imported the VM, I was immediately able to access the web admin page to continue the setup.
David
David, what exactly is not working? You wrote your NUC has no connection after a reboot but later it lost connection. So I assume it shure has a connection but late after the boot process? Regards, Ric
The USB NIC is present but it never binds to the networks/vSwitch after reboot. Since my post, I have manually run the 'esxcfg' commands from the local.sh modification which bind the vusb0 adapter to the vSwitch0, the 'Management Network' and the 'VM Network' and can confirm that they work and connectivity is restored once they are run.
I have also found some information saying you cannot run esxcli commands in the local.sh and have to run localcli, however, I amended the code and it has not made any difference for me. That information may nor be relevant to ESXi 6.7 though, I am not sure.
My instinct at the moment is that the local.sh is not being executed but I am not sure how to check or prove this.
One thing I want to try later today, when I get home from work, is to remove the checking loop from the code where it checks if the NIC status is up or not and just leave a pause and then the binding commands (esxcfg commands) and see if that makes any difference.
Basically, at the moment, after a reboot, the vusb0 adapter is preset and status is 'Up' but the binding does not happen without manual intervention.
David
if Secure Boot enabled，local.sh Won't execute
Thanks. I disabled SecureBoot prior to my testing above.
Is there any way to confirm whether local.sh is being processed?
Can try echo 'content1' > abc.txt
Verify if there is file abc.txt after startup
David, check your syslog.log with "cat /var/log/syslog.log |grep local.sh", there are entries when local.sh is running:
cat /var/log/syslog.log |grep local.sh
2020-01-06T15:17:45Z root: init Running local.sh
2020-01-06T16:27:53Z root: init Running local.sh
2020-01-08T11:25:37Z root: init Running local.sh
Regards, Ric
A quick update. I now have the local.sh being run at startup and it is restoring network connectivity through the QNAP USB NIC automatically for both the management and VM networks following a reboot of the host.
The reason it wasn't running previously was because the execute permissions had all dropped off the local.sh file.
I have a remaining issue to investigate. I have iSCSI storage that connects on the same NIC and this does not seem to re-connect properly so any VMs stored there don't work until the storage devices are refreshed. I suspect if I can find the commands to do this using esxcli, I can add those to the local.sh to run after the NIC has been initialised and bound to the networks.
David
David, here is a document how to connect iSCSI targets with esxcli.
I doubt the the local.sh is the right place and time at startup for doing this but never stop trying.
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc_50%2Fcli_manage_iscsi_storage.7.5.html
Works a treat - Kudos to Songtao - I think I'd just managed to compile a working driver using the toolchain and latest driver from sourceforge - so he beat me to it 🙂
I had issues where I would get a PSOD during the installer boot process. By cloning the image profile instead of creating a new image profile, this issue went away. It may have been including too many packages.
I am happy to hear there is a driver now for my new NUC10. I do have a challenge to create the boot image. I do not have a vCenter Server and also I do not have Windows at hand (I've only got Macs). Is there another easy way to make a 6.7 ESXi installer iso, or should I simply wait for a future release? Or should I get the temp Windows 10 VM and run it in Fusion?
Just to answer my own question... there's a few steps to it, if you do not have a running vCenter or even Windows 10. In my case, I had the ability to run VMware Fusion, although I'm sure VirtualBox would have worked too. Here are the steps, for those in the same situation as me and that don't know how to get it done.
Step 1: Get a Windows VM: https://download3.vmware.com/software/vmw-tools/ESXi670-NE1000-32543355-offline_bundle-15486963.zip
Step 2: In the Windows VM, run Powershell as an admin and execute this command to install VMware PowerCLI: Install-Module -Name VMware.PowerCLI
Step 3: Get ESXI-Customizer-PS https://www.v-front.de/p/esxi-customizer-ps.html or the current direct link: http://vibsdepot.v-front.de/tools/ESXi-Customizer-PS-v2.6.0.ps1
Step 4: Download the driver for the NUC10 NIC: https://download3.vmware.com/software/vmw-tools/ESXi670-NE1000-32543355-offline_bundle-15486963.zip (put it in a separate directory for easy reference later)
Step 5: Using a guide like http://woshub.com/add-drivers-vmware-esxi-iso-image/ (which is the one I used), in PowerShell, go to the directory where you downloaded the ESXi-Customizer-PS script and run:
.\ESXi-Customizer-PS-v2.6.0.ps1 -v67 -pkgDir C:\wherever\you\put\the\zip\file\from\step\4
This should get you some output, hopefully including:
++++++++++++++++++++
Running with PowerShell version 5.1 and VMware PowerCLI version 11.5.0.14899560
Connecting the VMware ESXi Online depot ... [OK]
Getting Imageprofiles, please wait ... [OK]
Using Imageprofile ESXi-6.7.0-20191204001-standard ...
(dated 11/25/2019 11:42:42, AcceptanceLevel: PartnerSupported,
Updates ESXi 6.7 Image Profile-ESXi-6.7.0-20191204001-standard)
Loading Offline bundles and VIB files from C:\wherever\you\put\the\zip\file\from\step\4 ...
Loading C:\wherever\you\put\the\zip\file\from\step\4\ESXi670-NE1000-32543355-offline_bundle-15486963.zip ... [OK]
Add VIB ne1000 0.8.4-3vmw.670.3.99.32543355 [OK, replaced 0.8.4-2vmw.670.2.48.13006603]
Exporting the Imageprofile to 'C:\Users\User\Downloads\esxicust\ESXi-6.7.0-20191204001-standard-customized.iso'. Please be patient ...
All done.
++++++++++++++++++++
Hi Willian,
I have the same problem, but I don't have a vsphere.
Could you please share your personalized image for nuc10i7fnh?
Thank you so much.
Regards,
Frederico Pereira (aka fredux)
if you have windows 10 as your OS, you can go from step 2 in my previous post, should get you the iso. Worked for me on my nuc10i7fnh.
Hi, I tried following the above steps and nearly completed but with the following error:
Your thoughts on this??
PS C:\vm> ./ESXi-Customizer-PS-v2.6.0.ps1 -v67 -pkgDir c:\VM\ESXi670-NE1000-32543355-offline_bundle-15486963.zip
This is ESXi-Customizer-PS Version 2.6.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)
(Call with -help for instructions)
Logging to C:\Users\USER\AppData\Local\Temp\ESXi-Customizer-PS-17748.log ...
Running with PowerShell version 5.1 and VMware PowerCLI version 11.5.0.14899560
Connecting the VMware ESXi Online depot ... [OK]
Getting Imageprofiles, please wait ... [OK]
Using Imageprofile ESXi-6.7.0-20191204001-standard ...
(dated 11/25/2019 11:42:42, AcceptanceLevel: PartnerSupported,
Updates ESXi 6.7 Image Profile-ESXi-6.7.0-20191204001-standard)
Loading Offline bundles and VIB files from c:\VM\ESXi670-NE1000-32543355-offline_bundle-15486963.zip ...
Exporting the Imageprofile to 'C:\vm\ESXi-6.7.0-20191204001-standard-customized.iso'. Please be patient ...
An unexpected error occured:
[WinError 10054] An existing connection was forcibly closed by the remote host
If requesting support please be sure to include the log file
C:\Users\USER\AppData\Local\Temp\ESXi-Customizer-PS-17748.log
WS, see the last line, did you this logfile?
Hi WS,
like Ric said, is there any info in the log file? Other than that, it seems there was a network issue, so, at the risk of sounding like a scripted support agent, did you try running it again to see if it was a fluke network issue that doesn't exist anymore?
No data in the log other than what i had copied.
just tried again and also from home last night with no luck... same error:
An unexpected error occured:
[WinError 10054] An existing connection was forcibly closed by the remote host
Further to this within the logs:
Exporting the Imageprofile to 'C:\vm\ESXi-6.7.0-20191204001-standard-customized.iso'. Please be patient ...
PS>TerminatingError(Export-EsxImageProfile): "[WinError 10054] An existing connection was forcibly closed by the remote host"
>> TerminatingError(Export-EsxImageProfile): "[WinError 10054] An existing connection was forcibly closed by the remote host"
An unexpected error occured:
[WinError 10054] An existing connection was forcibly closed by the remote host
It seems the error occurs when loading the new driver. The messages about loading the offline bundle are missing, it should look like this:
1 Running with PowerShell version 5.1 and VMware PowerCLI version 11.5.0.14899560
2 Connecting the VMware ESXi Online depot ... [OK]
3 Getting Imageprofiles, please wait ... [OK]
4 Using Imageprofile ESXi-6.7.0-20191204001-standard ...
5 (dated 11/25/2019 11:42:42, AcceptanceLevel: PartnerSupported,
6 Updates ESXi 6.7 Image Profile-ESXi-6.7.0-20191204001-standard)
7 Loading Offline bundles and VIB files from C:\Users\IEUser\Desktop\ESXi670-NE1000\ ...
8 Loading C:\Users\IEUser\Desktop\ESXi670-NE1000\ESXi670-NE1000-32543355-offline_bundle-15486963.zip ... [OK]
9 Add VIB ne1000 0.8.4-3vmw.670.3.99.32543355 [OK, replaced 0.8.4-2vmw.670.2.48.13006603]
10 Exporting the Imageprofile to 'C:\Users\IEUser\Desktop\ESXi-6.7.0-20191204001-standard-customized.iso'. Please be patient ...
11 All done.
Line 8 and 9 are missing.
So try to move the file "ESXi670-NE1000-32543355-offline_bundle-15486963.zip" to a subfolder like c:/vm/ne1000/ and change your command to
"./ESXi-Customizer-PS-v2.6.0.ps1 -v67 -pkgDir c:\VM\ne1000\ESXi670-NE1000-32543355-offline_bundle-15486963.zip"
The pkgDir part of the command should point to a directory, not a file! so "-pkgDir c:\VM\ne1000\"
I completely missed that in the command....
Thanks Guys, - Still no luck after correcting the path.
---------------------------
PS C:\vm> ./ESXi-Customizer-PS-v2.6.0.ps1 -v67 -pkgDir C:\VM\Packages -outDir C:\VM\ISO
This is ESXi-Customizer-PS Version 2.6.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)
(Call with -help for instructions)
Temporarily logging to C:\Users\User\AppData\Local\Temp\ESXi-Customizer-PS-3944.log ...
Running with PowerShell version 5.1 and VMware PowerCLI version 11.5.0.14899560
Connecting the VMware ESXi Online depot ... [OK]
Getting Imageprofiles, please wait ... [OK]
Using Imageprofile ESXi-6.7.0-20191204001-standard ...
(dated 11/25/2019 11:42:42, AcceptanceLevel: PartnerSupported,
Updates ESXi 6.7 Image Profile-ESXi-6.7.0-20191204001-standard)
Loading Offline bundles and VIB files from C:\VM\Packages ...
Loading C:\VM\Packages\ESXi670-NE1000-32543355-offline_bundle-15486963.zip ... [OK]
Add VIB ne1000 0.8.4-3vmw.670.3.99.32543355 [OK, replaced 0.8.4-2vmw.670.2.48.13006603]
Exporting the Imageprofile to 'C:\VM\ISO\ESXi-6.7.0-20191204001-standard-customized.iso'. Please be patient ...
An unexpected error occured:
[WinError 10054] An existing connection was forcibly closed by the remote host
If requesting support please be sure to include the log file
C:\Users\User\AppData\Local\Temp\ESXi-Customizer-PS-3944.log
Copied your setup with paths etc. into a Windows 10 VM without any errors.
Read this: https://twitter.com/VFrontDe/status/998868087586934785
There seems to be a problem with some SSL changes. Maybe in your setup too.
This is what I did to get the custom ISO created after a few failures using the other instructions I found. I hope it helps someone else.
1. Start Powershell as an admin and run this command to install PowerCLI: Install-Module -Name VMware.PowerCLI
2. Download the ESXI-Customizer-PS https://www.v-front.de/p/esxi-customizer-ps.html or the current direct link: http://vibsdepot.v-front.de/tools/ESXi-Customizer-PS-v2.6.0.ps1 and save it to a working directory, "C:\ESXi-NUC10\"
3. Download the NUC10 NIC driver and save it to a sub directory "C:\ESXi-NUC10\driver\": https://download3.vmware.com/software/vmw-tools/ESXi670-NE1000-32543355-offline_bundle-15486963.zip
4. Download the Offline bundle from VMware's site and save it to "C:\ESXi-NUC10\" I used 6.7.0U3b (ESXi670-201912001.zip)
5a. In the Powershell console navigate to "C:\ESXi-NUC10\" and run the Powershell script, this will create the ISO from the offline bundle and include all drivers in the driver directory:
.\ESXi-Customizer-PS-v2.6.0.ps1 -izip .\ESXi670-201912001.zip -pkgDir .\driver
5b. You may need to allow the script to run so be sure to unblock it and allow remotesigned scripts.
See: http://woshub.com/how-to-disable-open-file-security-warnings-in-windows-7/
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
6. Burn or write the ISO to USB and install!
I noticed the installer took a good while to install, but it did complete and ESXI 6.7U3b is now up and running on the NUC10!
Hi All,
If you have this error message at the end "could not find a trusted signer" so just add -nsc at the end of the command:
.\ESXi-Customizer-PS-v2.6.0.ps1 -v67 -pkgDir C:\wherever\you\put\the\zip\file\from\step\4 -nsc
After having burn the ISO on USB stick you should have an issue when booting on your NUC during install. To solve it you have to disable Secure boot on the BIOS.
@AYDK - Thank you!
Added -nsc and finally ISO created - Now to load and test. Let you all know how it goes
Howdy! Is there anyone having the issue with the TPM message on NUC10i7FNH with ESXI6.7u3 and vCenter (TPM 2.0 device detected but a connection cannot be established.)? Thanks, GD
I have this same problem. No way to get rid of this message. Also I can't seem to set EVC to anything above "Sandy Bridge" even though my older NUC's can be set to "Haswell"
I also have the TPM message, but next time I will restart the system I'll try to disable everything related to TPM in the bios. The message is just an annoyance though, it's not like it messes with functionality in any way.
I haven't tried any EVC settings yet...
I already disabled the tpm function from bios and message is still appearing.
Same here. No settings helps.
EVC was also annoying. Moving from NUC7 messed my system up quite badly.
Otherwise I am happy 🙂
My NUC10 had the same message in vCenter although I've disabled TPM in BIOS.
Upgrade the BIOS of NUC10i7FNH to latest version "FN0044.cap", and this warning message disappeared.
BTW, I encountered the same issue of "Shutting down firmware services...
Using 'simple offset' UEFI RTS mapping policy" which occurred on NUC8i7HNK before, that issue was resolved by BIOS update to version 51 or later. But FN0044 was the latest BIOS version for my NUC10. With the error message on screen, I tried to ping and ssh to ESXi later, and it succeed, the ESXi started correctly. Not sure why there's such error message when launching ESXi.
I downloaded the files and followed the steps, but it didn't work, ESXi still not finding the ne100 drivers, any idea about how to double check the drivers are in the iso? my nuc model is NUC10i7FNH which I suppose is the same one Intel® Ethernet Connection I219-V
Michel, please post all message from the creation steps here. Most of the time there is a mess with folders and files when running ESXi customizer.
Hi Michel,
I buildt a customized ISO for the same model. You can download it here if you want : http://dl.free.fr/jGcY6wfcw
Enjoy
It worked, I was using the file path instead the folder, thanks
I followed these steps and it works fine:
# (Optional) Install PowerCLI Module
Install-Module -Name VMware.PowerCLI -Scope CurrentUser
Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Export-ESXImageProfile -ImageProfile "ESXi-7.0.0-15843807-standard" -ExportToBundle -filepath ESXi-7.0.0-15843807-standard.zip
Remove-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Add-EsxSoftwareDepot .\ESXi-7.0.0-15843807-standard.zip
Add-EsxSoftwareDepot .\ESXi670-NE1000-32543355-offline_bundle-15486963.zip
New-EsxImageProfile -CloneProfile "ESXi-7.0.0-15843807-standard" -name "ESXi-7.0.0-15843807-NUC" -Vendor "virten.net"
Remove-EsxSoftwarePackage -ImageProfile "ESXi-7.0.0-15843807-NUC" -SoftwarePackage "ne1000"
Add-EsxSoftwarePackage -ImageProfile "ESXi-7.0.0-15843807-NUC" -SoftwarePackage "ne1000 0.8.4-3vmw.670.3.99.32543355"
Export-ESXImageProfile -ImageProfile "ESXi-7.0.0-15843807-NUC" -ExportToIso -filepath ESXi-7.0.0-15843807-NUC.iso
If you want i shared the ISO and you can download it from this link: https://we.tl/t-yJLQoom6PX (the link will expire in a week)
Hi Skenkz,
I'm having the same needs to install the NUC10, can you please share the IOS?
Thanks
Hi, did anyone run into the issue when NVMe drive is not detected by ESXi installation, though visible in BIOS? If so, is there any trick to overcome it?
I have installed the ne1000 driver, and using ESXi 6.7u2. I installed pfSense 2.4.5p1 with 2 vmnics mapped to 2 VLANs. Am seeing significant packet loss and TCP resets between pfSense and my local router.
Will try pfSense with it's own support for VLANs to see if things improve.
Any plan to add 8086:0d4c to the driver? I am almost certain that it is the same as 0d4f.
Please see https://www.williamlam.com/2020/08/enhancements-to-the-community-ne1000-vib-for-intel-nuc-10.html which now includes support for 0d4c
Re: Disabling TPM, please see https://www.williamlam.com/2020/08/disabling-tpm-2-0-connection-cannot-be-established-message-in-esxi-for-intel-nuc-10.html for confirmed instructions
Hi William, I've managed to to get ESXi 7.0.0 installed on my NUC10i7FNH using the new community ne1000 VIB (offline bundle). Thanks for your guidance on this.
Do you have any further guidance on how I can get the inbuilt Intel AC 9462 Wireless NIC to be recognised by ESXi so that I can use it as well?
The download links for download3 don't seem to be working anymore. I can't seem to download the NE1000 driver.
There was an updated version which I forgot to update this article. Its fixed now
Hello All,
Any clues , I been having issues installing ESXi 7 update 2 on the my desktop. Issues with Network card detection . I am using MSI mother board with card ( Ethernet controller: Intel Corporation Ethernet Connection (12) I219-V) .
Hi William,
Thanks for sharing this information with the community. I can confirm that this fling works with a Lenovo ThinkCentre M70q (003VMH) that comes with a built-in Intel (11) I-219V network card.
In order to get ESXi 7.0u2a (build 17867351) installed on this tiny computer you have to follow the following steps:
- Download the community network driver fling: https://flings.vmware.com/community-networking-driver-for-esxi
- Create a custom ESXi ISO with vCenter AutoDeploy or with the PowerCLI script
- Disable Secure Boot in the BIOS
- Create a bootable usb stick with Rufus and use the Custom ESXi ISO as your source.
- Install ESXi 7.0.2 from the USB stick.
I have Dell optiplex 7080 with eth Intel 219lm 8086: 0d4c how instal ESXI 6.7? Wher is driver? Driver for ESXi 7.0 not function
Hi: I am stuck trying to install on a NUC10i7FNK. Install fails with PSOD and the message: 'Could not mount /dev: Not found'. Seems like it doesn't like the M2 drive maybe? Any clues or direction greatly appreciated. I've searched and don't find any one else having referenced this issue.
Sounds like it could be HW. Try another USB if you’re booting and/or installing and connectors. We had one user report issues with m.2 and found one of cables were torn
Hi William, thanks so much for your reply. I have tried other USB sticks with the same result. I tried a different NUC today (NUC10FNH) with the same result. I feel like maybe I'm doing something really stupid in creating the drive with Rufus, but there aren't a lot of settings. Using MBR/BIOSorUEFI, FAT32/16kilobytes Cluster, Quick format. The error occurs even if I disable all the internal storage in BIOS, so thinking you are correct in that its related to the bootable USB.
Unless it's been removed from the edited version of this post, where is the link to the ne1000 driver that works with 8086:0D4F? Or am I blind (probably)?
See the note on 9/1/2020 🙂
I may be late to the party, but I've been experimenting with ESXi on a NUC10 Performance. I was able to install ESXi 7 with no issues. I have a vSphere 8 license I'm using from a VMITA course, which I plan on installing sometime this week. One thing I've been having trouble with is booting ESXi from a USB - It seemingly loads most the way, but the NUC powers off at the very end of the boot process. I've got it booting form NVMe for now. Any thoughts on fixing the USB boot issue?