Announcing Windows 10 Insider Preview Build 14986 for PC Insider

Kari said:

First, please notice the words highlighted in above quote, the words I forgot and are missing from my post.

OK, a quite simplified explanation:

With Windows 10, Microsoft introduced a new deployment tool called Windows Imaging and Configuration Designer (Windows ICD). It is part of Windows Assessment and Development Kit (Windows ADK).

Deployment and Imaging Tools are also a part of the ADK. It is a set of tools (commands), a set that when run will add special commands to Command Prompt, or rather you use this command add-on in Command Prompt interface.

Two really important components of Windows install media are boot.wim and install.wim files. To create them and write them to a bootable install media I use Deployment and Imaging Tools. First I need to write a WinPE image on my harddisk:

Attachment 112865

WinPE is needed to run Windows setup; extremely simplified you could say it's kind of mini operating system that takes care of install media boot and first phase of setup. After first reboot required by setup, WinPE is no longer needed, it giving control to Windows 10.

OK, when I have WinPE files saved on my machine let's say in WinPE folder on drive E:, and I have my Windows installation files stored on same drive in folder SetupFiles, and I want to create Windows ISO on drive X: with name Build14986x64.iso, I give the following command in Deployment and Imaging Tools (see oscdimg command options):

Code:

oscdimg -m -u2 -bE:\WinPE\fwfiles\etfsboot.com E:\SetupFiles X:\Build14986x64.iso

See @DavidY's ICD video in Ten Forums video thread: Solved Windows 10 instructional videos by Ten Forums members - Page 108 - Windows 10 Forums

That's it, I have now a Windows install ISO file. At least in theory; as I said, I've had a long and unpleasant day and I am feeling extremely exhausted and sick, I simply cannot start testing this today.

Kari

Trying this, Kari.

I set up 14971 in VMware Player. Activated. Update for WIP says not connected to the Internet whereas Network and Sharing says it is.

Perhaps the block mentioned by Dona

fjk61011 said:

Trying this, Kari.

I set up 14971 in VMware Player. Activated. Update for WIP says not connected to the Internet whereas Network and Sharing says it is.

Perhaps the block mentioned by Dona

No, both of my VMs are connected to my virtual switch, and one got the update pronto and the other has not gotten it (just checked a few minutes ago).

The 3^rd VM I have just about finished configuring. I'm going to use the UUP method to download and install the 14986 update and then follow the methods Kari wrote out to see if I can get a working .ISo, which I will test in a fourth VM.

re:14986 - thus far neither Store nor Settings have popped up automatically - anyone still seeing that little issue?

johngalt said:

**NOTE** In this thread and on a few websites, there have been recommendations to edit your registry and set two regkeys to zero. While this may have helped for this particular build, it is important that you restore these regkeys back to their original value if you changed them. This will impact your ability to receive future updates. If you did not make any registry edits, no changes are required and you may skip this note.

About that warning on Microsoft Community, I wonder on what it is based? I mean we have two simple, normal DWORDs with a certain value. One (SupportsUUP) tells if UUP is enabled (value 1) or disabled (value 0), the other (EnableUUPScan) tells system if WU can scan the system to see what needs to be upgraded (value 1) or if scan is disabled (value 0).

I simply do not believe that warning. Of course it's a totally other ballgame if (and when) Microsoft simply stops releasing ESD upgrades. Then we have no choice other than accept the fact that UUP is the method to be used to release upgrades. Until that, I cannot see disabling UUP could cause any issues.

   Warning

Please notice that the above is not a recommendation or suggestion to disable UUP! It's just how I see this, and why I will disable it on each of my Insider machines, real and virtual.

If you want to be sure and take no risks, do not disable UUP in registry.

BTW, EnableUUPScan DWORD will be automatically removed after a reboot when it and SupportsUUP have been disabled (set to 0). A user wanting to enable UUP again must manually re-create that DWORD setting it (and SupportsUUP) to 1.

johngalt said:

But neither VM allows me to use a PIN. I did not know that was a limiting factor of VMs. Because it is a major PITA to have to enter my generated 20 character password every time to log into the VMs....

Hyper-V Enhanced Mode does not support signing in with PIN or picture password. This is because of RDP restrictions; Enhanced Mode is based on RDP and same sign in requirements apply.

Alternative ways to sign in using Enhanced Mode are to set Windows to sign in automatically, or completely remove the password. When removing a user password (local accounts) but still wanting to use Enhanced Mode, the user must be added to Remote Desktop Users group. User without password not in this group cannot sign in in Enhanced Mode.

Hyper-V's normal mode fully supports PIN sign in. All my Windows 10 Hyper-V virtual machines have PIN set to my user accounts and I will always sign in with it when not needing Enhanced Mode.

Kari

johngalt said:

re:14986 - thus far neither Store nor Settings have popped up automatically - anyone still seeing that little issue?

See release notes on opening thread...

Kari said:

About that warning on Microsoft Community, I wonder on what it is based? I mean we have two simple, normal DWORDs with a certain value. One (SupportsUUP) tells if UUP is enabled (value 1) or disabled (value 0), the other (EnableUUPScan) tells system if WU can scan the system to see what needs to be upgraded (value 1) or if scan is disabled (value 0).

I simply do not believe that warning. Of course it's a totally other ballgame if (and when) Microsoft simply stops releasing ESD upgrades. Then we have no choice other than accept the fact that UUP is the method to be used to release upgrades. Until that, I cannot see disabling UUP could cause any issues.

   Warning

Please notice that the above is not a recommendation or suggestion! it's just how I see this. If you want to be sure and take no risks, do not disable UUP in registry.

BTW, EnableUUPScan DWORD will be automatically removed after a reboot when it and SupportsUUP have been disabled (set to 0). A user wanting to enable UUP again must manually re-create that DWORD setting it (and SupportsUUP) to 1.




Hyper-V enhanced mode does not support signing in with PIN. This is because of RDP restrictions; Enhanced Mode is based on RDP and same sign in requirements apply.

Alternative ways to sign in faster are to set Windows to sign in automatically, or completely remove the password. When removing a user password (local accounts) but still wanting to use Enhanced Mode, the user must be added to Remote Desktop Users group. User without password not in this group cannot sign in in Enhanced Mode.

Hyper-V's normal mode fully supports PIN sign in. All my Windows 10 Hyper-V virtual machines have PIN set to my user accounts and I will always sign in with it when not needing Enhanced Mode.

Kari

Yeah, I noticed the missing key on one of my VMs, the one that already updated.

Thanks for the heads up on Enhanced Mode. I did not know that. Now I do.

dencal said:

See release notes on opening thread...

Missed that - thanks.

All three VMs are working, all 3 allow RDP connections, and yet I can only connect to one using RDC. Odd.

The other two my host pretends don't exist - when in fact they do.

shakennstirred said:

I can set Google as my search provider, but it wont search for anything.
set it back to Bing and it fine lol

Edge?

I'm stuck on the make winpe image. My command line skills are a bit rusty.

fjk61011 said:

I'm stuck on the make winpe image. My command line skills are a bit rusty.

That was for kari