Wie starte ich den NUC7PJYH mit BIOS 052 im Wartungsfall vom USB-Stick?

[rb13125]

Intel NUC7PJYH mit neuestem BIOS 052 startet nicht mit Windows Installations-Stick generiert von Media Creation Tool 1903, obwohl Secure Boot abgeschaltet. Ebenso Rescue Boot Stick von Macrium Reflect 7. Auch wenn der Boot Stick durch RUFUS mit GPT/UEFI(ohne csm) erzeugt wurde.

Bringe ich den Rechner mit F10 in die Auswahl der Boot medien, wird der USB-Stick zwar angezeigt, aber bei Auswahl lande ich sofort wieder in der Liste. Auch mit einer geklonten Festplatte startet der Rechner nicht, nur mit der zur Zeit eingebauten SSD.

[LeonWaksman]

Check Bios settings in Boot section: Advanced > Boot > Boot Priority - UEFI boot should be enabled, Advanced > Boot > Boot Configuration - Fast Boot should be disabled, Advanced > Boot > Boot Configuration > Devices - USB should be enabled.

Leon

[rb13125]

Hello LWAKSMAN, thanks for your fast reply.

Here are screenshots of the settings in 'boot' section:

The entry for the USB-Stick, for Windows Boot Manager, and 2 for OS boot loader I think would not be valid for UEFI-boot. Why the USB-stick is also labelled with OS-BOOT LOADER, i think this is a term for legacy boot. The settings are as you describe:

and secure boot is off and and plattform keys initialized.

Windows 10 1903 x64 boot media was tested with another PC with UEFI boot successful. In the list of boot media it is only labeled UEFI:Sandisk on this PC.

Roger

[LeonWaksman]

Hello Roger,

1.    I've performed a test on the NUC7i7DNHE I have. It is not identical with your NUC; however, the findings should be applicable to you also.

2.    For this test I've used Sandisk Ultra 16GB USB memory. The installation media, I prepared using Microsoft Media Creation Tool.

3.    First, I founded that the installation media was recognized only in back upper USB port. In all other ports, the USB was not recognized as bootable media. However, in Windows in all port this USB worked.

4.    I'm attaching three images from this test. You may see in BootPriority the installation USB in first line and the HDD with Windows in the second line. On the BootMenu, the installation USB is the second item, while the HDD in the first. My NUC is booting from this USB.

5.    I have no explanation why you see four items in your computer.

6.    Please disconnect any devices (including USB HUB, if any) from your NUC. Leave only keyboard, mouse and monitor connected.

7.    Insert the installation USB (prepared with Microsoft Media Creation Tool), into back USB port. You may try also the front orange USB port.

8.    Power On your NUC and press F10, to enter into Boot Menu. Check if you see UEFI line with your installation media.

Leon

[rb13125]

Hi Leon,I tried all 4 usb ports with same result. If i select the usb stick and enter the boot menu is displayed again. However, although I use the same USB Stick model SANDISK Ultra 3.0 16GB, the entry is different. And of course the recovery and system partition shown as boot entries. I have one idea to clear the CMOS-data to be sure that there are no hidden data that cause the problem. For that i have first to find information where the ’jumper’ is located.

OK, it is the same as entering BIOS and loading BIOS defaults, so I already did. Next I try is booting from an external DVD drive...

And it worked! The entry in the Boot devices table is strange but it started from the installation DVD (5th entry).

The ASUS SBW-06D2X-U USB Device is named SANDISK, and the UEFI:USB is not twice in the name of the device as in other USB devices.

Best regards.

Roger

[LeonWaksman]

Hi Roger,

1. I'm sorry for this delayed replay. I wasn't near my computer.
2. It is always good idea to update Bios using Bios Recovery method with the Yellow security Jumper removed. This method of Bios update is different than setting Bios to default settings. Ususlly is performed if something wrong happened during Bios update. In my opinion this will not clean the old EFI Linux entries in Bios. In this video clip you will see method how to do this: https://www.youtube.com/watch?v=255ltqk7xDM&app=desktop (if is not clear in the video, all the diskpart command you should execute in Windows PowerShell (Admin) window).
3. In the following paragraph release find the steps needed for Bios recovery (if you decide to do this also):
4. Prepare USB stick fully formatted to FAT32 with Bios file JY0052.bio https://downloadcenter.intel.com/download/29065/BIOS-Update-JYGLKCPX-86A-?product=126137 . Format your USB with Quick Format option unchecked. Do not format your USB in MAC (OS) or Linux machine. Use Windows.
5. Disconnect the power adapter and remove the bottom panel from your NUC.
6. Remove the Yellow Bios Security Jumper. (page 48 in Technical Product Specification https://www.intel.com/content/dam/support/us/en/documents/mini-pcs/nuc-kits/NUC7xJY_TechProdSpec.pdf) See also on the attached image.
7. Insert the USB with the  JY0052.bio file.
8. Reconnect the power adapter and power ON the NUC. Wait 30 sec - 2min. The Recovery process will start automatically and will end after 2 -5 minutes.
9. When bios recovery is completed, switch the power OFF, remove the power adapter and replace the Security Jumper (pins 1-2) . Reinstall the bottom panel.
10. Power your NUC ON.
11. Enter Bios setting by pressing F2 during boot process.
12. Press F9(followed by "Y"), to set Bios to default settings. Press F10 (followed by "Y"), to save the settings and exit to O.S. Let the NUC fully reboot.

Regards

Leon

[LeonWaksman]

One more idea. Since you are not be able to boot USB from BOOT menu, I suggest that you enter your BIOS Advanced > Boot _UEFI > Boot Order and drag the UEFI USB Sandisk to the top of the list. Save the settings and exit BIOS. Now your NUC should boot from this USB. Other option is to double click on the 5th line, while you are in BIOS.

Once you are booted into Windows environment, from open Command Prompt and clean the old entries.

Leon

[rb13125]

Hi Leon,

I did the BIOS recovery with no change. I'll read now the document linked in Step 6 to find hints to go on. I'm happy that I found the way to start from DVD is working, so I can start with a clean installl of windows 10, which was the reason for need to use startup from usb device. So my old blueray disc writer is reactivated.

I'm sure the startup from USB worked with older Firmware when I bought this PC. Last when I replaced the magnetic harddisc with the Kingston A400 SSD. It was done with MACRIUM Reflect 7 recovery software started from USB-stick.

Roger

PS: I found no new idea to go on in the document.

[LeonWaksman]

Hi Roger,

Did you try my advice from my last post?

Leon

[rb13125]

Hi Leon,

I tried to boot PC with resequenced entries saved, direct with doubleclick from the visual bios, and the boot menu.

Roger​

[rb13125]

I tried again and again, it is impossible to start the NUC7PJYH from a different medium than the Kingston A400 system disk. even when it was cloned to another drive this will not startup and immediately after trying the power LED is switched off and boot again. Since no downgrade of the BIOS is possible, I have to remain using this weak SSD or drop this NUC PC immediately and replace by a different, I'm sure non Intel-origin device, sorry, I'm using PC's since 1987, I had never such problems with any of my computers. It seams that the only device which can be used for startup is fixed in the BIOS data, no startup from usb-sticks, from different HDD or SSD (one time it started from BluerayDiscWriter, but I couln't repeat this today), even not using a clone of the disc, from which startup is possible. I do not have a second one of this model, but I would bet it is not possible with it. The BIOS 51 and 52 had locked up this PC and I'll stop working on it and buy another. Maybe I'll download later BIOS which fix this problem, but on the other side it is not worth to spend more time on it. Sorry and out.

[LeonWaksman · Accepted solution]

Hi Roger,

I understand your frustration to be stuck without possibility to recover from this situation. I want to clarify one question; since you can boot as you wrote with the Kingston drive, did you try to clean the old bios entries using the procedur described in this video? https://www.youtube.com/watch?v=255ltqk7xDM&app=desktop

Leon

[rb13125]

Yes, my frustration was very big yesterday when the startup from DVD drive did not work as before.

To remove some entries from BCD worked and the NUC now startup from Windows 10 Installation media and Macrium Reflect 7 rescue USB Stick. Probably the BCD storage has only space for small number of entries. The removed entries were network boot and partitions without bootloader on ssd. Still not working is to start up from a cloned HD. But this may be a result of the cloning software. The recovery with the windows command line interface of the installation media was not successful to rebuild bcd or scan for windows installations.

I'll try next the installation of windows to the cloned disk(after cleaning partition table) to see that SSD can be replaced this way.

But first I have to take care of some other things,

Regards

Roger

[LeonWaksman]

Hi Roger,

1. I'm very glad that your original problem was solved (booting from USB), after cleaning the spare entries in Bios. So, now you may install Windows 10 and close this thread.
2. For your convenience, this is a link to list verified by Intel compatible components for your NUC http://compatibleproducts.intel.com/ProductDetails?activeModule=Intel%C2%AE%20NUC# This is list of the components tested by Intel with your NUC, however, many other untasted by intel components may work as well.

Regards

Leon

[rb13125]

Hello Leon,

it's raining all the day and so my tasks in the garden to prepare it for winter are shifted to tomorrow. So I went on with my problems with the NUC. It started from the windows 10 installation media and installed to the new ssd with no problem. So I have now a new , clean installed Windows 10 Pro 64-Bit PC running. I'll install some applications again and not try to install an image backup of the old system. It's time to say goodbye to old experience, may be there is some way to get the data for the clone or recovered disk in the NVRAM/BCD or what is it called but I think that in most cases the problems are more on the human side to detect which behaviour is result of a new feature or of a malfunction. Thanks for your help and your patience.

Regards

Roger