New
#20
Ahh, it was secure boot. I don't remembr ever disabling that in the last several VMs I've made....
Ahh, it was secure boot. I don't remembr ever disabling that in the last several VMs I've made....
That's one of those defaults Microsoft has got wrong; you need to disable Secure Boot which by default is enabled when creating a Generation 2 Windows 10 VM.
Is this a recent change? All my VMs are gen 2 and I haven't had to do that yet.....
Just curious. It's going along installing now....
It should work, and has earlier worked, but since a few builds it has been like this: if you want to install 10 on Gen 2 VM, you need to disable secure boot.
I have noticed that the*uup download files contain Pro files and Pro N files. Does this mean you can now use N versions on*the Insider Program?
WOW, this new build converted to ISO is significantly smaller than the previous one (15007 - 4.17GB vs 15014 - 3.80GB). That is HUGE! A lot of cleanup has happened.
Thanks Kari for the reminder about secureboot, I tend to forget that. Probably because I have not used Hyper-V for a while.
Thanks for sharing UUPtoISO.
The batch file UIPtoISO.cmd hangs up before showing the menu on my computer. Looks like a localization issue (FR).
After having switched single quotes into double quotes, the menu shows up. After keying "1" however, I'm stuck with:
Can't open ".\UUPs\~3" read-only: No such file or directory.
I'm guessing this has to do with line 331:
for /f "usebackq delims=" %%b in (`find /n /v "" temp\uups_esd.txt ^| find "[%1]"`) do set uups_esd=%%b
Does this means that the script failed in escaping double quotes?
It seems in addition that a few pairs of single quotes were "added".
Any hint?
Last edited by qilex; 23 Jan 2017 at 12:22.
Can't say anything before I have tested the batch in other language versions of Windows. Can't think language causing issues, commands in Windows batch files, PowerShell, VB and other scripts are universal, in English.
If you have not upgraded yet you might want to check if ESD to ISO works for you instead, see this post in ESD to ISO tutorial for instructions in discarding UUP upgrade and download ESD upgrade instead: ESD to ISO - Create Bootable ISO from Windows 10 ESD File
Unfortunately switching to ESD when UUP upgrade has already been downloaded means that upgrade process starts from beginning, downloading everything again.
Oups!
Your script is working fine.
Directory "C:\Rtools\bin" is included in the system PATH and contains a gnu find.exe. Strangely enough, when I manually launch the command prompt with administrator privileges, the correct find.exe from Windows is used. When your script launches a console with runas=1, the gnu find is used. So, the issue was very specific to this computer.
Thanks again for your time