@george1421 I was able to change that file to an earlier version and it appears to have fixed our UEFI issue on our newer HP PC’s
@JJ-Fullmer Please let me know what I can provide in testing if needed
@george1421 @JJ-Fullmer I am more than happy to do some testing. Please provide me instruction on what is needed and the debug information that is needed and I can provide some time to testing. Thanks for all of your help.
And to answer the question I am unsure how to change the rEFId version in FOG to make this work for this hardware but we do have a workaround by using BIOS for now till we get this issue resolved.
@JJ-Fullmer We have found something very interesting. If we use rEFInd version 0.10.9 we are able to get the menu and we are able to select Windows from there with no issues. If we go to 0.11.X or higher we run into issues of it not finding Windows and would get stuck on “Scanning for boot loader”. We even went so far to copy the refind.conf file that was on fog our to our rEFInd USB and it booted to Windows without any issues. We have also tried the other things that you have posted with no further of a result.
@george1421 So now that we finally had access to the menu and to the shell we were able to issue the command that you requested
@jj-fullmer We tried to make the recommended changes to the refind.conf file and have tried several paths based on the navigation we used through the BIOS side to the .efi file and all results have come back with it not being able to find anything. Tried both: \EFI\Microsoft\Boot\bootmgfw.efi and \EFI\boot\bootx64.efi
@george1421 @JJ-Fullmer Thank you all for the info. To provide the most accurate information from the tech. There never was a menu option from rEFInd. The menu that was being accessed was from the HP BIOS to which there was no Windows Boot Manager to select but instead we had to drill down to the file and select it to boot. Normally without network boot it would boot just fine.
From what JJ was saying it appears that this is a known issue with these boxes and that we would instead have to use a local version of rEFInd. We have tried using a USB for this and has failed as well to find any boot devices and is simply hanging on Initializing. We have taken the HDD out of the ProDesk and into a known working PC and Windows did boot with network boot without any issues. This really points its finger back at the ProDesk.
If there is anything else you would recommend that we try at this point to troubleshoot? I will try to prob the rEFInd community as well to see if they have some solutions.
George we are working on gathering that information and I will post back with that information shortly. From what I have seen we never have any menu or options to select from like you described but we will try to find that or at least try to figure out how to make the menu appear.
@Szeraax I appreciate you pointing that out. Normally this would be a concern but what we have found is when you install Windows 10 on a new hardware, even if the hardware is the same, Windows 10 will go into a getting your PC ready setup. EDIT (CORRECTION): When configuring the image we will not activate Windows with its key but continue to use the generic key that is associated with Windows 10 for our golden image. We also utilize MAK keys which is not a concern for us in that regard.
@george1421 So it appears that installing 1803 has not fixed this issue that we are experiencing. I have tried to add that path to the refind.conf file for it to find something to boot with but it has failed. What else would you recommend us to try at this point?
@george1421 Okay. So I downloaded that ISO and it still is doing the exact same thing. For more clarification after talking with the technician, it appears that Windows Boot Manager does not show up in the boot menu of the PC. Instead he has to select boot from file, find the driver and drill down to EFI/boot folder to start Windows. What is interesting is that when remove network boot out of the equation it boots straight to the operating system without any issue. We are currently in the process of installing 1803 on the PC to see if it resolves this issue. But so far I am guessing that it won’t as something else is going on with UEFI for some reason on this box.
This is the latest one which because we just updated FOG I do believe is the default. I have just downloaded the refind and will test that and see what the results are. I will also see what directory we have to go to. I just saw where we can specify that in the refind.conf