@adric known issue https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-319#post-1459586 you cannot integrate x86 CU offline anymore unless they release fixed SSU or use the workaround (audit mode + online CU + sysprep + capture new install.wim)
Upgraded to 2019 LTSC yesterday. Spend the entire afternoon going through tweaking and modifying it again. And we are the lucky ones! We only have to do this every 3 years... I had to actually create a shortcut for control panel because MS literally hides it now. I really don't like were windows is going.
yep same here the first thing I needed to do was put in the desktop was a shortcut to the control panel and another to the cmd otherwise it is impossible to "tune" anything in this crap literally speaking well to me to M$FT filled the OS with useless frills by this is that now I do not even leave the 2015 LTSB at least until next year from there is only upgrade to the 2016 LTSB; on the other hand with the experience that I have acquired over the years I could verify the following: the first thing that the user needs to do in the 1803 or 1809 compilation is to first configure the GPO because otherwise it is a headache only whereas in the previous versions of LTSB there is this type of problem since it is possible to configure the GPO after I say this because this dawn when trying to install the AMD video drivers Windows "broke" the installation because the file MF.DLL and MFREADWRITE.DLL were missing ?? (this means something related to code execution signature) then I needed to enter the security mode using the DDU first remove the WHQL driver that I had tried to install, I downloaded another AMD driver by the Laptop I went to the pendrive there puff !! finally managed to install the video driver correctly then I say again that M$FT seems to think that everyone is a developer to use this crap of LTSC 2019 so I wonder how does the poor user who has Windows 10 HOME ??! ! finally I turn off my main machine I unplugged the HDD used for the test I connected the SSD again and I am here happy of the way with my 2015 ROUND LTSB without any annoying problem or warnings of the operating system and finally removing Windows Defender correctly is not a task easy for anyone can believe is only my 2 cents for this nightmare sorry for my English Ooops: wrong thread correct is: Windows Enterprise 10 (N) LTSC 2019)
What's the problem? The generic/cosmetic error? KMS activation expects the machine to have a SLIC (standard for OEM machines). In case the SLIC is missing that message is presented and can be safely ignored. If you do not believe, contact your system admin .
not simply go where I indicated and from there make another post showing your problem that someone will help you in the best way ok
Thanks, I thought it was a error. I assume that the auto in AutoKMS stands for automatically reactivating after the grace period? Thanks, I will post in the correct subforum next time.
It's fine from the open-source POV, but still needs a background process running. If that fails it's able to screw the system due to the deep integration. Had this on friends systems, quite nasty. I prefer solutions that do it via DLL hooking only when the menu is invoked (like SIB++), less error prone (especially with Windows updates).
Iirc SIB++ is the only solution using a hook, Start8/10 is also using background process(es). Totally worth the few bucks for SIB++. Didn't check/test any others.
i don't have a problem using the std ltsb crapless menu pin to start all my programs and find this ideal