Proper Windows 10 VM for M1/M2/M3 Macs

Discussion in 'macOS' started by stayboogy, Jan 18, 2024.

  1. stayboogy

    stayboogy MDL Addicted

    May 1, 2011
    855
    229
    30
    #1 stayboogy, Jan 18, 2024
    Last edited: Jun 10, 2024
  2. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,944
    150
  3. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    18,957
    19,486
    340
    Albeit not directly related to the topic of this thread, I'm really curious to know how can installing SKU-specific certificates taken from a regular build on an expired/expiring preview release be beneficial for bypassing the kernel-enforced timebomb and flight-signing policies?

    Kindly don't come up with "it just works," since I genuinely do root for a proper technical explanation. Otherwise, please don't call attention to a run-of-the-mill frankenbuilding method, especially in discussions where Microsoft product activation is not the primary objective.
     
  4. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,944
    150
    Expiration date is just one of the kernel features enforced but the sku stuff.
    Not different than WMCenabled sku or dcpromoenabled.

    Just like you ca switch from server to client or from home to pro, you can switch from something that expires in 2024 to something that expiries never.

    Perhaps this has nothing to do with frankenbuilding.
     
  5. stayboogy

    stayboogy MDL Addicted

    May 1, 2011
    855
    229
    30
  6. stayboogy

    stayboogy MDL Addicted

    May 1, 2011
    855
    229
    30
    Adding this here as well:


    Here is an example of the performance I am talking about. In this instance, which is my goto instance to test both file operation performance and processing performance is this:

    Code:
    sudo fallocate -l 8192m ./testfile
    sudo dd if=/dev/zero of=./testfile bs=1024 count=8388608
    All this does is create a swapfile of 8GB allocating in 1MB blocks.


    Here are the individual results:


    M1 MacBook Pro 16GB/1TB (nvme)--Ubuntu WSL terminal inside a Windows 10 Arm64 VM with 4 cores 8GB RAM:

    Code:
    +0 records in
    8388608+0 records out
    8589934592 bytes (8.6 GB, 8.0 GiB) copied, 65.3213 s, 132 MB/s
    

    Dell i5 quad core 16GB/1.5TB (nvme)--Debian WSL terminal inside Windows 10 x64 bare metal install uefi:

    Code:
    +0 records in
    8388608+0 records out
    8589934592 bytes (8.6 GB, 8.0 GiB) copied, 58.2025 s, 148 MB/s
    
    As you can see, the M1, running essentially the same software but within a Virtual Machine is not far behind my intel i5 quad core installed on bare metal much better storage than the soldered storage of the M1, and it is a whole 7 seconds behind the i5, but with the Virtualization that is going on and writing to a virtual disk that is spread over multiple files, the M1 proves superior. Those 7s are so negligible that it seems stupid to even use my Dell now.