Windows 10: Windows 10 instructional videos by Ten Forums members


  1. Posts : 20,035
    Windows 10 Insider Preview Build 17083
       1 Week Ago #1271

    Layback Bear said: View Post
    Once again. Thank you Kari for another fine video.

    Jack
      My ComputerSystem Spec

  2.    1 Week Ago #1272

    Kari said: View Post
    New video: Dual Boot - The Really Easy Way



    This video is kind of sequel for one I posted earlier, in which I show how to install Windows 10 for dual boot on native boot virtual hard disk.

    The new video is the same, except that it shows how to do the same deploying Windows 10 to a physical drive. Difference is, Windows on native boot virtual hard disk cannot be upgraded, whereas deploying it to a physical drive works and acts as any clean installed Windows.

    Commands used in the video:

    To check edition indexes on a Windows 10 ISO:

    dism /Get-WimInfo /WimFile:X:\Sources\install.wim

    X: = the drive letter for mounted ISO image.

    Notice that if using ESD based ISO like the one made with Media Creation Tool, use install.esd instead of install.wim. If you have a dual architecture ISO, the folder containing 32 bit WIM or ESD file is X:\x86\Sources, and folder containing 64 bit WIM or ESD file is X:\x64\Sources.

    To deploy Windows with edition index 1 from mounted ISO Y: to partition Z:, the command is:

    dism /Apply-Image /WimFile:Y:\Sources\install.wim /Index:1 /ApplyDir:Z:\

    Again, change install.wim to install.esd if using ESD based MCT ISO.

    To add deployed Windows on drive Z: to Windows boot menu, use following command:

    bcdboot Z:\Windows

    When deployed, the new OS has ID {default}. To rename it, give it a better description, use following command:

    bcdedit /set {default} description "Any name"

    AnyName = name you want to use and show as description on boot menu.

    That's it!

    Kari
    Hi @Kari, I always use

    bcdboot z:\windows /p /d

    Those switches keep the current OS you are using as the default boot OS.

    I have had cases in the past where the new bcd boot entry is screwed up and PC does not get as far as the boot menu (or sometimes it starts to boot, fails and when you restart, it tries to reboot to same OS ie you do not get to boot menu), and I have to recover using good old Macrium Reflect 'fix boot problems'

    With those switches, the original boot entry is left as default, and pc normally gets to the dual boot screen without any further issue.
      My ComputerSystem Spec


  3. Posts : 14,064
    Windows 10 Pro
    Thread Starter
       1 Week Ago #1273

    cereberus said: View Post
    Hi @Kari, I always use

    bcdboot z:\windows /p /d

    Those switches keep the current OS you are using as the default boot OS.
    There's a reason why I always leave newly deployed secondary OS as default and recommend users do the same. The deployment, applying image with DISM only takes care of Windows Setup (the installation phase).

    When you boot to new OS first time, OOBE starts requiring 5 to 10 minutes and two restarts. Leaving the new OS temporarily default, you can take a break, not having to stay in front of display to select correct OS after those restarts.

    When I am then on desktop of the new OS first time, I run msconfig and set the main, original OS as default.

    Click image for larger version. 

Name:	image.png 
Views:	21 
Size:	124.6 KB 
ID:	191169


    cereberus said: View Post
    I have had cases in the past where the new bcd boot entry is screwed up and PC does not get as far as the boot menu (or sometimes it starts to boot, fails and when you restart, it tries to reboot to same OS ie you do not get to boot menu), and I have to recover using good old Macrium Reflect 'fix boot problems'

    With those switches, the original boot entry is left as default, and pc normally gets to the dual boot screen without any further issue.
    If deployment has been done correctly, without errors, the OS always boots. Following instructions on the video, it just works.

    Most typical error for an OS being not able to start is when user is using a native boot VHD; if let's say VHD file has been created as 128 GB dynamically expanding VHD, it requires this 128 GB free on the partition where the VHD file is stored. If the free space falls under 128 GB, boot fails and this will be shown:

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	228.6 KB 
ID:	191170

    However, that is an easy error to fix. Simply press F9 to show boot menu and select your main OS.

    Kari
      My ComputerSystem Spec

  4.    1 Week Ago #1274

    Kari said: View Post
    There's a reason why I always leave newly deployed secondary OS as default and recommend users do the same. The deployment, applying image with DISM only takes care of Windows Setup (the installation phase).

    When you boot to new OS first time, OOBE starts requiring 5 to 10 minutes and two restarts. Leaving the new OS temporarily default, you can take a break, not having to stay in front of display to select correct OS after those restarts.

    When I am then on desktop of the new OS first time, I run msconfig and set the main, original OS as default.

    Click image for larger version. 

Name:	image.png 
Views:	21 
Size:	124.6 KB 
ID:	191169




    If deployment has been done correctly, without errors, the OS always boots. Following instructions on the video, it just works.

    Most typical error for an OS being not able to start is when user is using a native boot VHD; if let's say VHD file has been created as 128 GB dynamically expanding VHD, it requires this 128 GB free on the partition where the VHD file is stored. If the free space falls under 128 GB, boot fails and this will be shown:

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	228.6 KB 
ID:	191170

    However, that is an easy error to fix. Simply press F9 to show boot menu and select your main OS.

    Kari
    I am aware vhd limitation - I only set them around 50GB. I can assure you I have had cases where the pc fails to boot properly - probably driver related and I just got caught in a reboot loop, and pressing f9 made no difference. Never had an issue I could not easily get out of since I added those parameters.
      My ComputerSystem Spec


 

Related Threads
Hi fellow Ten Forums geeks :) Thanks to @Wynona's and @Cliff's idea I thought why not start sharing our homemade Windows 10 themes. To keep this clean and simple, please post only themes with copyright free or your self made backgrounds to avoid...
Read more: New Windows 10-based Xbox One user experience will soon roll out to all Preview members
7730 Not bad numbers 10 10 for the first month of the leak. I am sure it will continue to grow!:party: Charlie
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:26.
Find Us