N version and KMS (MTKV261) will be uploaded during the evening. (20 min) The same link as before. Yes it is MSDN ISO
Thanks for the links much appreciated, if I have an older LTSB version of 2015 can I just grab the 2016 latest build and update my existing windows without losing its settings and software ? Never done it before and don't fancy chancing anything
Unless you are a WMC user from the US, or you have some DRM'd paid contents, you can upgrade w/o much concern.
Just for the record, I've activated this LTSB 2016 with a MAK key, backed up activation. Replaced the old and small OCZ SSD with a new and larger Samsung one, restored the activation and it worked! Nice!
How do you backup activation, does not matter what you have backup-ed, when you log on it goes through MS servers, not what you have backed up
You mean it connects to activation servers to validate activation? As I'm using a local account, I don't think it so. With the ethernet cable unplugged, I've restored activation and rebooted. Windows was then activated and stayed the same after connecting to the Internet.
It may say activated, but until you go online and log on you will never know, MS servers activate you, not what is on your computer, you just have copy saying activated, but you really wont know until you go online
Generel: the activation always depend on the time-stamp of partition (time-stamp that you format) and not on the HD the only dependence of the HD is the driver -> on a hardware change e.g. HD to SSD boot from a CD or usb you must set the timestamp of the ssd to the same timestamp of the old hd (there are many tools that do it) or simple use a intelligent tool that make a copy of your partition (and make the partition smaller if needed) and then set the timstamp of the old hd to a other (eg old +1) then copy the driver files to the new SSD into the system32 folder voila no new aktivation is needed (sometimes you must use the repair boot function to find the new driver)
can anybody confirm this hashes ? Windows 10 1607 Enterprise LTSB Evaluations 90 days Code: FD65BFE31AF5FD59D8537210CD829FE3E83FEEB2 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_EN-US.iso confirmed ED6E357CBA8D716A6187095E3ABD016564670D5B *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-US.iso confirmed CAD2EC45A1FC5365D18AEEE4D6FCA11514E0BCA9 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_EN-GB.iso 628D657CD87A193ACD3C1DB7FC9577BC53ABDDC1 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_EN-GB.iso 0CA6CEE55DF98B787BCC8CDBC7F3C432F7D22EBB *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_DE-DE.iso 74F7BBD05EF8AA80720E6C52EBCD2146B4F2BE04 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_DE-DE.iso B67033173778C5F0BE7F69F1E85E60AD0446DF98 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_ES-ES.iso 7ECC11E24D0F1798096DCF2FFC4DC21E54824A1A *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_ES-ES.iso 464B2336570C0A528AB4C620079B094E73FAEC09 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_FR-FR.iso 90B2502BCCDD4418A37FEB28FE8006C24B385D6A *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_FR-FR.iso 2FDF3B59561AFDFA83707F4B04E2E6D00D0667AA *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_IT-IT.iso 584DB4D393410AD46E52ECEFDC133F874DB05488 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_IT-IT.iso 36C09BC3477D63719D1692F2C32A6B4DB6752F4B *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_JA-JP.iso 045F644501895E2D4F879304D76A7E28E1F55816 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_JA-JP.iso E36CB00421B3EB30DB081F0A91C2B4D34956FE8D *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_KO-KR.iso F266943721A976A2E226CB824607C45B7F81C64A *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_KO-KR.iso 35679B3CD1FF428259D908184C128522CB3DACA8 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_PT-BR.iso 73E51331E3F7DCB978A4FBCB6434A821A0327EE2 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_PT-BR.iso DE6146FE3FBA9194724240328CECF5DC62DC9242 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_ZH-CN.iso 3A27684D92E7A34D38EF2BA4D2B6A8BED1FE0A1C *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_ZH-CN.iso F35F1C276A21F4E753FA8FDCC070EBCA54842A12 *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X86FRE_ZH-TW.iso CF055BAB9192F6608451C97DF0DB38800DBEA3CC *14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISE_S_EVAL_X64FRE_ZH-TW.iso
multi to TRIAL? You really want (to CREATE) TRIAL to something else! (as source is much easier to obtain by others)
no i don't want svf's i made svf's by myself i locking for some ppl who download the original Iso's and compare it with my hashes - Eval-Center has no sha1 list for the files