-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB stick hangs on boot #1097
Comments
Thanks for the report.
|
Just downloaded the official The As you can understand, since there's no telling in what incompatible manner non-official ISOs of Windows 10 may have been modified, I cannot support non-official ISOs. If you want to install Windows 10 Edu or Windows 10 Enterprise, please download the official ISO using one of the methods highlighted above, as at the very least you should be able to create the bootable USB using FAT32. I will now close this issue. |
I can assure you that I definitely am ;-) This ISO is downloaded from Microsoft's website via my Action Pack subscription. My license keys don't work with any other images. You won't be able to download anything without an active configured subscription, but here's the URL: https://msppdd.microsoft.com/msppdd/Home/Downloads?selectedType=OnPremise This
I was able to get
I got the
So, armed with a smaller As a side note, I find it odd that the USB stick appears twice in the available boot devices list. I tried building a new ISO for Rufus, using the guidance found here: http://forum.imgburn.com/index.php?showtopic=1779 — BEGIN WARNING — The last release of the oldish, but still excellent, ImgBurn bundles OpenCandy malware in its installer. (More on OpenCandy: https://en.wikipedia.org/wiki/OpenCandy) The safe recommendation is to use 7Zip after downloading to extract the .EXE from the installer. FYI this trick doesn't work for all installers, but we at least got lucky with this one. ImgBurn doesn't require any supporting files, libraries or configurations; the .EXE runs standalone without installation. — END WARNING — Rufusing up that ISO didn't work either, although with the smaller So I undertook to burn it to a DVD-R. The burn/verify went off smoothly, but alas I find I'm unable to configure for DVD Boot in my UEFI settings. I have to switch to Legacy to get that. It's starting to look like I'm running out of options for UEFI (which I'd like to use if at all possible). I did find this: So I may yet be able to get a PXE boot. We'll see... Since I've been able to show that I'm using an official Microsoft ISO—alas, no checksums available—you may want to consider reopening the issue. But that of course is up to you. Thanks for going to the trouble of downloading and testing that other ISO. |
It's a Dell Inspiron I purchased new about three years ago. See attached.
Absolutely. When it hangs on |
It's working now. Apparently something's gone wonky with my USB hub. When I boot with it unplugged, I can load the USB stick. I can even load So you'll probably want to keep the issue closed. Thanks for your assistance/understanding. Great utility you've got here. Keep up the good work. |
Glad you managed to sort it out, and sorry about thinking that you were using a non official ISO. I hadn't seen a combined Education + Professional + Enterprise from Microsoft, and usually, these tend to only be found in unofficial AIO (All-In-One) ISOs, which is why I assumed wrong. But can you please tell me the MSDN name of that ISO (something like As to your issue, I guess your wonky USB Hub is creating an issue with your UEFI firmware during device enumeration, hence the hangup. It's good to have this information, as I'll be able to tell users who run into similar symptoms to try unplugging all other USB devices they have, so thank you very much for your report and for sharing your findings. |
YW, glad I can help :-) Here's the filename:
...and here's the SHA1 hash:
But I don't think you'll find it on MSDN. At least for my subscription, there's no Enterprise 1709 ISO. |
Just checking in... Do you need anything more from me? |
Okay, according to the SHA-1, I created a UEFI:NTFS bootable USB from that image and tested it on an intel NUC, after plugging it to a USB 3.0 4-port hub, and saw no issue with the UEFI:NTFS boot. Windows was able to load as expected. Therefore, I can only confirm that the issue has to do with your environment. But thanks for the details. |
Yes, I agree. I'm now running on a clean Windows reinstall, originating from a Rufus-created USB stick using that same ISO—after I unplugged my USB hub. (I decided to forego the WIM extraction; that operation has been relegated to an interesting exercise.) This was a good follow-up, Pete... I wonder where you get the time. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
Log
button in Rufus and copy/pasted the log into the line that says<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
#
button (at the bottom of the Rufus interface), to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image. (unable, Microsoft won't publish a hash for this ISO; repeated frustrating calls reveal that support staff doesn't know what a hash is)Issue description
*** UEFI:NTFS (x64) ***
Log
The text was updated successfully, but these errors were encountered: