i upgraded and i say it's only worth it if you really need it. if you want the dark theme for the explorer > upgrade if you want to play newer games like forza 4, or need a higher windows version for other stuff > upgrade if you want minor tweaks like gpu usage in the task manager and other stuff > upgrade but if you don't need any of this stuff and everything is already working good for you, there is no need at all for you to upgrade. some of my friends will stay on 1607 and i did only upgrade because i wanted to play forza 4, because i liked and wanted the dark theme and because i needed a fresh install anyway. on ltsc 2019 for me, everything runs just as well as on ltsb 2016. so it's up to you, either way you will run the best version of windows 10.
Thanks I have used the 2016 version but went Pro as I had a genuine key. I now have the new Ryzen chip so the new 2019 version should be a better match, I am very tempted to go LTSC as the constant upgrades and updates with Pro get on my nerves. I liked the tranquility of the 2016 LTSB.
I am trying to create an updated x86 ltsb 2016 offline image with W10UI and for some reason I'm getting an error at the end of the processing of the 09-CUM. An error occurred - Package_for_RollupFix Error: 0x800f0922. Everything works fine with the same kbs for an x64 offline image. Any ideas? Spoiler Code: ============================================================ 1. Target (x86) : "u:\$W0\$0_WUI\x86\ltsb+09.wim" 2. Updates: "u:\$W0\$0_WUI\x86\Repo-Dir" 3. DISM: "u:\$W0\ADK_6\amd64\DISM\dism.exe" 4. Enable .NET 3.5: YES 5. Cleanup System Image: YES 6. Reset Image Base: YES 7. Update WinRE.wim: YES M. Mount Directory: "d:\W10UImount" E. Extraction Directory: "d:\cab" ============================================================ 0. Start the process ============================================================ Change a menu option, press 0 to start, or 9 to exit: 0 ============================================================ Running W10UI v5.2 ============================================================ ============================================================ Extracting .cab files from .msu files ============================================================ 03:10 1/4: windows10.0-kb4054590-x86_Net472.msu 2/4: windows10.0-kb4132216-x86_SSU.msu 3/4: windows10.0-kb4457131-x86_CU_18-09.msu 4/4: windows10.0-kb4457146-x86_Flash_18-09.msu ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/4: Windows10.0-KB4054590-x86.cab 2/4: Windows10.0-KB4132216-x86.cab 3/4: Windows10.0-KB4457131-x86.cab 4/4: Windows10.0-KB4457146-x86.cab ============================================================ Mounting ltsb+09.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.15063.0 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_KB4132216~31bf3856ad364e35~x86~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ 03:13 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 2 - Adding package Package_for_KB4054590~31bf3856ad364e35~x86~~10.0.1.2072 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_KB4457146~31bf3856ad364e35~x86~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~14393.2485.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0922 Error: 0x800f0922 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Resetting OS image base ============================================================ 03:19 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 [=========== 20.0% ] Error: 0x8000ffff DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Adding .NET Framework 3.5 feature ============================================================ 03:19 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Enabling feature(s) [==========================100.0%==========================] Error: 0x8000ffff DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Reinstalling cumulative update... ============================================================ 03:20 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~14393.2485.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x8000ffff Error: 0x8000ffff DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Resetting OS image base ============================================================ 03:20 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 [=========== 20.0% ] Error: 0x8000ffff DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ============================================================ Updating winre.wim ============================================================ 03:20 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_KB4132216~31bf3856ad364e35~x86~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~14393.2485.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0922 Error: 0x800f0922 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log 03:23 "u:\$W0\ADK_6\amd64\DISM\dism.exe" /image:"d:\W10UImountre" /Cleanup-Image /StartComponentCleanup /ResetBase Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.14393.0 [=========== 20.0% ] Error: 0x8000ffff DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log errorlevel -2147418113 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image File : U:\$W0\$0_WUI\x86\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.15063.0 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding updated winre.wim ============================================================ 1 file(s) copied. ============================================================ Unmounting ltsb+09.wim - index 1/1 ============================================================ 03:24 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image File : u:\$W0\$0_WUI\x86\ltsb+09.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding ltsb+09.wim ============================================================ Deployment Image Servicing and Management tool Version: 10.0.15063.0 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press any key to exit. 03:30
@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).