Tablet Mode is removed from build 19042.421 (Backported from build 20161). Now I noticed about this. In 19041.685 it exist.
For those who celebrate, Merry Christmas and a wonderful 2021, with lots of peace, health and lots of kisses and hugs!
Hello. I'm new here and not entirely certain I understand everything correctly. I bought a laptop and it came with Windows 10 Home version 1909 build 18363. I was wondering if using the instructions in this post https://forums.mydigitallife.net/th...c-20h1-vb_release.80763/page-157#post-1601562 will allow me to turn it to enterprise version? And then I use KMS_VL_ALL_AIO for activation? As far as I understand that is all I need to do, is that right?
There is something different among 20h1 and 20h2 when it comes to default keyboards available. I have installed both using the following options during OOBE: and these are my keyboards right after 20h1 installation (and all previous versions): but this is how it looks like in 20h2: why it's English (United States) - Polish (Programmers) now? all the settings seem to be the same, so where does the difference come from? any clues?
every installation will auto-update through WU and they're already doing this for some years now, that the Techbench ISO is "older" than the MVS release.
Yes, I already installed the 19042.631 TechBench ISO and then updated to version 19043.685 via Windows Update. I was just thinking that MSFT might want to release 19042.685 as a TechBench ISO. It's not a huge issue, just a point of curiosity.
Whatever the reason, in this day-and-age of cybercrime, it seems like it would be more secure to download 19042.631 from a legit Techbench MSFT server, and then get a hash code from a legit MSFT webpage to certify that you downloaded a genuine copy of Windows 10 from the Techbench server. Upon installation of that bonefide, licensed Techbench copy of Windows 10, you can run Windows Update to get 19042.685 in a matter of seconds. With the MVS ISOs, they are posted across the internet on non-MSFT servers with hash lists that are usually not verifiable. Can you direct me to a verifiable MSFT webpage that has the hash list for MVS ISOs that doesn't require a MVS subscription?
Directly taken from MVS: https://forums.mydigitallife.net/threads/mvs-dump.78070/ ps, when the checksum is verified, the source doesn't matter... Happy New Year
It is courteous of you to volunteer to answer my question. What I am looking for is an MSFT webpage or MSFT source for the MVS hashes. The hash code of a bogus Windows 10 ISO can match the hash code from a counterfeit hash list. If the hash code from a downloaded Windows 10 ISO matches a hash code from a MSFT webpage, with an MSFT-owned domain name, then the Windows 10 ISO is highly likely to be legit. So that is why I am emphasizing the source of the hash list. Happy new year to you too. I hope 2021 is much better than 2020.
If there was one, it would have been common knowledge and people like @whatever127 wouldn't have to find out how to fetch the data directly from MSFT, MVS dump is ran automated without any human interaction needed.
What is the number xxxxx.xxxxx of the build of the official stable version of Windows 10 20H2 distributed by the MVS (former MSDN) channel? Thanks Bye