Do you have any hint how to resolve a filename length problem with "explorer.exe" in LTSB 2016 v 1607, build 14393.2396 ? Namely, if the length of the absolute path and file is more then ~250 characters it returns error. Is there any help, besides upgrading to some newer version like 1809. Thanks
I have to note that there are at least TWO versions of oscdimg.exe - a 32bit/x86 version and a x64/64bit (amd64) version of that file. I got both of them after using the get waik tools download but I'll use the 64bit version of oscdimg.exe with W10UI Edit: I have to admit that I'm having tons of fun making my own integrated/slipstreamed W10 LTSB 2016 ISO using W10UI though it's very time consuming
Use its unicode Windows API path: '\\?\C:\Long FileName' Or the UNC path if required: '\\?\UNC\127.0.0.1\c$\Long Filename\'
Anyone installed KB4487006 on their Windows 10 2016 LTSB? Appears to only be available if you manually check for updates, and appears to be pretty large. It took around 45 minutes to download (on a fiber connection, no less), and has been "installing" for the last 15 minutes.
Microsoft "Night light" feature in MS Win 10 LTSB 2016 v1607 OS: Maybe stupid question, but, is there any unofficial solution to integrate the "Night light" feature in MS Win 10 LTSB 2016 v1607 OS? This "Night light" feature comes officially with the MS Win 10 Creators Update v1703, but, considering that there are unofficial solutions available to add, for e.g., the MS Edge web browser, and the Windows Media Center (WMC) on that same and oldie, MS Win 10 LTSB 2016 v1607 OS, maybe someone create some similar and successful solution, even for this "Night light" feature, and for that same OS...? Thank you in advance for the answer!
Thank you @AndyMutz, I already using this great F.lux Software LLC - Justgetflux app for already a year by now, but I was just freely asking, maybe there is a solution to integrate the Microsoft original "Night Light" feature... @hetherozx: For ancient long file name problemo on MS Windows OSs, I also recommend the Purgeie.com - DelinvFile v5.03 (but it become a Trial software in recent days...), or Corz.org - Long Path Fixer for Windows v0.9.0.0 (it is a Freeware)..., because my humble opinion is that the Longpathtool.com - Long Path Tool v5.1.6 (it is a Trial software), is to buggy software... Also, If you are not be able to delete some particular folder because this same error, and none of the above proposed solution will help, try to delete this particular folder in "offline mode" - means, with some Bootable Live CD or DVD media, such as LSoft Technologies Active@Boot Disk... Good luck!
Current updates for .14393 aka 1607 (LTSB 2016) As of 2019/06/11 kb4503267 Cumulative Update 2019/06/11 [CU .3025] kb4132216 Servicing Stack 2018/05/21 [SS Base] kb4503537 Servicing Stack Update 2019/06/11 [SS Add-on] kb4503308 Flash Update 2019/06/11 kb4054590 .NET-4.7.2 2018/07/12 <or> kb4495610 .NET-4.8.0 2019/05/14
it seems that since May 2019, KB4132216 is not needed anymore. at least in my tests, I can now integrate all updates, using just the most current SS update. -andy-
KB4132216 is completely superseded by KB4485447 (SSU from Feb. 2019), KB4498947 (SSU from May 2019), and KB4503537 (SSU from June 2019) and yes, just integrating the recent SS update (which is KB4503537) is good enough as older SSUs like KB4498947 and KB4485447 are no longer needed