New Windows 10 Insider Preview Fast+Skip Build 18985 (20H1) - Sept. 19 Insider

Caledon Ken said:

Attachment 248509

No drive letters in Navigation pane or detail pane.

As this is just an insider build that I poke at I'll wait until they fix. I don't have iso for repair although I guess I could get. Thanks Andre.

Glad you posted this. I have the same annoyance in Windows 10 for Workstations.

IronZorg89 said:

Sorry I misunderstood your post, but I don't think it is worth the hassle of going back two builds prior. As you mentioned you are better off waiting the next build or try a repair install from an .ISO from UUPDump — I am not sure MS already has the .ISO for the current one (18985-21H1)

- - - Updated - - -



Thanks for the clarification about upgrading a VM, but I will certainly have a look at your refrenced link about the matter. Keep up the good work.

Cheers!

Additional clarification - you cannot just take the VHD created as a dual boot option and run it in a VHD without creating an EFI partition (for UEFI) or system reserved partition (legacy bios) so you can boot VHD in VM to upgrade it.

Several ways to do this but easiest is

1) install OS in VM first (using VHD format)

2) once finished, close VM, and mount VHD as a drive (say it has drive letter E)

3) create boot entry for VHD by typing following from admin command prompt

bcdboot E:\windows /p /d

The parameters after bcdboot ensure the existing installation remain the primary boot starting installation.

When you boot to second installation first time, it takes a while whilst resolving drivers.

If you do create the dual boot first using the tutorial method, it is a bit trickier making it bootable in a VM.

cereberus said:

Additional clarification - you cannot just take the VHD created as a dual boot option and run it in a VHD without creating an EFI partition (for UEFI) or system reserved partition (legacy bios) so you can boot VHD in VM to upgrade it.

I just added this note to both video post showing how to deploy Windows to a native boot VHD, and to this tutorial: Native boot Virtual Hard Disk - How to upgrade Windows:

   Note

When creating VHD file to be used in native boot, always use MBR partitioning! To upgrade Windows on native boot VHD, it must be temporarily attached to a virtual machine. An MBR partitioned VHD is easy to attach to VM, it only needs Windows partition to be marked active, whereas a GPT partitioned VHD with only a single partition for Windows requires manually creating system partitions before it can be used on VM.

If you for any reason want to use a GPT partitioned VHD in native boot (can't think any valid reason!), it is better and recommended that you first create a Generation 2 VM in Hyper-V, installing Windows 10 on it. This takes care of the partitioning, doing it correctly. The VHD can then be used as native boot VHD, or on a VM.

cereberus said:

If you do create the dual boot first using the tutorial method, it is a bit trickier making it bootable in a VM.

It is not tricky at all, if and when using MBR partitioning when creating native boot VHDs. Easy and fast. See steps 1.14 through 1.17 in above linked tutorial.

Kari

cereberus said:

Additional clarification - you cannot just take the VHD created as a dual boot option and run it in a VHD without creating an EFI partition (for UEFI) or system reserved partition (legacy bios) so you can boot VHD in VM to upgrade it.

Several ways to do this but easiest is

1) install OS in VM first (using VHD format)

2) once finished, close VM, and mount VHD as a drive (say it has drive letter E)

3) create boot entry for VHD by typing following from admin command prompt

bcdboot E:\windows /p /d

The parameters after bcdboot ensure the existing installation remain the primary boot starting installation.

When you boot to second installation first time, it takes a while whilst resolving drivers.

If you do create the dual boot first using the tutorial method, it is a bit trickier making it bootable in a VM.

Kari said:

I just added this note to both video post showing how to deploy Windows to a native boot VHD, and to this tutorial: Native boot Virtual Hard Disk - How to upgrade Windows:

   Note

When creating VHD file to be used in native boot, always use MBR partitioning! To upgrade Windows on native boot VHD, it must be temporarily attached to a virtual machine. An MBR partitioned VHD is easy to attach to VM, it only needs Windows partition to be marked active, whereas a GPT partitioned VHD with only a single partition for Windows requires manually creating system partitions before it can be used on VM.

If you for any reason want to use a GPT partitioned VHD in native boot (can't think any valid reason!), it is better and recommended that you first create a Generation 2 VM in Hyper-V, installing Windows 10 on it. This takes care of the partitioning, doing it correctly. The VHD can then be used as native boot VHD, or on a VM.

It is not tricky at all, if and when using MBR partitioning when creating native boot VHDs. Easy and fast. See steps 1.14 through 1.17 in above linked tutorial.

Kari

Thanks very much to both of you for the added insight, but right now I am facing another issue after dual booting. The partition I want to use for Insiders Program is giving me a screen resolution problem. I don't seem to be able to download AMD Catalyst driver in order to use Catalyst Control Center for scaling the resolution. Every time, I end up with an Access denied error: "Failed to load detection driver" and also you don't have permission to Access "URL of AMD's" site on this server. So far, I cannot find a solution to this problem and it is driving me out of my wits' end.

Concerning the VHD and VM upgrading, I will have to sit down a day free of any obligations to make sense of all of this. Sure, maybe I will post in the forum for questions related to steps I don't understand. Hopefully you will be there to give some guidance.

Cheers guys!

Just upgraded a 18970 VM of Windows 10 for Workstations with a 1 TB virtual drive using WU. Good thing WU is because I have had problems with creating the ISO of this build using UUPDUMP.

Here's the error I am getting (in linux(

ERROR] "/Windows/WinSxS/msil_taskscheduler.resources_31bf3856ad364e35_10.0.18980.1_en-us_a39729854e72140d/TaskScheduler.resources.dll": blob not found
SHA-1 message digest of missing blob:
7dc626b1dd92fbfe2c0a302a8776f3c32327c308
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.



The way I interpret the stuff about internal 20H2 builds is that Skip Ahead should reopen in a month or so. We will see.

Microsoft User Research session for Windows 10 Touch Keyboard

I am now updating a 18970VM created in 5 minutes with the Gnome-Boxes that comes with Gnome 3.34. Fasted upgrade I've yet encountered. I recommend Gnome-boxes in the new Gnome desktop for a different and very pleasing virtualization experience.

Windows 10 SDK Preview Build 18985 available now - September 24