Announcing Windows 10 Insider Preview Build 15019 for PC Insider

For the first time I can remember the current Insider Build 15019 is also the Canary build. I doubt that we will see a new rbuild this week.

I have been able to upgrade both VMs on my remote server - Virtualbox and VMware. It's mostly a matter of patience. For the initialization hang I followed guidance and stopped the Windows Update service and rebooted. The performance of both VMs is greatly improved over 15014.

I was also able to use VMware Converter to virtualize my physical instance of the current IP and then used Starwind Converter to create a .vhdx disk from the .vmdk disk. I'm running it on Hyper-V in my Windows Server 2016 partition. I just remove Virtualbox and VMware products nested WS and VB don't make a lot of sense.


There are many changes in this Hyper-V instance. One example - the only power option is "disconnect". Of course I can turn off the VM using the Hyper-V manager. Then there is the activation question ....

Geeks, seriously, this Command Prompt vs. PowerShell is interesting but let's not forget the facts: Command Prompt will be an integral part of Windows into far future, as will PowerShell. They both have their own function, both suiting better than the other for certain tasks.

I just updated my Windows 10 Pro Build 15019 using PowerShell. Works far better and makes hiding / not accepting certain updates much easier than using Settings > Windows Update:

As I realise this is not known to most users, I will start making a tut right now. Should be written in a few hours.

martyfelker said:

Then there is the activation question ....

There is no activation question.

Each virtual machine is an individual machine, like any other individual PC on your network. If you create a new VM, like virtualising a physical PC with any P2V solution and making a VM of that, the VM created will of course not be activated regardless what the original physical machine's activation status was. The machine (VM created from P2V VHD) is new with new hardware signature, there exists no digital license / hardware signature for that new machine.

If you have an activated host and you install the same edition on a VM on that host on a new VM, it will of course not be activated.

If you have an existing activated Windows 10 on an existing VM, you can clean install on that same VM and the new fresh install will be automatically activated based on that virtual machine's hardware signature and that machine's Windows 10 digital license.

If you have an activated Windows 10 on an existing VM and you replace the Windows installation on that VM restoring a P2V image or other system image of the same edition, it will be automatically activated based on that virtual machine's hardware signature and that machine's Windows 10 digital license.

You seem to have a strange belief that if you run virtual machines on an activated Windows 10 host, those virtual machines will be automatically activated, or that if you activate one virtual machine then all virtual machines will be activated. That is absolutely not the case; each virtual machine has its own hardware signature and requires its own license.

Kari

FWIW, the 4 VMs I created in 4Q 2016 were all created using Windows 7 Pro keys from my old Tech Net subscription, and all accepted those keys with very few issues (one key gave me fits, but using it to create a VM two weeks ago worked fine), so if you have old Win 7 / 8 keys for old machines lying around that you haven't yet upgraded to 10, give them a shot.

martyfelker said:

For the first time I can remember the current Insider Build 15019 is also the Canary build. I doubt that we will see a new rbuild this week.

I have been able to upgrade both VMs on my remote server - Virtualbox and VMware. It's mostly a matter of patience. For the initialization hang I followed guidance and stopped the Windows Update service and rebooted. The performance of both VMs is greatly improved over 15014.

I was also able to use VMware Converter to virtualize my physical instance of the current IP and then used Starwind Converter to create a .vhdx disk from the .vmdk disk. I'm running it on Hyper-V in my Windows Server 2016 partition. I just remove Virtualbox and VMware products nested WS and VB don't make a lot of sense.


There are many changes in this Hyper-V instance. One example - the only power option is "disconnect". Of course I can turn off the VM using the Hyper-V manager. Then there is the activation question ....

Marty, could you explain, please, how you determined this? Very interesting.....

the current Insider Build 15019 is also the Canary build.

eddward said:

10 days old Canary build.

Can you expand on that a bit??