If I install Win10 Pro in a DOS-based new notebook & activate via HWID with an online MSFT account, will that be a permanent activation /solution? Or something like KMS activation or activation will be lost after a periodical time i.e. 3/6 months? Asking this as I really don't wanna go through all the hassles of installing Win7 first then activating it, after that going through the manual degradation process as I heard HWID follow the same 'gatherhost' activation path (setup)
HwID = permanent on that hardware, online activation KMS = time-based activation (180d, 45d, 30d), offline activation Search the Internet for "massgravel" and use the Force tool.
Previously I just installed w10 & activated it w/ my W7 Ultimate or Professional key & have had success doing it that way, every time, even upgraded W10 Home to Pro w/ a W7 key. You should save your time & do it that way.
this is for upcoming 21h1 so this should probably be rtm in december or earlier if like 2004 version that was done dec 18 - will wait till after january 2021 patch update if that is the case to get 21h1 and further cu fixes after that timeframe will probably be named windows 10 2104 or some new naming scheme if microsoft changes on whim
Cannot be my list, cause i not have update yet. At now, as far i can read on web (social, forums, telegram etc) there are many specific issues (and i'm sure you already know about): - lsass.exe force to reboot system. - printers and plotters all kind of issue (from people i know who have design studios) (only 2004, 1909 is ok). - troubles and bsod with graphics driver, i know maybe is not microsoft fault... a system 2004 will be unstable anyway. - very frequent games crash after update. - bsod when plug and unplug some thunderbolt docks - trim on hdd (i don't know if already fixed) - defrag on sdd after reboot. - hyperv vm broken after update (i read many peoples with that issue) And i have not read this thread looking for other specific issues. I just notice i have the update ''not ready yet'' suddenly on all my computers from a day to another and without any reason. So that's why i think this is a problematic update, never happen before to a single machine to see the message ''not ready yet''. Even the oldest ones was alwas enough smooth... not this time... So I think I'll wait 20H2, cause is not just an enablement package, from now next few months will be a collection of patch and bug fixes, if ms want put on track this update.
None of that list ever happened to me (and not reported here on mdl), except the optimize/defrag not showing correctly, most are very hardware specific it seems. If it is the same as with 1903 > 1909 by EP (as it does look like it is), the fixes will be valid for 20H1 and 20H2.
Anybody using Windows 10 N for gaming? I remember having problems a few years back, but can't find any info on recent compatibility.
Do not use windows N. I doesnt have some codec needwd for a few apps and games. Its criooled version od windows 10.
Some games will want codecs that it doesn't have and may not run/crash/not display videos, depending on the specific example and how it handles them being missing. You can resolve it by installing the 'Media Feature Pack' from Microsoft... but then you've just installed the stuff that was removed from N anyway, so what was the point in installing N in the first place?
IIRC, Media Feature Pack cannot replenish all the missing things, some will stay broken. Just do not install the broken-by-design-and-EU-laws N-SKUs.
Hi, Has anyone tried installing 2004 on Surface Pro X from an ISO? It seems to have an upgrade block in place. I wonder if anyone installed a clean version from an ISO and if yes, do you have any problems? Thanks!
still blocked, i've managed to clean install 18362 build only with export-driver option from one and only 1903 recovery image