How can any system verify/confirm it's not a MSDN iso with a VLSC filename, if the content is exactly 1000% identical?
Again good question, and ask Microsoft. I don't know how many times I have to explain this to you. I downloaded the en-us ISO from my MSDN. It won't activate with the VAMT key. Neither will Server nor Office. Again though I thank you for the ISO I needed, and not making me wait for Microsoft to finally fix my VLSC account. Good day to you.
@Slacker220 I do have some knowledge about enterprise setup and I can assure you, the error is in your end (probably trying to use LTSB 2015 MAK on LTSB 2016) - as the MSDN and VLSC ISOs are exactly same and behaves similarly in my test environments.
Incorrect as it worked just fine with the VLSC media. The issue only comes with MSDN media, and no I am not trying to use LTSB 2015 MAK keys. Thank you for you input though.
MSMG ToolKit, this will make it in install iso Not with this but an upgrade with it will work seems you want a standalone install of edge
Hi, I've been dealing with trying to update current version (14393.0) of ltsb n to version 14393.2035 but so far no achievement. Could someone please guide me which servicing stack (if any) and CU I have to integrate?
In WHD you can download all 4 updates, if you hover above the updates, it will tell what it is. 14393 SSTack = KB4049065 14393 CU = KB4057142
Allright, I've been dealing with creating up to date and clean 1607.2035 ISO for two days but no achievement. I kindly request if anybody has a link or ISO of that build, could you please help me? Thanks in advance.
What is the problem? I just made 4 x 201LTSB 14393.2035 iso's by just integrating the updates, when you're not familiar with the use of simple dism commands, you can use W10UI online/offline Updates Integration script. Put the updates, downloaded by WHD next to the script and set it to your desired settings, this was my configuration: Code: @echo off cd /d "%~dp0" set uiv=v4.1 :: when changing below options, be sure to set the new values between = and " marks :: for updating current os, leave this option as %SystemDrive% set "target=i:\W10UI_4.1\2016_LTSB\Work" :: updates location, %cd% represent the current script directory set "repo=i:\W10UI_4.1\2016_LTSB\Updates_x64" :: dism.exe tool path (default is system's if the host os is win10) set "dismroot=%windir%\system32\dism.exe" :: enable .NET 3.5 feature set net35=1 :: optional, specify custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "net35source=" :: Cleanup OS images to "compress" superseded components (might take long time to complete) set cleanup=1 :: Rebase OS images to "remove" superseded components (warning: break "Reset this PC" feature) :: require first to set cleanup=1 set resetbase=0 :: create new iso file if the target is a distribution folder :: require placing oscdimg.exe or cdimage.exe next to W10UI.cmd set iso=1 :: set this to 1 to start the process directly once you execute the script :: make sure you set the above options correctly first set autostart=0 :: optional, set temporary directory for extracted files set "cab_dir=%~d0\W10UItemp" :: optional, set mount directory for updating wim files set "mountdir=%SystemDrive%\W10UImount" set "winremount=%SystemDrive%\W10UImountre" For iso creation you need to either put oscdimg.exe* or cdimage.exe** next to the script too. *. oscdimg.exe gets installed by the windows ADK and can be found in the install folder of ADK (in my scenario: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg". **. Cdimage.exe you can find in the bin folder of the UUP>ISO converter project.
Hello guys, I'm new to this forum. Today I installed the Windows 10 LTSB customized with MSMG Toolkit in my computer to be lighter and I'm feeling the OS very light and solid, but I'm not being able to activate this copy. I have a legit license for Windows 10 that I've used it to activate an original ISO of Windows 10 downloaded from Microsoft a couple of weeks ago. Any idea what's going on? I get the error code 0x8007007B in the Activation option in Settings and also the error code 0x80041014 in the "Change product key" option. PLEASE HELP MY FRIENDS thank you in advance
Do both of these win10 have the same edition ? if they are different, that's normal the activation has failed, you can't use 1 license key to activate 2 different win10 editions, the editions have to be identical.
Thanks for your soon reply! Ok, I guess that was the problem, according to the "System information" of administrative tools, says: Build:14393 (I'm not sure if it's the right place to look at), and my license is for the Win 10 Pro (1709). So, nothing that I can do right?
LTSB need KMS activation > https://forums.mydigitallife.net/threads/kms_vl_all-online-offline-kms-activator.63471/