LOL how caould my post be so completely misunderstood. What I did was to agree with you, then linked to post that shows how to get from recovery mode boot to Command Prompt to install. In addition, I linked to a tutorial that shows to other users how to do what you did, install from another partition instead of USB or DVD.
No, but I've made a video about it. Quote from our video thread:
Kari
UUPDUMP is great but sometimes when a build comes out some files are missing like the ssh files on last build. However, the repository is usually updated in a couple of days.
@KariNote
Geeks, I have not had time to update UUPtoISO tool. I will do it before the end of the week. With these new builds (Fast & Skippy) released today February 15th (14th on the wrong side of the big pond), download latest converter from my OneDrive and use it instead of our tool: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Kari
I created an ISO from 17101 using this converter, and still it boots to the keyboard layout. The process looked identical to the UUPtoISO tool process. What am I missing?
Has anyone successfully done this process with build 17101 or 17604? Either with the downloaded files from the update or from MiniDump. Created bootable media and not go straight to the keyboard layout screen. Anyone?Geeks, I have not had time to update UUPtoISO tool. I will do it before the end of the week. With these new builds (Fast & Skippy) released today February 15th (14th on the wrong side of the big pond), download latest converter from my OneDrive and use it instead of our tool: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Kari
I've built the .ISO for 17064 using the winlib 6 .ZIP Kari linked - I'll try to get it to boot later this evening and see what happens, both off DVD as well as USB.
Also, when I double click that convert-UUP.cmd, it automatically asks for elevated privileges. I don't manually run as Admin. AShouldn't be a factor, unless the machine you're trying this on has a goofed Admin account (but then it should also be funny when not forcing it to run as Admin and letting it elevate itself)....
Yes, I have too, for previous builds. It's just 093 and 101 that still break. That's why I was wondering if anyone had actually done this successfully, all the way thru, with 17101. Can't find anybody who has, so I don't know if it really works, for these builds.
No, don't think the account is messed up in any way. I'd see more issues than this.
Made some encouraging progress. I started by downloading uupdump files as my starting point
When I created iso using uuptoiso and the winlib6 link from @Kari, both isos were exactly the same size to last byte and both exhibited the "jump go keyboard" erroneous behavior. I concluded uuptoiso and winlib 6 are effectively the same.
I then used winlib version 14 which I downloaded from web myself (did not save link though) and tried it again and this time it created an iso which was a little bigger than before, and had slightly different options. This iso worked properly.
So, as stated earlier it seems to be winlib 14 you need.
@Kari - is it possible you gave us the wrong link?
Even if winlib 14 is correct version, I am not sure about its robustness as I had problems with it falling over but I did redownload uupdump files and iirc, first time I downloaded all editions but this time chose just the PRO option.
So I have now successfully used uupdump with winlib 14 version.
Quote
