New
#11
I did save the .iso file on the USB stick and tried to mount it. Did not work (although the "mount" command was available).
After I copied the .iso file to the hard disk (data partition), I was able to mount it (using the windows explorer context menu mount command) and then ran the setup.exe as administrator.
Unfortunately with the identical result as with my original tries using the USB stick with the installation package on it create as explained for creating a installation USB stick.
I still get the same error message without any specific or helpful details:
Any further ideas, or do I have to do a full installation with reinstalling of all Apps :-(
The one that was specified further up.
I downloaded the 64bit version of Windows 10 (not the N or the single language version) in German.
Since I have the same problem with the ISO version as with the previously downloaded USB installation (using the installation disk creation tool by Microsoft), I do not think it is related to the installer or the installer medium...
Which of your partitions do you have the ISO physically on? The C: partition (your OS) or the other Data Partition?
EDIT: @markrosa ... reason I'm asking is the space. If you have the ISO on that other data partition, it may be a problem. That partition is at 91% full. Only 9% available. The process requires temporary file space to "do it's thing". 9% is not much and MS may be balking at it being less than 10% available. This is not to be confused with the Windows.old folder that will be created on your C: drive. If the process wants to create it's temp working files on the same partition it was executed from, it may not see enough room to do that, and give you that error message. This is only a S.W.A.G. on my part, but you could try moving that ISO to the C: partition, where's there's plenty of room, and trying again. Only a guess at this point.......
Last edited by f14tomcat; 17 Nov 2016 at 09:58.
The .iso is on the P: partition (sorry, just wanted to make it simpler by naming it D for data in my comment; I failed in that attempt ;-)) which has plenty of space as well (30 GB free on a 48 GB partition; and that is 30 GB free with the .iso already on it). So I doubt, that this could be the reason. But nevertheless, I will try it from the C: partition as well later on...
EDIT: Just tried it. Same result even when .iso is on C: partition and mounted from there...
@markrosa
Your specs say you are running win 10 pro on a surface pro 3. I also am running win 10 pro on a surface pro 3. I am on build 14393.447. What is your build number? WIN KEY + R, enter WINVER.
Your MiniTool partition display is far different than mine. I'm at a loss to explain that. The position of the partitions and the size of your Recovery Partition does not make sense to me. Maybe to someone else.
Here is your Minitool & mine.....
Yours:
Mine:
I'm running UEFI, it appears you are not. This is a little out of my league, but that 360MB recovery may need to be 450MB and windows has no room to expand it.
I'm gonna ask for some input on this one, @essenbe. It just doesn't look right.
@f14tomcat, it doesn't look right to me either. He can't be running an MBR install on a GPT disk, I don't believe. The sizes of the partitions are wrong, it seems and he looks to be missing the 16MB partition. I am not sure what is on Partition 1 either. If it is a recovery partition, he has 2 of them, which isn't uncommon, as you know. The first partition reads Windows RE tools, which may be a partition he created. I have never see that partition on an install.
In the FWIW dept, here is mine.