New
#700
It seems there would be no new builds this week i. e. uptill 17.00 hours Indian Standard Time on Saturday here in India unless the folks at Microsoft work on a Saturday in which the build no would be 16206 or higher. Let us wait & see.
@DEEPDKHI2
Please see here: Announcing Windows 10 Insider Preview Build 16199 PC + 15215 Mobile Insider - Page 28 - Windows 10 Forums
This thread is for specific questions/discussion of the UUP to ISO conversion process.
(Kari beat me by 2 seconds....)
Just tried to original UUP2ISO with build 16215. It gave me the beep again when I pressed the number 1 on the numeric keypad, then I pressed [CTRL] + 1 (keypad) and then it accepted a normal 1 on the keypad.
I'll try the fixed executable next and then compare the .ISOs to see if there is anything different between them.
I do not know in which words and how often I should tell this!
Note from tutorial (step 3.2):
NoteThere is a bug in builds 16193 and 16199 preventing user to select an option in a script like this tool. All that happens when you press 1, 2 or 3 as told above is a loud beep sound.
If this happens to you, use the temporarily fix posted in this post.
I will remove this notice when Microsoft has fixed the bug in coming builds.
What does that mean:
- The bug is in builds 16193 and 16199, not in UUPtoISO tool. Microsoft's fault, nothing wrong in tool
- Running UUPtoISO tool in both above mentioned builds you need to use the provided fix
- Running UUPtoISO tool in build 16188 or older, UUPtoISO tool works and the fix is not needed
Kari
And I don't know how you want to misinterpret what I wrote. Kari, I'm not a buffoon. I specifically wrote that I used the old tool and it exhibited the same behavior, and that I was going ot use the fixed exe as well.
If you don't understand testing, that's great. But don't go off on your rants on me, I'm doing what I do methodically and purposefully.
Got it?
I already have the new build, and it was a confirmation that the issue in the cmd.exe was not fixed, as simple as that.
I simply repeated known facts: in builds 16193 and 16199 there is a known issue with CHOICE command in scripts that causes the tool not to work. Any further testing is of course OK although completely unnecessary; the bug is known and does not go away regardless however often it is tested,
Running the tool from build 16193 or 16199, the provided fix must be used. Running the tool from older builds it is not needed.
Kari
Yes, and I encountered completely different results this time around form the last time I tried it in this build.
Last time I could get no success until a seemingly random set of characters were passed to the system.
This time, I did exactly as described and it worked. Which means I was also able to view the info that the tool parsed from the folder, which the fix cannot do.
On a side note, did you ever get around to working in the non-choice methodology (input?) that someone else proposed for the batch files?
Honestly, after posting a working fix I have not even thought about it. In that sense I am really lazy: there's a temporary known bug in build or two, I have made an easy and 100% working fix for it, I see no reason to start working on another fix.
Any user is of course free to choose whatever method to get an ISO, the fix I have provided will make it easy now in buggy 16193 and 16199, and hopefully in 16215 or another near future build it is no longer required.
Build 16215 known issues do no longer list this bug so I am quite optimistic.
Kari