Yes, this is my sentiment exactly. Can anyone direct me to an iso of 16179? I don't want to wait for them to come up with a solution, as that could take forever and my sys won't do the update. I prefer to just do the update myself. But I haven't seen any iso's of that build online yet. I would really appreciate it.
VMs specially VMWare are as straight forward as they come, I have been running and testing almost any OS, some installed and even some live. Only complications to connect to other drives on same system so I just use backup drives to fetch anything I need. There's at least 2 Linux distros sitting in it right now.
Most testing here appears to be of the "can I install it in a VM, yes, look the start menu is slightly different" level.
Some people use VMs (I do for things that are important to me) some don't.
There aren't ISO released but you can (with 20 seconds googling) download the required bits direct from MS and make your own ISO using a converter which you can get here on TenForums (or elsewhere if you want).
It would be dumb to upgrade your main PC with no backup but I've done it in the past. It depends on your perception of risk and how much you care if it doesn't work.
For me, every singe upgrade has worked and if it failed I'd not care.
If you don't know how to keep your data safe you shouldn't be playing with beta versions.
No VMs for me. I've built all my desktop PCs since the mid 1990s and always have an extra 1 or 2 around that are current enough when something like Insider Preview comes along. So nothing of real value on my Insider box, but I still do image backups at least once per build to protect my time.
Testing a new IP build on those commonly available VM systems, especially Microsoft's own Hyper-V, is something that must happen in the MS Windows development labs hundreds if not thousands of times before the next new build is released to the general mass of those on the Insider Program, and that is probably why Kari can guarantee that an upgrade performed in a VM will work.
However, IMO, that is not what the Insider Program is really about - repeating the work already carried out.
I feel that it should be a test on a sample of the general population of machines, old, new, perfect and faulty, overclocked and underspecified, warts and all, and definitely never likely to be seen anywhere near the Microsoft Windows development labs, and not on a batch of behave-alike virtual machines with a small range of virtual components and devices that only exist in the VMs themselves.
I j ustgot the OK from Brink to share my 16179 ISO. Although I suppose I could use onedrive I'm going to see if I can't share it publically via Dropbox. Microsoft seems reluctant to put up an ISO from the rs3 branch so we should do our parts and not snipe at each other. I am ignoring any future taunting. And it is a fact that Mail is broken on this build - I've confirmed the inability to add Gmail or Yahoo on my Enterprise and Education Virtualbox VMs. So I posted on the feedback hub. But I'm sure someone can confirm the bug here.
Actually, I was hoping to create the ISO file using your excellent UUP-to-ISO tutorial, but got the following error messages in the process:
============================================================
Creating boot.wim . . .
============================================================
Using LZX compression with 6 threads
Archiving file data: 870 MiB of 870 MiB (100%) done
============================================================
Creating install.wim . . .
============================================================
[ERROR] "\Windows\WinSxS\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.16179.1000_none_917c35420446d39a\iexplore.exe": blob not found
SHA-1 message digest of missing blob:
0ef777fcd70c36149adfdbfc19b7c0cd1b98e6fc
ERROR: If this is a delta WIM, use the --ref argument to specify the WIM(s) on which it is based.
ERROR: Exiting with error code 55:
A file resource needed to complete the operation was missing from the WIM.
Errors were reported during export.
Press any key to exit.
A small but important clarification: An upgrade on a fresh, clean installed Hyper-V virtual machine always works. Of course a VM can develop same kind of issues with Windows Update than any physical machine, that's why I recommend doing it as I told earlier: clean install, update, join Insider program, make checkpoint, upgrade and make ISO, upgrade your physical PC with ISO, restore VM checkpoint and wait next upgrade.
Where / when / how have I said / recommended / suggested that you should test Insider builds on a VM? If the goal is to test Insider builds and WU can't deliver the upgrade on your PC, what is wrong in getting the upgrade on a VM, making an ISO and upgrading the physical PC with it?
That's all I have said: if you can't get your PC upgraded, the VM method always works to get upgrade & ISO to be able to upgrade your PC for further Insider testing.
The ESD method has not worked in several last builds. Current upgrades are delivered as UUP upgrades, not as ESD, therefore another tutorial and tool are needed: UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Windows 10 Installation Upgrade Tutorials
Kari
Last edited by Brink; 22 Apr 2017 at 18:36. Reason: removed unneeded comments
Quote
Of course, in the beginning back in 10/2014, I was dual-booting for several months, had to as the first builds were very unstable--until sometime in the spring of 2015, when I felt confident enough to delete my Win8.1 partition.
