27 total posts
Nothing really looks wrong.
For UEFI booting I've had to move on to W8 or W10 or a really new version of Linux. Why Windows 7? It's unclear here.
Also, new machines usually lock out old Windows (7 is old.)
I'm using Windows 8.1 with Bing
I'm actually using Windows 8.1 with Bing
I read through the thread, but again, I'm using Windows 8.1 with Bing not Win 7. There is a significant difference between the two versions as (based on what I have read thus far) the UEFI technology began incorporating into systems that came pre-installed starting with Windows 8 in the mass marketplace.
Two of my Win 7 laptops do not even have UEFI as it was strictly BIOS without any options of Secure Boot or Legacy up to that point (and frankly it was never such a headache). The only reason I need to enable Secure Boot is for mitigating security risks (certain Window Updates can't even install manually because I'm in Legacy Support mode).
Regarding upgrading to Win 10, I have another HP (different model) that came with Win 10 and after doing a fresh Windows install, I'm experiencing the exact same problem with Win 10 as well.
UEFI, AHCI and folk that have troubles.
The discussion shows how to possibly work around it.
I'm seeing more products that will NEVER boot and install W7. Add to that the folk that are in denial (you?) and it gets worse.
Since you don't believe I have to defer and send you to HP.
I don't understand what you're suggesting...
I have two virtually new laptops one Win8 and the other Win10 experiencing the same problem with UEFI. Clearly, there is something I'm missing here, some step or tweak I missed so I don't understand what it is exactly I'm in denial about?
HP is as much help as asking my dog for the answer, thanks.
I have read this thread twice
and I still don't understand what you are trying to do with this !
Are you trying to boot Win 7 from a flash drive ?
Is that what this is about ?
That's not gonna happen....
I dunno but...
there may be cracked software at large here.
I don't understand what the OP's Windows 7 laptops have to do with this.(?)
Because R. Profitt kept mentioning Win 7 out of nowhere
His first two comments kept pushing me about Win 7 when nothing in my original post had to do with it. I simply made a reference to how there was no UEFI in any of my Win 7 laptops as it seems to have gone viral getting preinstalled in systems beginning with Win 8 etc. That is all.
I used what you wrote.
" Used 'Windows 7 USB/DVD Download Tool' "
That's used for Windows 7.
For Windows 10 we use Microsoft's Media Creation Kit.
I only know what you tell me.
-> Now there is HUGE ISSUE with some models that don't allow you to install Windows of any version except what the maker provides. It's a rather awful issue so let's note that too.
I know a few HPs like the Lenovo mentioned in this article.
What's in other articles are these Signature Edition models also are blocking installing Windows.
I'm experiencing the same problem with my other HP that has Win 10 and I downloaded the ISO directly from Microsoft. It's not a cracked issue.
Broken. Why? Read this.
If you used a Windows 7 tool to create bootable Windows 10 media that's the wrong tool.
Google up the "Media Creation Kit" for Windows 10.
Trying to Boot Flash Drive in Secure Boot Mode
I don't know what the confusion with Win7 is all about? The only time I even mentioned Win 7 was when I mentioned the name of the tool I used initially to create the flash drive ISO which is called "Win 7 USB-DVD Download Tool". Let me try to be more clear:
My laptop came pre-installed with Windows 8.1 with Bing.
I had to do a new installation of Windows 8.1 with Bing using an ISO of Windows 8.1 with Bing I created onto a flash drive.
The only way I was allowed to boot my flash drive was by disabling Secure Boot and enabling Legacy Support.
After installing Windows 8.1 with Bing I tried going back into BIOS and restoring the default settings: Secure Boot enabled. Legacy Support disabled.
Apparently, this is not allowed as the only way I can have Secure Boot enabled would be to have installed the Windows with Secure Boot enabled to begin with (this was not possible for me as explained above).
So basically, I have to reinstall Windows 8.1 with Bing from a flash drive while keeping Secure Boot mode enabled and Legacy Support disabled.
Various forums have suggested that the reason my flash drive can't be read while Secure Boot is enabled is because I haven't formatted my flash drive correctly (which was originally NTFS). I have tried multiple variations of converting to FAT32 (as recommended) and reinstalling the ISO using Rufus (which provides GPT for UEFI, MBR for UEFI and other options for formatting). but none of these iterations seem to work as my USB drive won't read.
Based on all of the methods I have already tried from my original post, have I missed a step or haven't tried something? Hope this has helped.
I don't know what
all of this 8.1 with Bing crap is but why not just go to HP for restore media ?
What is the point of purchasing restore media if it won't load the USB flash drive and/or CD/DVD drivers? You're missing the point.
Than uncomplicate this thread
and tell us what you are truly talking about.
Something's missing somewhere .....
I couldn't be any more clear than my second explanation. It's okay, you tried. Thanks anyway.
Okay, thanks to another user from another site I had posted on, I received the answer I was looking for and am posting it here for anyone's future reference. The problem lies in the 32 bit version of Windows I had installed:
" 32bit is unable to boot on a UEFI GPT disk computer. Only 64bit will work." https://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx
I downloaded a Windows 8.1 Single Language 64 bit ISO strictly as a test (as Microsoft doesn't make Bing version available (yet?) for download), used Rufus to set partition scheme to GPT for UEFI and file system as FAT32 and created the new image.
WARNING: If your laptop came with Windows 8 or 8.1 with Bing you will not be able to install any other version of Windows 8 or 8.1 other than Bing. You might be able to use a generic key during setup to get it installed but your Windows will not be activated afterwards as your OEM key is integrated into your firmware and will not activate any other version of Windows 8 other than with Bing. Make sure you have secured either a recovery partition or ISO of this exact version before wiping off your hard drive. If you have used the correct Windows 8 with Bing ISO you will not be asked to enter a product key during setup but rather will be taken straight to the Terms & Policy agreement page.
Once I plugged in the flash drive, it booted right away into installation setup while in Secure Boot enabled / Legacy Support disabled mode. This was what I was trying to do all along.
Regarding my other laptop with the Windows 10 experiencing the same problem: I was so preoccupied with fixing the Windows 8.1 laptop that I never bothered to reformat my flash drive to GPT and FAT32 and had mistakenly installed the correct 64 bit but as a NTFS file system. All I had to do was create a new image with the right settings (above) and sure enough Windows 10 recognized the flash drive immediately and I now have Win 10 installed with Secure Boot enabled / Legacy Support disabled.
1. Download correct 64 bit ISO and don't settle on 32 bit even though the OS will still work for the most part.
2. Format your flash drive as GPT partition and FAT32 using Rufus - Don't use Windows USB/DVD Download Tool as it automatically creates NTFS format without you being able to control its settings and it also doesn't provide you options on controlling the partition schemes. Rufus will save you a lot of time and running around.
3. If installing a fresh Windows, boot the ISO with Secure Boot enabled/Legacy Support disabled otherwise you can't change it afterwards.
You said you'd already done that!
"Used 'Rufus v. 2.11.995' software to create ISO as FAT32 under several different setting iterations:
1. GPT partition scheme for UEFI (this presumably should be the most appropriate setting but it still did not work). End Format: FAT32
2. GPT partition scheme for UEFI (once with Dual UEFI/BIOS mode enabled and once again with it disabled). End Format: FAT32"
Please Look Again
If you go back and look at my original post, you can clearly see I mentioned both in my system specs at the very top as well as the second bullet point "Did multiple fresh installs of Windows 8.1 with Bing (32 bit) erasing all partitions from hard drive every time (my system is designed for 64 but I only have access to a 32 ISO)." that I had at the time installed and was once again trying to reinstall a 32 bit version.
In my SOLVED! post I clearly mentioned the answer to my problem being my use of a 32 bit when I should have used a 64. Using Rufus to set the correct partition scheme to GPT and file system to FAT32 did not matter when creating a 32 bit ISO as it will only work correctly on a 64 (thus what the entire hold up was all about).
Yep, that's what you were told here too.
"nd had mistakenly installed the correct 64 bit but as a NTFS file system. "
And there's the part you failed to mention here with all the FAT32 references above.
" 32bit is unable to boot on a UEFI GPT disk computer. Only 64bit will work." https://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx"
And how is that different than you were told here.
"If this is for Linux, then any UEFI capable 64 bit LIVE version should boot OK. If it's 32 bit and MBR, you MUST boot Legacy."
You also now post " I was so preoccupied with fixing the Windows 8.1 laptop that I never bothered to reformat my flash drive to GPT and FAT32 "
Yet at the first you said the opposite.
"1. GPT partition scheme for UEFI (this presumably should be the most appropriate setting but it still did not work). End Format: FAT32
2. GPT partition scheme for UEFI (once with Dual UEFI/BIOS mode enabled and once again with it disabled). End Format: FAT32"
Yes, there's some confusion in the thread, but.....not us.
I do thank you for coming back and explaining what worked for you, that's commendable because many fail to do so.
WOW. Just WOW!
"Yep, that's what you were told here too."
- uhh, exactly when was I told that vital piece of information that my problem was installing a 32 bit when it should have been a 64? Go ahead. Find this information of exactly who said this to me BEFORE I found the solution out from another site - but before you go wasting my time any more, do everyone here a favor and check the dates and see if it was posted before I found out the solution from a better source and posted it here! You're just playing MONDAY MORNING QUARTERBACK!
"And how is that different than you were told here: "If this is for Linux, then any UEFI capable 64 bit LIVE version should boot OK. If it's 32 bit and MBR, you MUST boot Legacy."
- uhh, perhaps it's different because I posted the solution to my problem on Dec 10th PST and your suggestion was posted 2 DAYS LATER on Dec 12th! Struggling with chronology are we?
"You also now post " I was so preoccupied with fixing the Windows 8.1 laptop that I never bothered to reformat my flash drive to GPT and FAT32 " Yet at the first you said the opposite."
- YES because everything I mentioned in my first post was directly performed on my Win 8.1 laptop and NOT my Win 10. That's what the original post was and has always been about! I never said I had performed all of the same steps for my Win 10 laptop, I only said I was experiencing the same problem with the UEFI booting in my Win 10 as well. You are just assuming all of the steps I mentioned were also performed on my other laptop as well when I never stated such a thing! That's like assuming I was installing a Windows 10 32 bit on my other 64 bit laptop when I never made any mention of any specifics about my other laptop. You're just going off topic and making assumptions.
I gotta say I'm very disappointed with all of the sub-par responses I received here from everyone as none of the other forums I posted on (original question posted VERBATIM!) struggled the way people here have. Good lesson learned (seeing how I'm a new member here and all) to only post on CNET as an absolute last resort as the level of confusion, miscomprehension and possible trolling is pretty ridiculous here! I'm done spending any more time on this post as I have already answered my own question. Now I'll let you get back to calling some more Monday Morning Quarterback plays.
Same problem any help ?
I am still nclear on how this will go through.
I am facing the same option, my drivers automatically crashes and I am back to stage one. Any help would be appreciated.
why not use Legacy Mode?
If this is for Linux, then any UEFI capable 64 bit LIVE version should boot OK. If it's 32 bit and MBR, you MUST boot Legacy.
Have you followed the steps in my "SOLVED!" post?
You want to make sure the partition scheme and file system of your flash drive is formatted correctly in order for your driver to read it in Secured Boot enabled / Legacy Support disabled mode.