MSDM turned out to be an annoyance, now that we have MAS, I'd rather not have that table at all honestly.
Why, the msdm is an 100% genuine activation, it only mostly is for Home (on business devices it mostly is Professional), do you want to activate another SKU then just use MAS HWID.
I usually just add a default ei.cfg to my USB stick and install Pro or Enterprise to bypass the Home key in MSDM.
After downloading the 22h2 updated w10 iso and svf file, Virus Total flags svfx.exe & AVG won't allow svfx.exe to open stating it is infected with IDP.HELU.autoIt11. Should I be getting these virus alerts?
Most likely false positives, set avg to allow it to be used. And else get your ISO directly from MASSGRAVE: https://forums.mydigitallife.net/posts/1887222
After getting around to start the install of the w10 file on os.click, I noticed two things. 1) The download on os.click says the build is 19045.4894, but the .wim file says the version is 19041.4894. Wouldn't that mean that the build is based on the 2020 h1 build instead of the 19045 / 22h2 build ? ________________________________________________________________________________________________ 2) During the .iso transfer to a usb stick, a pop up surprised me stating the boot loader had been revoked. Similar with the w10 image on Massgrave. en-us_windows_10_consumer_editions_version_22h2_updated_sep_2025_x64_dvd_4a22741d.iso What is that about? ] View attachment 73523
This is expected. Current versions of Rufus will now provide a warning that your ISO doesn't have a boot file signed by the UEFI CA 2023 Secure Boot cert. If you're not using Secure Boot (it's disabled), this warning can be ignored. If you have not revoked the CA 2011 cert (by adding it to your UEFI's DBX list), this warning can be ignored. If you have revoked the CA 2011, then may need to mount the image and update it. Rufus wants to provide visibility so you're not surprised why the USB drive gets a security error when booting in Secure Boot mode.
This is also expected. 19041 is the real (base) build number. All other build numbers (19042-19045) are purely virtual (Registry entry) and activated through an Enablement Package (EP), which is a normal ~20KB update only. The updates for all 1904x builds are the same. You could even still update 20H1 with them, if they didn't block it.
I think the true problem is the URL. I can remember the massgrave.dev link well, but I can't memorize the forum URL. MDL needs a shortURL service, stat!
or a new tool with gui on github tested on a win 10 to 25h2 laptop from 2013 tool is flyoob.......... probably using integrated features from various on this forum am sure