Waco wrote:Just because you can doesn't mean you should.
Indeed, but a great many of us here can. We really, really can.
Personal computing discussed
Moderators: renee, Flying Fox, Ryu Connor
Waco wrote:Just because you can doesn't mean you should.
just brew it! wrote:Ryu Connor wrote:Meerkt has likely done this, he's fairly technical, it aids him in his adventures.
This just struck me as insanely funny for some reason. Yes, I'd say many of us embark on "technical adventures" from time to time...
(My day job probably qualifies too...)
Ryu Connor wrote:churin wrote:Thank you all for your replies.
I tried the above suggestion and got "Boot files successfully created" message after executing the suggested command. But the Windows 10 is still no boot.
This is a desirable solution if it works since it avoid wiping out installed application softwares. Any further suggestions?
Hmm. I think I know what's happening. I'm guessing your system is using UEFI boot, GPT partitions, and your C: drive is NTFS. That won't work, winload.efi can't launch from NTFS.
Boot into WindowsPE
Use Diskpart to shrink the partition by 100MB.
Create a 100MB EFI System Partition using Diskpart.
Format it in FAT32.
Assign a drive letter
Run the bcdboot command.
just brew it! wrote:You've probably already spent more time trying to repair it than it would've taken you to wipe it and start over.
DancinJack wrote:Waco wrote:Reinstall from scratch. It's the easiest method to ensure you don't have trouble in the future. Also, stop screwing around with things you don't understand unless you have a good backup strategy first.
The reason I have suggested this multiple times now is the OP deleted the system and recovery partitions not knowing what was going on with them. I just don't see how diving into diskpart, cloning, and recreating partitions is a good idea in this case.
Anyway, obviously, I agree with you Waco. Just reinstall clean and be done with it.
jihadjoe wrote:How did you originally install Windows on that machine?
I imagine if you back up your C: partition, then re-doing the original install procedure will re-create the hidden system partition along with a C: that you can restore your backup to if you'd rather not re-install all your apps and reconfigure your settings one by one.
churin wrote:jihadjoe wrote:How did you originally install Windows on that machine?
It was several months ago and I do not remember how. There appears to be two ways of clean-install with two different end results. If you specify partition size, installer creates extra small partition AHEAD of the main partition and places system file on the extra partition. If you create a partition before launching installer and pick that partition, then no extra partition is created. Is there any other way for clean install?I imagine if you back up your C: partition, then re-doing the original install procedure will re-create the hidden system partition along with a C: that you can restore your backup to if you'd rather not re-install all your apps and reconfigure your settings one by one.
The above is valid only if the partition referred to as "hidden system partition" is indeed the system partition. Isn't system partition placed ahead of a main partition? Note that the partition I deleted was right side of the main partition as shown on disk management graphic.
just brew it! wrote:churin wrote:jihadjoe wrote:How did you originally install Windows on that machine?
It was several months ago and I do not remember how. There appears to be two ways of clean-install with two different end results. If you specify partition size, installer creates extra small partition AHEAD of the main partition and places system file on the extra partition. If you create a partition before launching installer and pick that partition, then no extra partition is created. Is there any other way for clean install?I imagine if you back up your C: partition, then re-doing the original install procedure will re-create the hidden system partition along with a C: that you can restore your backup to if you'd rather not re-install all your apps and reconfigure your settings one by one.
The above is valid only if the partition referred to as "hidden system partition" is indeed the system partition. Isn't system partition placed ahead of a main partition? Note that the partition I deleted was right side of the main partition as shown on disk management graphic.
It probably put it after the main partition because you told it to install to a pre-existing partition at the beginning of the disk (so it had no choice).
I clean installed W10 Pro-v.1607 on 100GB partition in 250GB SSD. I do not remember whether the partition was created before the installation or during the installation.
churin wrote:One thing I forgot to mention when I replied to your post: The WinPE did not boot from the machine where it was created using a working W10 system. I know by experience, this machine does not allow GPT to boot.
I have another machine which appears to have UEFI, tried. and found it to boot the WinPE. I carried out what you suggested on the machine. But the result was that the problem system did not boot on either machine.
I wonder why the partition for the WinPE is GPT even it was created on BIOS machine not UEFI.
Motherboards involved are GA-97A-UD3 and GA-970A-D3. The spec said both come with Hybrid EFI. The WinPE was created on the former but could boot only from the latter.
Yan wrote:I've certainly forced Windows 7 to use a single partition, by partitioning first and then telling Windows to install in that partition. This was with BIOS/MBR, though.
Ryu Connor wrote:Diskpart can create an MBR disk that is a singular giant partition. You can then direct the installer to place Windows on your created partition. This will install Windows without creating a system partition (boot files) or a recovery partition (winre).
TheRazorsEdge wrote:EFI has been solid for 15+ years now, so I'm honestly surprised anyone uses BIOS anymore. It offers nothing aside from compatibility with ancient hardware--most of which won't run under a modern OS anyway.
just brew it! wrote:The spec's been mostly stable for nearly that long, but actual implementations that don't suck didn't become common until much later.
TheRazorsEdge wrote:Then Vista/7 came along, and Microsoft broke legacy compatibility pretty hard. There isn't much reason to run BIOS on anything built for Win7+.
Waco wrote:Unless, of course, you started a Windows 7 install on a legacy platform and upgraded it to Windows 10 on a newer platform. My personal machine at home still boots via legacy mode simply because MS couldn't get the upgrade process correct for the transition. Someday I'll reinstall from scratch, but that day isn't today.
Waco wrote:TheRazorsEdge wrote:Then Vista/7 came along, and Microsoft broke legacy compatibility pretty hard. There isn't much reason to run BIOS on anything built for Win7+.
Unless, of course, you started a Windows 7 install on a legacy platform and upgraded it to Windows 10 on a newer platform. My personal machine at home still boots via legacy mode simply because MS couldn't get the upgrade process correct for the transition. Someday I'll reinstall from scratch, but that day isn't today.
Aranarth wrote:In the latest version of windows 10 there is now a mbr2gpt tool and there are directions for how to convert legacy boot to eufi or secure boot using that tool.
I haven't tried it yet but it sounds quick and easy.
Ryu Connor wrote:churin wrote:One thing I forgot to mention when I replied to your post: The WinPE did not boot from the machine where it was created using a working W10 system. I know by experience, this machine does not allow GPT to boot.
I have another machine which appears to have UEFI, tried. and found it to boot the WinPE. I carried out what you suggested on the machine. But the result was that the problem system did not boot on either machine.
I wonder why the partition for the WinPE is GPT even it was created on BIOS machine not UEFI.
Motherboards involved are GA-97A-UD3 and GA-970A-D3. The spec said both come with Hybrid EFI. The WinPE was created on the former but could boot only from the latter.
WinPE can be built to only boot GPT, MBR, or both.
If you use a WinPE that boots MBR, you can't rebuild a GPT boot.
If you use a WinPE that boot GPT, you can't rebuilt an MBR boot.
If you use a WinPE that can boot both, you must boot from the correct option to make the repair.
churin wrote:I created another bootable WinPE USB on GA-97A-UD3 and found it boot on either of the motherboards. The spec says both mobos have Hybrid EFI but one comes with MBR interface and another with UEFI interface. I wonder why I did not see any option to select GPT or MBR when booting the WinPE.
alexanoin wrote:Seems I have the same issue with OP. I am trying to boot into a UEFI based computer with the reset disk. but no account was found on the computer as well as OS.