1. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    719
    444
    30
    OK, so now on uupdump.ml I'm seeing .449 on both branches. There's one on the 18362 branch and another one on the 18363 branch. I think I've been drinking the wrong brew!!! Fortunately, the hashes are exactly the same, so the 18363.449 appears to be a duplicate of 18362.449.

    But what's more intriguing is that we have another build! We've got "Windows 10 Version 1909" and "Windows 10 Version Next". 'Not sure what the "Next" version is, but the link leads nowhere. Any ideas?
     
  2. cuteee

    cuteee MDL Guru

    Oct 13, 2012
    5,729
    982
    180
  3. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. ultimate_live

    ultimate_live MDL Expert

    Mar 15, 2011
    1,022
    671
    60
    #6564 ultimate_live, Oct 24, 2019
    Last edited: Oct 24, 2019
    With Windows 10 19H2 does Windows Sandbox work with Vmware Workstation?
     
  5. toyo

    toyo MDL Senior Member

    Aug 14, 2009
    472
    313
    10
    That can't happen. You cannot have 2 hypervisors both working as far as I know.
     
  6. GodHand

    GodHand MDL Addicted

    Jul 15, 2016
    534
    926
    30
    You can indeed run Windows Sandbox and VMWare together (or any additional hypervisor). First, you have to create a replica of your active boot entry using BCDEdit but adding trailing text to its description to make sure it's easily identifiable. For example 'No Hyper-V.'

    TL;DR Open an elevated command-prompt and enter:

    Code:
    bcdedit /copy {current} /d “Windows 10 – No Hyper-V”
    
    This copies your current boot entry and creates an exact replica with the 'No Hyper-V' added to its description.

    Once that is complete, it will create a unique GUID that is bound to that boot entry and returns it to the console. Save this GUID and then set its hypervisorlaunchtype to 'off':

    Code:
    bcdedit /set {GUID} hypervisorlaunchtype off
    
    Then reboot your PC and you will enter the Windows Boot Manager where you select your previously created “Windows 10 – No Hyper-V” boot entry.

    To revert this process and disable the usage of Windows Sandbox and VMWare is much easier: just press the Windows key + R and enter 'msconfig' into the search bar. Select the 'Boot' tab and delete the 'Windows 10 - No Hyper-V' entry.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. toyo

    toyo MDL Senior Member

    Aug 14, 2009
    472
    313
    10
    That's not running them together? That's disabling one hypervisor so the other can run. VMware can't run with HyperV enabled. Sure this is a decent solution to just disabling features and rebooting, but in the end it's not running them together.
     
  8. ultimate_live

    ultimate_live MDL Expert

    Mar 15, 2011
    1,022
    671
    60
    Thanks for it. Another question. Were can I find the hashes of Windows 10 19H2 Enterpise x64?
     
  9. LostED

    LostED SVF Patch Lover

    Jul 30, 2009
    7,154
    21,096
    240
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,678
    450
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,678
    450
  12. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,405
    605
    60
  13. SAM-R

    SAM-R MDL Guru

    Mar 21, 2015
    5,822
    5,609
    180
    Yes Those were .CAB Files. It is now on Windows Update, so Files are now .MSU
     
  14. bonesz

    bonesz MDL Addicted

    Jun 30, 2013
    634
    354
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,678
    450