UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files  

EQuito said:

Hi HippsieGypsie and thanks for the link.

Unfortunately, I can't use that fix because I'm using Legacy mode and MBR due to Acronis having trouble backing up GPT partitions, actually restoring them.

The thing is, I've done this hundreds of times so I don't understand why this particular build is failing.

Actually, you can. You jsut skip the one step where you run convert gpt. Read me full response below.

HippsieGypsie said:

You're welcome. Sounds like it's a bug for some. May relate to BIOS? I'm quite sure, but I think you can still use commands for MBR scheme. Worth a look into. Don't hesitate to post on the tutorial thread I linked. I'm sure Kari or someone would be willing to help. Using @ Kari without the space between will alert him. Good luck.

Hippy is 100% correct.

My machine, listed under system specs for first machine, is an old machine I built 6+ years ago, using a CPU that is now ~9 years old (Core i7 965 EE) and a mobo that is 7 (eVGA X58 Classified 3). The mobo only has BIOS so I am unable to use GPT as a boot drive for Windows 10, but I have all my other drives converted to GPT for future proofing (on non-UEFI-based machines, you can still use GPT for storage, just not to boot - to boot from GPT you must have UEFI.

However, those instructions in that tutorial are pretty much what I follow, although I do it on my own without any predefined scripts.

Here is my methodology (I use the entire disk, not a single partition, for my installs, so I use a partition-destructive method to install. If you are not using an entire disk to install to, don't follow these instructions.

1. Boot to Windows 10 Install Media
2. Perform all steps necessary to get to the drive selection UI, including skipping entering a key, selecting clean install, as well as making the choice of the installation type (architecture / version, such as x64 Pro or x86 Home)
3. When at the HD selection GUI, use SHIFT + F10 to open a command prompt window
4. Type
   Code:

   diskpart

   and hit Enter
5. Type
   Code:

   list disk

   and hit Enter
6. Find your disk number that you are installing Windows 10 to, then enter
   Code:

   select disk #

   , where # is the number of the disk you want to install to (recommended to have only that disk connected, but I do this with 6 physical discs connected, so if you pay attention it's not hard)
7. Type
   Code:

   list disk

   and hit Enter to verify that the disk you want to install to is now selected (should be a "*" character to the left of the disk number)
8. Type
   Code:

   clean

   and hit Enter - it may take a couple of moments (even a few minutes depending upon HD speed) before it comes to a prompt again
9. Type
   Code:

   list disk

   and hit Enter - now the disk you have selected should show the same amount of space in both size and free columns.
10. Type
    Code:

    exit

    twice to close out CMD
11. Click on the Refresh button for the GUI to see the new unallocated HD
12. Select unallocated HD and continue the installation

At this point, the installation continues by creating the partitions that it wants to on the disk and moves on. Since you're clean installing, this is the optimum way to go.

If this does not work, however, grab an .ISO of 16299, do the above exactly the same, and get 16299 installed, then use your .ISO of 17063 to upgrade it.

HTH

EQuito said:

Hi HippsieGypsie and thanks for the link.

Unfortunately, I can't use that fix because I'm using Legacy mode and MBR due to Acronis having trouble backing up GPT partitions, actually restoring them.

The thing is, I've done this hundreds of times so I don't understand why this particular build is failing.

You must be using an old version of Acronis.

Ditch it and use superior and reliable Macrium Reflect Free.

You can convert legacy bios installs to uefi (mbr to gpt).

Tutorials for both in tutorial section.

EQuito said:

First of all, thank you all for your prompt responses and willingness to help.

Secondly: I'd like to summarize all my replies here so I don't take too much space on this thread.

But first a bit of background so you understand where I'm coming from:

I'm 58 years old, so if you're also old and geeky enough, you may remember me from the Icrontic Forums or APU's days when my Abit NF7s bios mods were pretty popular during the infancy days of OC'ing.
Anyway, I left the US, move back to my native country in 2005 and basically my knowledge and hardware didn't progress since until last year, when I bough my first 64bit machine, the one in my signature. My old trusty Dell Inspiron 9300 laptop served his purpose and still does, thus why I still use and old copy of Acronis 2009 32bit which also works just fine for my needs. So, all this UEFI and GPT stuff is pretty new to me and a bit hard to understand so I prefer to keep using the Lenovo 64bit in legacy bios and MBR mode.

OK, back to the issue at hand: HippsieGypsie's and johngalt's advise where very helpful resolving the partition issue but in the end it didn't work. After the first reboot, I got a GSOD, tried again and got a never ending black screen.

My theory as what's going on:

Build 17046 is the first one ever (since January 2015) to failed in both my 32bit and 64bit machines, therefore I think Microsoft is purposely blocking and/or phasing out old hardware not using UEFI bios and/or GPT mode. That would explain the huge amount of failed installs since Build 17025.

So, even though I prefer clean installs, I'll just continue to update from within Windows and try not to worry about it too much.

Once again, thanks for your help. Merry Christmas and a Happy New Year to you all!Cheers!

Firstly, it does not matter in the slightest if an install is uefi or legacy bios when it comes to installing any version of Windows 10.

You have absolutely nothing to back up your theory.

Secondly, UEFI installs offer several advantages so you should consider moving to it.

Thirdly, the Fast Ring is not for users who do not wish to, or are unable to cope with significant risk of things breaking. Given your comments above, I have to say you need to seriously think about whether the Fast Ring is for you.

Finally Acronis 2009 is so old. You really cannot trust it any more. It certainly will not work on UEFI installs if you did move. Ditch it and move to Macrium Reflect Free or similar, or buy new version of Acronis.