Successful Install of Windows 10 using Command Prompt after Many Errors

I kept getting a media driver error after clicking the install button from multiple builds using a bootable USB. I tried downloading a new ISO from Microsoft, no luck (SHA-1 was exact). Using Microsoft’s USB creator, Rufus, Unetbootin, and using DISM to slipstream my laptop drivers into the boot.wim file with no luck either. Here’s what I ended up doing after having Windows 10 install failing with builds 9926, 10041, and the build prior to 9926 (can’t remember the number).

Now it might be slightly different for your setup as I was installing this as a dual boot on a laptop with a 500GB HDD currently running Windows 8.1. If you already have a second drive or partition to install to, just skip to step 4. If you want to do a clean install and have a Windows 8 recovery drive, boot to it and skip to step 5. If you have a Windows 7 disc, you can probably use that to boot to a command prompt for a clean install or dual boot (I just don’t have a Windows 7 machine right now to test).

  1. Open Disk Management

  2. Right click your C: partition (or largest one), and select shrink volume (You typically want Windows 10 on a partition after the one that holds Windows 7/8)

  3. Select partition size in MB (I entered 100000MB for roughly 100GB)

  4. Charms Bar > Settings > Change PC Settings > Update and Recovery > Recovery > Restart Now (Make sure bootable media is in the drive (USB\DVD)

  5. Troubleshoot > Advanced Options > Command Prompt

  6. Select account with Administrator rights and login with password (if prompted)

  7. Diskpart > list vol > note install media drive letter > exit

  8. X:\setup.exe (x = your install drive media letter found in previous step)

  9. Now you’ll see the Windows 10 setup. Happy Installing J

When I ran Windows update and went from build 10041 to build 10049 (fast update option), it took somewhere around 5.5 hours just for the install. There were a few times I thought it was stuck, but I just let it go. So for a heads up if you haven’t seen the issues from others, the upgrade to build 10049 is going to take forever. So be patient and let it do its thing. After the update there was 30GB used with 11.1GB of that from the Windows.old folder. You can delete the Windows.old folder if you don’t plan on rolling back to the previous build.

 
Discussion Info

Last updated August 16, 2018 Views 31,366 Applies to:

Firstly.... why go to all that trouble just to execute the setup file...? You only need to open the iso to reveal the folders... open the sources folder and scroll down to setup and double click it.

However.... as I've said on here I can run the setup file like anyone else... but.... as soon as it does the restart and opens the logo screen the process halts.

There's an issue right at that point for me and the only way to know what the problem is exactly would be to log the process. 

I know that setup logs are created but have no idea how to locate them...???

Nick

“Firstly.... why go to all that trouble just to execute the setup file...? You only need to open the iso to reveal the folders... open the sources folder and scroll down to setup and double click it.”

I know I can just browse to the setup file and launch it. The issue is I don’t want to do an upgrade from Windows 8.1 to Windows 10, I want a dual boot. Plus it was the only way I was able to get it to install with multiple Operating Systems on the HDD.

“However.... as I've said on here I can run the setup file like anyone else... but.... as soon as it does the restart and opens the logo screen the process halts.”

Maybe issues with the in-place upgrade option.

“There's an issue right at that point for me and the only way to know what the problem is exactly would be to log the process. “

I realize the issues you’re having. I noticed in one of your threads that you wanted to run a dual boot with Windows 8.1 and Windows 10. That is exactly what I accomplished with the above walk through. You should give it a try if everything else you tried has failed. I started this to help others as you can see all the trouble I had listed in the first paragraph. I hope if you try it, it can help with your issues too.

“I know that setup logs are created but have no idea how to locate them...???”

I’m sorry, I don’t know where the logs are located at.

You just save my friends academical life, thanks man!