Windows Videos


  1. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #1271

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

    Jack
      My Computer


  2. Posts : 15,441
    Windows10
       #1272

    Kari said:
    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 Computer


  3. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #1273

    cereberus said:
    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.

    Windows Videos-image.png


    cereberus said:
    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:

    Windows Videos-image.png

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

    Kari
      My Computer


  4. Posts : 15,441
    Windows10
       #1274

    Kari said:
    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.

    Windows Videos-image.png




    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:

    Windows Videos-image.png

    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 Computer


  5. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #1275

    Last Saturday, 8th of December, we had one of our TenForums Live webcasts. The topic was Hyper-V, and I had prepared a presentation / demonstration about how to use Differencing Disks to save both storage space and time.

    Although the webcast was recorded, it was too hard to edit the footage because lots of on & off topic chat going on, questions and answers and so on. I decided to make a "clean" capture instead of posting that video.

    You geeks who participated, please do not take this wrong; it is completely OK to chat and interrupt presentations with clarifying questions. I just thought that the topic is important, and wanted to make a bit better video.



    Video description on YouTube:

    How to use Hyper-V Differencing Disks to save storage space and time when creating new virtual machines.

    Please post all comments on TenForums: Video: Hyper-V Differencing Disks - Windows 10 Forums

    Medical advice: if the narrator's hard, Scandinavian accent causes pain in your ears and / or orpsychological issues, consult your local bartender.

    Kari
      My Computer


  6. Posts : 4
    Windows 10
       #1276

    Thread too long, I want to slowly look at these content, good post.
      My Computer


  7. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #1277

    Suoimer said:
    Thread too long.
    First post has table of contents in an embedded Excel sheet, which is updated today.
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #1278

    New video: Hyper-V - Enable Nested Virtualization.



    Nested virtualization allows running Hyper-V on a virtual machine. In addition, it allows Windows Sandbox (available in build 18305 and later) to be run on a virtual machine, which in its turn allows saving snapshots of Sandbox using Hyper-V Production Chekpoints. Simply setup Sandbox on a Hyper-V VM, and when you need to save Sandbox current state, create a checkpoint for the VM.

    This video shows how to setup nested virtualization on a VM in just a minute.

    You can download the simple PowerShell script used in video here:

    Download

    Unblock the script before running it (tutorial)!

    Notice that Hyper-V and Windows Sandbox are not available in Windows 10 Home edition.

    Read more: Nested Virtualization | Microsoft Docs

    Kari

    EDIT: In this post, I told earlier to create Standard checkpoint to include Sandbox current state. That is not correct, I apologisize the error; to save current state of Sandbox, you need of course a Production checkpoint.
    Last edited by Kari; 15 Dec 2021 at 05:59.
      My Computer


  9. Posts : 8
    Windows 10 TP
       #1279

    The link in the video to the mini server no longer exists or has been renamed to something else. Its a no go for me.
      My Computer


  10. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #1280

    Jazmac said:
    The link in the video to the mini server no longer exists or has been renamed to something else. Its a no go for me.
    Yes, the UUP Dump Miniserver does not work anymore. See this tutorial for an alternative method: Windows Insider - Get Latest Fast Ring ISO image | Tutorials

    Kari
      My Computer


 

  Related Discussions
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:12.
Find Us




Windows 10 Forums