[DISCUSSION] Windows 10 Enterprise (N) LTSC 2019

Nope, KMS or KMS38 (and probably KEY/MAK) only.

 

So the latest ISO is 17763.107, but I'm seeing posts with people on build 17763.316. Do I just install from that ISO and run windows update? or do I have to do something manually to get it to .316?

 

You can actually get it to build .349. Check out the Windows 10 Hotfixes thread.

 

I did and found the post with the needed updates, thank you!

 

I am testing LTSB and the conversion of calculator units works and the quick keys assigned on the notepad also do it without problem.

I wonder why it doesn't do it correctly in LTSC if it's more 'current'.

 

On my LTSC, I have the old calculator. Any way to get the new one?

 

This probably has been asked before, but I couldn't find it by the search.

Say I would want to change my Windows 10 LTSC install to a Windows 10 Pro version. Is an in-place upgrade the only way to do this?
I remember having seen that it is possible to change a reg key and then enter a w10 pro key. It was (or is) on MDL.

Cheers.

 

This should be helpful: https://forums.mydigitallife.net/th...e-switch-core2pro-upgrade-up-downgrade.78147/

 

Is anyone using Optimize-Offline having issues integrating Windows Store since the apps were updated on git or is it just me?

LE: Found the issue, reported on github.

 

That's just what I needed, thanks.

 

Do you know or do you think this will be fixed at some point with an update?

Using the Store?

 

I can't get the in-place upgrade to work from Enterprise 1803 to LTSC - the option "Keep personal files and apps" is greyed out, regardless of what I choose in the license switcher. What am I missing here?

 

Question: Can I download the .1 build of 1809 and just offline update that one myself? In other words, is there anything in the .107 "refresh" integrated by microsoft that I as an end-user can't integrate via dism(for example)?

 

I just use the .1 iso and update offline with dism using the latest CU. There's no issue that I know of going either way, you just get a somewhat smaller iso without integrating a new CU on top of the one already applied. In terms of function I don't think there's any difference.

 

Please ask for help with the tool, in the tread of the tool, @s1ave77 can help or clarify this.

 

No.

 

Do you think is impossible to manipulate in this way the boot.wim?

 

new updated iso?

 

LTSB & LTSC never get refresh iso's.

Except for 17763.107, but MSFT doesn't consider it a refresh release but the re-release of 1809.

 

Wzor just tweeted..